Temporarily disable 'ct install' test in CI

There's some kind of incompatibility between the GitHub runner
environment and vLLM v0.11.0's CPU image. During the testing process
the vLLM API pod starts, logs some messages about 'Automatically
detected platform CPU' and the seemingly gets killed and enters a
crash loop. Enabling debug logging on vLLM with
VLLM_LOGGING_LEVEL=DEBUG doesn't provide any useful clues and the same
vLLM CPU tests work fine on a standard Ubuntu 24.04 VM outside of
GitHub actions. Disabling this CI test for now. TODO: Try re-enabling
this when a newer vLLM version is available.

Author: sd109

.github/workflows/test-pr.yml

@@ -111,5 +111,12 @@ jobs:
       # https://github.com/helm/charts/blob/master/test/README.md#providing-custom-test-values
       # Each chart/ci/*-values.yaml file will be treated as a separate test case with it's
       # own helm install/test process.
-      - name: Run chart install and test
-        run: ct install --config ct.yaml
+      # NOTE(sd109): There's some kind of incompatibility between the GitHub runner environment
+      # and vLLM v0.11.0's CPU image. During the testing process the vLLM API pod starts, logs
+      # some messages about 'Automatically detected platform CPU' and the seemingly gets killed
+      # and enters a crash loop. Enabling debug logging on vLLM with VLLM_LOGGING_LEVEL=DEBUG
+      # doesn't provide any useful clues and the same vLLM CPU tests work fine on a standard
+      # Ubuntu 24.04 VM outside of GitHub actions. Disabling this CI test for now.
+      # TODO: Try re-enabling this when a newer vLLM version is available.
+      # - name: Run chart install and test
+      #   run: ct install --config ct.yaml