pytest-dev / pytest-dev/pytest-html
Fix headless chrome timeout error in grunt tests
Open
Nobody has claimed this yet.
test
- Dominant language
- Python
- Stars
- 779
- Forks
- 260
- PR merge metrics
- No merged PRs in 30d
Description
The JS tests run by grunt will occasionally fail with the error below. We should fix it. The error is sporadic and goes away on rerun ( usually )
Run npm test
> @ test /home/runner/work/pytest-html/pytest-html
> grunt test
Running "qunit:src" (qunit) task
Testing testing/js_test_report.html >> There was an error with headless chrome
Fatal error: Navigation timeout of 5000 ms exceeded
npm ERR! Test failed. See above for more details.
Error: Process completed with exit code 1.
Run link: https://github.com/pytest-dev/pytest-html/pull/405/checks?check_run_id=1525098011
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running npm test, which invokes grunt test and the qunit:src task against testing/js_test_report.html. Investigate the headless Chrome navigation timeout shown in the linked check run; done means the JavaScript tests no longer fail intermittently with the 5000 ms timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100