test: bailout test_threadsafe_function/test#24714
Conversation
|
Waiting for #24712 to land before re-running CI. |
|
Resume Build: https://ci.nodejs.org/job/node-test-pull-request/19046/ Might need a full CI re-run to incorporate the change from #24712 if that test continues to fail, but I'm not sure about that. |
looks like either the resume CI did not pick up the landed commit, or the changes did not have any effect - the test is continued to run and fail. Let me run a full CI to confirm one or the other. full CI: https://ci.nodejs.org/job/node-test-pull-request/19072/ |
Running "Resume Build" will rebuild from the same commit as the job that is being resumed. It will not rebase against master. So, yeah, running a full CI was the way to go. Now that we've done that... Resume Build CI: https://ci.nodejs.org/job/node-test-pull-request/19074/ ✔️ |
|
Collaborators, 👍 here to fast-track. |
The test fails consistently on windows-fanned with vs2017. mark it as flaky while the issue is being progressed, and to keep CI green / amber. Ref: nodejs#23621 PR-URL: nodejs#24714 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
c419eb2 to
2b1dd6c
Compare
The test fails consistently on windows-fanned with vs2017. mark it as flaky while the issue is being progressed, and to keep CI green / amber. Ref: nodejs#23621 PR-URL: nodejs#24714 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
The test fails consistently on windows-fanned with vs2017. mark it as flaky while the issue is being progressed, and to keep CI green / amber. Ref: nodejs#23621 PR-URL: nodejs#24714 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
This is a known failure so mark it such, so that
CI is green / amber while the issue is being progressed.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesRef: #23621
Ref: #24607
/cc @Trott