test-native-2.yml
on: push
Build iOS RN Test App (Prod)
/
Build
11s
Build iOS RN Test App (Dev)
/
Build
14s
Native iOS Test (Prod)
8m 4s
Annotations
2 errors and 1 warning
Unhandled error:
tests/rn-test-container/native-test.test.ts#L20
Error: ENOENT: no such file or directory, lstat 'tests/rn-test-container/build/Build/Products/Release-iphonesimulator/RNTestContainer.app'
❯ Object.lstatSync node:fs:1641:25
❯ Object.lstatSync ../../node_modules/graceful-fs/polyfills.js:318:34
❯ statFunc ../../node_modules/fs-extra/lib/util/stat.js:24:20
❯ getStatsSync ../../node_modules/fs-extra/lib/util/stat.js:25:19
❯ Object.checkPathsSync ../../node_modules/fs-extra/lib/util/stat.js:64:33
❯ Proxy.copySync ../../node_modules/fs-extra/lib/copy/copy-sync.js:27:38
❯ setup native-test.test.ts:20:3
❯ native-test.test.ts:104:5
❯ ../../node_modules/@vitest/runner/dist/index.js:146:14
❯ ../../node_modules/@vitest/runner/dist/index.js:533:11
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -2, code: 'ENOENT', syscall: 'lstat', path: 'tests/rn-test-container/build/Build/Products/Release-iphonesimulator/RNTestContainer.app' }
This error originated in "native-test.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "native-test.test.ts". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Native iOS Test (Prod)
Process completed with exit code 1.
|
Native iOS Test (Prod)
Cache save failed.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
appium.log
|
580 Bytes |
|
ios-test-container-prod
|
12.1 MB |
|