Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:605:17 ❯ processTimers node:internal/timers:541:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:605:17 ❯ processTimers node:internal/timers:541:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:605:17 ❯ processTimers node:internal/timers:541:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:588:17 ❯ processTimers node:internal/timers:523:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:588:17 ❯ processTimers node:internal/timers:523:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:588:17 ❯ processTimers node:internal/timers:523:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:581:17 ❯ processTimers node:internal/timers:519:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:581:17 ❯ processTimers node:internal/timers:519:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:581:17 ❯ processTimers node:internal/timers:519:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:588:17 ❯ processTimers node:internal/timers:523:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:588:17 ❯ processTimers node:internal/timers:523:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:588:17 ❯ processTimers node:internal/timers:523:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:581:17 ❯ processTimers node:internal/timers:519:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:581:17 ❯ processTimers node:internal/timers:519:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:581:17 ❯ processTimers node:internal/timers:519:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Process completed with exit code 1.

AssertionError: expected 'D:\usr\lib\node_modules\appium\index.…' to be '/usr/lib/node_modules/appium/index.js' // Object.is equality Expected: "/usr/lib/node_modules/appium/index.js" Received: "D:\usr\lib\node_modules\appium\index.js" ❯ packages/wdio-appium-service/tests/cli-utils.test.ts:90:24

AssertionError: expected 'D:\global\appium\index.js' to be '/global/appium/index.js' // Object.is equality Expected: "/global/appium/index.js" Received: "D:\global\appium\index.js" ❯ packages/wdio-appium-service/tests/cli-utils.test.ts:77:24

AssertionError: expected 'D:\project\node_modules\appium\index.…' to be '/project/node_modules/appium/index.js' // Object.is equality Expected: "/project/node_modules/appium/index.js" Received: "D:\project\node_modules\appium\index.js" ❯ packages/wdio-appium-service/tests/cli-utils.test.ts:66:24

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:605:17 ❯ processTimers node:internal/timers:541:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:605:17 ❯ processTimers node:internal/timers:541:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:605:17 ❯ processTimers node:internal/timers:541:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Process completed with exit code 1.

Process completed with exit code 1.

AssertionError: expected 'D:\usr\lib\node_modules\appium\index.…' to be '/usr/lib/node_modules/appium/index.js' // Object.is equality Expected: "/usr/lib/node_modules/appium/index.js" Received: "D:\usr\lib\node_modules\appium\index.js" ❯ packages/wdio-appium-service/tests/cli-utils.test.ts:90:24

AssertionError: expected 'D:\global\appium\index.js' to be '/global/appium/index.js' // Object.is equality Expected: "/global/appium/index.js" Received: "D:\global\appium\index.js" ❯ packages/wdio-appium-service/tests/cli-utils.test.ts:77:24

AssertionError: expected 'D:\project\node_modules\appium\index.…' to be '/project/node_modules/appium/index.js' // Object.is equality Expected: "/project/node_modules/appium/index.js" Received: "D:\project\node_modules\appium\index.js" ❯ packages/wdio-appium-service/tests/cli-utils.test.ts:66:24

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:588:17 ❯ processTimers node:internal/timers:523:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:588:17 ❯ processTimers node:internal/timers:523:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:588:17 ❯ processTimers node:internal/timers:523:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Process completed with exit code 1.

AssertionError: expected 'D:\usr\lib\node_modules\appium\index.…' to be '/usr/lib/node_modules/appium/index.js' // Object.is equality Expected: "/usr/lib/node_modules/appium/index.js" Received: "D:\usr\lib\node_modules\appium\index.js" ❯ packages/wdio-appium-service/tests/cli-utils.test.ts:90:24

AssertionError: expected 'D:\global\appium\index.js' to be '/global/appium/index.js' // Object.is equality Expected: "/global/appium/index.js" Received: "D:\global\appium\index.js" ❯ packages/wdio-appium-service/tests/cli-utils.test.ts:77:24

AssertionError: expected 'D:\project\node_modules\appium\index.…' to be '/project/node_modules/appium/index.js' // Object.is equality Expected: "/project/node_modules/appium/index.js" Received: "D:\project\node_modules\appium\index.js" ❯ packages/wdio-appium-service/tests/cli-utils.test.ts:66:24

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:581:17 ❯ processTimers node:internal/timers:519:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:581:17 ❯ processTimers node:internal/timers:519:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:581:17 ❯ processTimers node:internal/timers:519:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:605:17 ❯ processTimers node:internal/timers:541:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.

Error: Timeout: Appium did not start within expected time ❯ Timeout.<anonymous> packages/wdio-appium-service/src/launcher.ts:242:28 ❯ listOnTimeout node:internal/timers:605:17 ❯ processTimers node:internal/timers:541:7 This error originated in "packages/wdio-appium-service/tests/launcher.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 "should respect custom timeout from config". 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.