-
-
Notifications
You must be signed in to change notification settings - Fork 747
Problem with tests hanging after they start to run (using puppeteer helper) #3576
Unanswered
jayudey-wf
asked this question in
Q&A
-
I'm wondering if people have seen where tests appear to be hanging after 'starting' the test.
Here is an example of what I see in the console output when running in debug mode before the process stops reporting anything
2023年02月03日T19:47:31.032317730Z Add markup from toolbar
2023年02月03日T19:47:31.032654348Z › Test Timeout: 300s
Failure Reason:
On a successful run I see logging like this
2023年02月03日T19:44:48.154071543Z Add markup from toolbar
2023年02月03日T19:44:48.154315772Z › Test Timeout: 300s
2023年02月03日T19:44:48.381567785Z › [Dir] /testing/test/codeceptjs
2023年02月03日T19:44:48.381668181Z >>Current Test FileName: file
My reporter options look like this
mocha: {
reporterOptions: {
"codeceptjs-cli-reporter": {
"stdout": "-",
"options": {
"verbose": true,
"steps": false,
}
},
"mocha-junit-reporter": {
"stdout": "./output/console.log",
"options": {
"mochaFile": "./output/reports/junit-results.[hash].xml",
}
}
},
}
I'm wondering if there is some other course of action I could do to try and gather some more information about what is 'halting' the process so I can continue my investigation (currently this is happening ~1 in 30 runs)?
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 1 comment
-
- try to turn off
verboseflag - try to increase
--max-old-space-sizefor NodeJS https://nodejs.org/api/cli.html#--max-old-space-sizesize-in-megabytes
Beta Was this translation helpful? Give feedback.
All reactions
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment