-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: run known_issues tests in CI #6559
Conversation
Add `known_issues` tests to `make test` and `make test-ci` targets and their equivalents on Windows.
Appreciate it! Use of the labels really helps save time. |
cc @joaocgreis |
#6555 landed, which means this can land, so I'm removing the |
Single test failure in CI looks unrelated. Opened an "investigate flaky test" issue for it. Re-running CI: https://ci.nodejs.org/job/node-test-pull-request/2521/ |
CI is green. /bump @nodejs/collaborators |
LGTM, but I'm not comfortable being the only sign off on Python code :-) |
LGTM |
Add `known_issues` tests to `make test` and `make test-ci` targets and their equivalents on Windows. PR-URL: nodejs#6559 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
Landed in 5d0b1f4 |
Add `known_issues` tests to `make test` and `make test-ci` targets and their equivalents on Windows. PR-URL: #6559 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
@Trott lts? |
@thealphanerd Yes. |
@Trott does not land cleanly.. feel free to backport |
It's not essential. I'm OK with leaving it out. |
* Since #6559 known_issues does run on CI. * Add some notes to explain the expectations around tests in known_issues. PR-URL: #12262 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Alexey Orlenko <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
* Since nodejs#6559 known_issues does run on CI. * Add some notes to explain the expectations around tests in known_issues. PR-URL: nodejs#12262 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Alexey Orlenko <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
* Since #6559 known_issues does run on CI. * Add some notes to explain the expectations around tests in known_issues. PR-URL: #12262 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Alexey Orlenko <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
* Since #6559 known_issues does run on CI. * Add some notes to explain the expectations around tests in known_issues. PR-URL: #12262 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Alexey Orlenko <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
* Since nodejs/node#6559 known_issues does run on CI. * Add some notes to explain the expectations around tests in known_issues. PR-URL: nodejs/node#12262 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Alexey Orlenko <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
Checklist
Affected core subsystem(s)
test
Description of change
Add
known_issues
tests tomake test
andmake test-ci
targets andtheir equivalents on Windows.
This should not land until #6555 lands first.(#6555 landed, woot.)/cc @cjihrig @Fishrock123 @nodejs/testing ... and whoever the Python folks are who can tell me if I'm Doing It Wrong in
testcfg.py
... @thefourtheye? @bnoordhuis? @jbergstroem? Someone else?