change yaml

Signed-off-by: Judy Ng <[email protected]>

tests/integration-tests/configs/scaling_stress_test.yaml

@@ -2,13 +2,7 @@ test-suites:
   performance_tests:
     test_scaling.py::test_scaling_stress_test:
       dimensions:
-        - regions: [ "us-east-1" ]
-          instances: [ "c5.large" ]
-          oss: [ "alinux2" ]
-          schedulers: [ "slurm" ]
-    test_scaling.py::test_static_scaling_stress_test:
-      dimensions:
-        - regions: [ "us-east-1" ]
-          instances: [ "c5.large" ]
+        - regions: [ "euw1-az3" ]
+          instances: [ "p3.2xlarge" ]
           oss: [ "alinux2" ]
           schedulers: [ "slurm" ]

tests/integration-tests/tests/common/scaling/get_bootstrap_errors.sh

@@ -19,7 +19,7 @@ touch "bootstrap_errors.txt"
 # Find a log message like:
 # ... WARNING - Node bootstrap error: Node queue-0-dy-compute-resource-0-1690(192.168.90.197) ...
 # and get the IP address and instance id
-sudo cat ${CLUSTERMGTD_LOG} | grep -i "Node bootstrap error" | awk -F"[()]" '{print $2}' | while read -r ip_address ; do
+sudo cat ${CLUSTERMGTD_LOG} | grep -i "no corresponding instance in EC2 for node" | awk -F"[()]" '{print $2}' | while read -r ip_address ; do
     # Since the same cluster is re-used for multiple scale up tests, this script may find the same bootstrap error
     # multiple times and then get the wrong instance logs since the IP address would be attached to a new instance.
     # Therefore, only write the compute node logs for the IP address if the file doesn't exist yet.