ios: aws tst spec collect logs corerctly

Author: hannojg

apps/simple-camera/device-farm-tests/AwsTestSpecIOS.yml

@@ -29,8 +29,11 @@ phases:
 
   test:
     commands:
-      - HARNESS_JUNIT="$WORKING_DIRECTORY/harness-results.junit.xml"
-      - HARNESS_LOG="$WORKING_DIRECTORY/harness-output.log"
+      - HARNESS_ARTIFACTS="$WORKING_DIRECTORY/harness-artifacts"
+      - HARNESS_JUNIT="$HARNESS_ARTIFACTS/harness-results.junit.xml"
+      - HARNESS_LOG="$HARNESS_ARTIFACTS/harness-output.log"
+      - HARNESS_METRO_HOST_FILE="$HARNESS_ARTIFACTS/metro-host-ip.txt"
+      - mkdir -p "$HARNESS_ARTIFACTS"
 
       # Resolve host IPv6 for Metro. On macOS runners IPv4 won't work, as
       # confirmed by AWS support. AWS recommends utun interfaces for this.
@@ -49,7 +52,7 @@ phases:
         fi
 
         echo "Using Metro host IPv6 for iOS harness: ${METRO_HOST_IP}"
-        echo "$METRO_HOST_IP" > "$WORKING_DIRECTORY/metro-host-ip.txt"
+        echo "$METRO_HOST_IP" > "$HARNESS_METRO_HOST_FILE"
 
       # Actually run the JS Harness tests. Harness owns the XCTest agent
       # lifecycle, but uses AWS's generated .xctestrun instead of building one.
@@ -63,7 +66,7 @@ phases:
         HARNESS_IOS_XCTESTRUN_FILE="$DEVICEFARM_XCUITESTRUN_FILE" \
           HARNESS_IOS_XCTEST_DERIVED_DATA_PATH="$DEVICEFARM_DERIVED_DATA_PATH" \
           HARNESS_METRO_BIND_HOST="::" \
-          HARNESS_IOS_METRO_HOST="$(cat "$WORKING_DIRECTORY/metro-host-ip.txt")" \
+          HARNESS_IOS_METRO_HOST="$(cat "$HARNESS_METRO_HOST_FILE")" \
           HARNESS_IOS_DEVICE_ID="$DEVICEFARM_DEVICE_UDID" \
           HARNESS_DETECT_NATIVE_CRASHES=false \
           CI=true \
@@ -74,4 +77,4 @@ phases:
             --reporters=jest-junit 2>&1 | tee "$HARNESS_LOG"
 
 artifacts:
-  - $WORKING_DIRECTORY
+  - $WORKING_DIRECTORY/harness-artifacts