| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
This reverts commit f216d5b. Seems like it breaks the nightly job so reverting until we figure that out.
|
@mhdawson build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/2271/pipeline |
Sorry, something went wrong.
|
This needs to be reverted as we do have failing tests when run with coverage enabled (and have forever I think) so the original change prevents the gathering and printing of coverage information. |
Sorry, something went wrong.
|
There is something up with the main coverage job as well, but testing locally I confirmed we need the revert |
Sorry, something went wrong.
|
Would also like to fast track this. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Coverage job CI run, shows that this resolves the issue: https://ci.nodejs.org/job/node-test-commit-linux-coverage-daily/2/ |
Sorry, something went wrong.
|
Renamed jobs as something was broken with the CI job for coverage even though coverage build locally. New CI which references the updated job: https://ci.nodejs.org/view/Node.js%20Daily/job/node-test-commit-linux-coverage/3/ |
Sorry, something went wrong.
|
Windows Node.js CI failure was known issue:#25512 Will resume build. |
Sorry, something went wrong.
|
Build resumed: https://ci.nodejs.org/job/node-test-pull-request/20186/ |
Sorry, something went wrong.
|
I marked this as do not land as the original commit is marked as such. |
Sorry, something went wrong.
|
Strangely renaming a working job, with no other changes caused the job to fail so there is some state somewhere. I've cleared out the workspace, deleted the files on disk but that still did not help. I'm just going to leave it as the new name with "-daily" in the job name. |
Sorry, something went wrong.
|
This link is now valid again https://ci.nodejs.org/job/node-test-commit-linux-coverage-daily/2/ |
Sorry, something went wrong.
|
Ok resumed CI job is green :). |
Sorry, something went wrong.
|
Think I've got the ok's for fast-track, landing now. |
Sorry, something went wrong.
That's sounds like a sub-optimal situation. I'll try to look into that. Cross-ref: #25432 |
Sorry, something went wrong.
P.S. renaming the job the same name as the broken one caused Jenkins to reuse the broken workspace directory. It might store a broken compilation artifact. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This reverts commit f216d5b.
Seems like it breaks the nightly job so reverting until
we figure that out.
Checklist