| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@ofrobots build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/1939/pipeline |
Sorry, something went wrong.
Original commit message:
[turbofan] Fix ObjectCreate's side effect annotation.
Bug: chromium:888923
Change-Id: Ifb22cd9b34f53de3cf6e47cd92f3c0abeb10ac79
Reviewed-on: https://chromium-review.googlesource.com/1245763
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Jaroslav Sevcik <jarin@chromium.org>
Cr-Commit-Position: refs/heads/master@{nodejs#56236}
Refs: v8/v8@52a9e67
|
Resume Build CI: https://ci.nodejs.org/job/node-test-pull-request/19509/ |
Sorry, something went wrong.
|
Is the test-bootstrap-modules failure on CI with --worker relevant? It happened both CI runs... |
Sorry, something went wrong.
|
It doesn't repro on my machine. I've launched that worker job again: https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/3258/. |
Sorry, something went wrong.
To repro locally, you ran it with something like this?: tools/test.py --worker parallel/test-bootstrap-modules (The --worker flag to tools/test.py is the important bit, I think.) |
Sorry, something went wrong.
|
Yeah. I cannot seem to be able to reproduce this with that command, or with the command to run the whole default suite. It would be good to know if there are other environmental differences on that "freestyle" job. |
Sorry, something went wrong.
|
Here it is happening on a different v10.x PR/CI run. So I think the test is just broken on v10.x-staging. https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/3261/ @nodejs/releasers How to proceed here? Land anyway and a releaser will bisect to figure out where/when CI started failing? 😱 |
Sorry, something went wrong.
|
Possibly relevant: #23876 Also: /ping @nodejs/workers |
Sorry, something went wrong.
|
AFAICT, the test starting failing at e872089 |
Sorry, something went wrong.
@codebytere ^^^^^^^^^^ |
Sorry, something went wrong.
|
looks like this is a new build target. Is it failing anywhere else? cc @nodejs/build |
Sorry, something went wrong.
|
Fixing the regression in this pre-req change: #25112 |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
Original commit message:
[turbofan] Fix ObjectCreate's side effect annotation.
Bug: chromium:888923
Change-Id: Ifb22cd9b34f53de3cf6e47cd92f3c0abeb10ac79
Reviewed-on: https://chromium-review.googlesource.com/1245763
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Jaroslav Sevcik <jarin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56236}
Refs: v8/v8@52a9e67
PR-URL: #25027
Refs: v8/v8@52a9e67
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Original commit message:
[turbofan] Fix ObjectCreate's side effect annotation.
Bug: chromium:888923
Change-Id: Ifb22cd9b34f53de3cf6e47cd92f3c0abeb10ac79
Reviewed-on: https://chromium-review.googlesource.com/1245763
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Jaroslav Sevcik <jarin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56236}
Refs: v8/v8@52a9e67
PR-URL: #25027
Refs: v8/v8@52a9e67
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
| Back | FazBrowse Home | New Git URL |
Original commit message:
[turbofan] Fix ObjectCreate's side effect annotation. Bug: chromium:888923 Change-Id: Ifb22cd9b34f53de3cf6e47cd92f3c0abeb10ac79 Reviewed-on: https://chromium-review.googlesource.com/1245763 Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#56236}Refs: v8/v8@52a9e67
Checklist
V8-CI: https://ci.nodejs.org/view/All/job/node-test-commit-v8-linux/1935/
CI: https://ci.nodejs.org/job/node-test-pull-request/19502/