Uh oh!
There was an error while loading. Please reload this page.
test: always ignore vm-timeout-escape-queuemicrotask - #31980
Closed
lundibundi wants to merge 1 commit into
Closed
Conversation
nodejs-github-bot
commented
Feb 27, 2020
Collaborator
jasnell
reviewed
Feb 27, 2020
Uh oh!
There was an error while loading. Please reload this page.
jasnell
approved these changes
Feb 27, 2020
Uh oh!
There was an error while loading. Please reload this page.
lpinca
approved these changes
Feb 27, 2020
nodejs-github-bot
commented
Mar 2, 2020
Collaborator
2 tasks
mmarchini
approved these changes
Mar 2, 2020
mmarchini
commented
Mar 2, 2020
Contributor
Our CI is treating the skipped test as failing? |
richardlau
commented
Mar 3, 2020
Member
|
This issue is unfixable with the current implementations of V8 and Node.js. Changes to make this fixable are unlikely to happen in the foreseeable future. The test itself is flaky and skipped. It serves as a demonstration of the issue only.
lundibundiforce-pushed
the
ignore-escape-queuemicrotask
branch
from
March 4, 2020 15:53
e13248c to
4629d51Comparelundibundi
commented
Mar 4, 2020
MemberAuthor
@mmarchini@richardlau@jasnell@lpinca PTAL, removed the skip from the test and put to in the .status file instead. |
nodejs-github-bot
commented
Mar 4, 2020
Collaborator
richardlau
approved these changes
Mar 4, 2020
jasnell
commented
Mar 4, 2020
Member
Still LGTM |
nodejs-github-bot
commented
Mar 6, 2020
Collaborator
BridgeAR
approved these changes
Mar 9, 2020
nodejs-github-bot
commented
Mar 9, 2020
Collaborator
nodejs-github-bot
commented
Mar 9, 2020
Collaborator
nodejs-github-bot
commented
Mar 9, 2020
Collaborator
nodejs-github-bot
commented
Mar 10, 2020
Collaborator
mmarchini
commented
Mar 10, 2020
Contributor
Landed in 30bbeb7 |
mmarchini pushed a commit
that referenced
this pull request
Mar 10, 2020
This issue is unfixable with the current implementations of V8 and Node.js. Changes to make this fixable are unlikely to happen in the foreseeable future. The test itself is flaky and skipped. It serves as a demonstration of the issue only. PR-URL: #31980 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matheus Marchini <mat@mmarchini.me> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
MylesBorins pushed a commit
that referenced
this pull request
Mar 10, 2020
This issue is unfixable with the current implementations of V8 and Node.js. Changes to make this fixable are unlikely to happen in the foreseeable future. The test itself is flaky and skipped. It serves as a demonstration of the issue only. PR-URL: #31980 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matheus Marchini <mat@mmarchini.me> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Merged
codebytere pushed a commit
that referenced
this pull request
Mar 23, 2020
This issue is unfixable with the current implementations of V8 and Node.js. Changes to make this fixable are unlikely to happen in the foreseeable future. The test itself is flaky and skipped. It serves as a demonstration of the issue only. PR-URL: #31980 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matheus Marchini <mat@mmarchini.me> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Merged
codebytere pushed a commit
that referenced
this pull request
Mar 30, 2020
This issue is unfixable with the current implementations of V8 and Node.js. Changes to make this fixable are unlikely to happen in the foreseeable future. The test itself is flaky and skipped. It serves as a demonstration of the issue only. PR-URL: #31980 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matheus Marchini <mat@mmarchini.me> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
codebytere pushed a commit
that referenced
this pull request
Mar 31, 2020
This issue is unfixable with the current implementations of V8 and Node.js. Changes to make this fixable are unlikely to happen in the foreseeable future. The test itself is flaky and skipped. It serves as a demonstration of the issue only. PR-URL: #31980 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matheus Marchini <mat@mmarchini.me> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Always skip the test as it is not expected to be fixed (probably ever).
Left in the known_issues as an example and 'note' that the issue is
there and won't be fixed.
Follow up #31966.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes