Allow nightly builds to fail until #1731 can be fixed.#1791
Conversation
|
As you can see, CI is failing due to linters. |
No. The failing linter is allowed to fail, which allows the next stage to proceed with running jobs. The real failures are: Results (137.32s):
288 passed
2 xpassed
4 failed
- cherrypy/test/test_httputil.py:62 test_invalid_status[hey-Illegal response status from server ('hey' is non-numeric).]
- cherrypy/test/test_httputil.py:62 test_invalid_status[status_code1-Illegal response status from server ({'hey': 'hi'} is non-numeric).]
- cherrypy/test/test_httputil.py:62 test_invalid_status[1-Illegal response status from server (1 is out of range).]
- cherrypy/test/test_httputil.py:62 test_invalid_status[600-Illegal response status from server (600 is out of range).]
3 xfailed
2 skipped |
| # TODO: fix tests | ||
| - python: *pypy3 | ||
| - env: TOXENV=pre-commit-pep257 | ||
| - python: nightly |
There was a problem hiding this comment.
This change works:
Your build matrix was set to allow the failure of job 2075.7.
|
The last commit on I believe, something has changed in the runtime of the CI. Which is a separate problem itself. |
Root cause
|
|
This should be fixed by 96b34df now. |
|
Okay, 14c12d2 really fixes it. |
No description provided.