Skip to content

test: skip node refresh e2e test

Sign in for the full log view
GitHub Actions / Unit Test Results - Windows failed Apr 27, 2024 in 0s

1 fail, 113 pass in 1m 52s

  1 files  ±0   17 suites  ±0   1m 52s ⏱️ +17s
114 tests ±0  113 ✅  - 1  0 💤 ±0  1 ❌ +1 
139 runs  ±0  138 ✅  - 1  0 💤 ±0  1 ❌ +1 

Results for commit 58d8a47. ± Comparison against earlier commit 1eb59b5.

Annotations

Check warning on line 0 in KeyManager should generate pfx keys

See this annotation in the file changed.

@github-actions github-actions / Unit Test Results - Windows

KeyManager should generate pfx keys (KeyManager should generate pfx keys) failed 

junit.xml [took 1m 0s]
Raw output 
Error: thrown: "Exceeded timeout of 60000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
    at D:\a\solo\solo\test\unit\core\key_manager.test.mjs:111:3
    at _dispatchDescribe (D:\a\solo\solo\node_modules\jest-circus\build\index.js:91:26)
    at describe (D:\a\solo\solo\node_modules\jest-circus\build\index.js:55:5)
    at D:\a\solo\solo\test\unit\core\key_manager.test.mjs:25:1
    at SourceTextModule.evaluate (node:internal/vm/module:229:23)
    at Runtime.linkAndEvaluateModule (D:\a\solo\solo\node_modules\jest-runtime\build\index.js:710:20)
    at jestAdapter (D:\a\solo\solo\node_modules\jest-circus\build\legacy-code-todo-rewrite\jestAdapter.js:75:5)
    at runTestInternal (D:\a\solo\solo\node_modules\jest-runner\build\runTest.js:367:16)
    at runTest (D:\a\solo\solo\node_modules\jest-runner\build\runTest.js:444:34)
View more details on GitHub Actions