test: un-set test-emit-after-on-destroyed as flaky#51995
Merged
nodejs-github-bot merged 1 commit intoMar 8, 2024
nodejs:mainnodejs/node:mainfrom
abmusse:unmark-flaky-test-emit-after-on-destroyedCopy head branch name to clipboard
Merged
test: un-set test-emit-after-on-destroyed as flaky#51995nodejs-github-bot merged 1 commit intonodejs:mainnodejs/node:mainfrom abmusse:unmark-flaky-test-emit-after-on-destroyedCopy head branch name to clipboard
nodejs-github-bot merged 1 commit into
nodejs:mainnodejs/node:mainfrom
abmusse:unmark-flaky-test-emit-after-on-destroyedCopy head branch name to clipboard
Conversation
I tested running the test case 100k times on the AIX ci machine and was unable to re-produce the error. Also it has not showed up recently as flaky on the ci. I suggest we mark this as un-flaky. ref: #50245 (comment)
richardlau
approved these changes
Mar 7, 2024
Collaborator
lpinca
approved these changes
Mar 7, 2024
Collaborator
|
Landed in 4e109e5 |
rdw-msft
pushed a commit
to rdw-msft/node
that referenced
this pull request
Mar 26, 2024
I tested running the test case 100k times on the AIX ci machine and was unable to re-produce the error. Also it has not showed up recently as flaky on the ci. I suggest we mark this as un-flaky. ref: nodejs#50245 (comment) PR-URL: nodejs#51995 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
marco-ippolito
pushed a commit
that referenced
this pull request
May 2, 2024
I tested running the test case 100k times on the AIX ci machine and was unable to re-produce the error. Also it has not showed up recently as flaky on the ci. I suggest we mark this as un-flaky. ref: #50245 (comment) PR-URL: #51995 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Merged
jcbhmr
pushed a commit
to jcbhmr/node
that referenced
this pull request
May 15, 2024
I tested running the test case 100k times on the AIX ci machine and was unable to re-produce the error. Also it has not showed up recently as flaky on the ci. I suggest we mark this as un-flaky. ref: nodejs#50245 (comment) PR-URL: nodejs#51995 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
I tested running the test case 100k times on the AIX ci machine and was unable to re-produce the error. Also it has not showed up recently as flaky on the ci. I suggest we mark this as un-flaky.
ref: #50245 (comment)
CC @mhdawson @richardlau