Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip test depending on always-true removed --harmony-atomics flag #155

Merged

Conversation

ajklein
Copy link
Member

@ajklein ajklein commented Apr 14, 2023

The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.

@ajklein ajklein requested a review from syg April 14, 2023 21:01
Copy link

@syg syg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@ajklein ajklein merged commit d016b39 into v8:node-ci-2023-03-15 Apr 14, 2023
@ajklein ajklein deleted the 2023-04-14_skip_noatomics_test branch April 14, 2023 21:17
pthier pushed a commit that referenced this pull request Apr 26, 2023
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
victorgomes pushed a commit that referenced this pull request May 22, 2023
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
pthier pushed a commit that referenced this pull request Jul 4, 2023
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
pthier pushed a commit that referenced this pull request Aug 24, 2023
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
victorgomes pushed a commit that referenced this pull request Sep 12, 2023
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
victorgomes pushed a commit that referenced this pull request Sep 12, 2023
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
victorgomes pushed a commit that referenced this pull request Nov 8, 2023
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
pthier pushed a commit that referenced this pull request Jan 17, 2024
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
victorgomes pushed a commit that referenced this pull request Feb 14, 2024
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
victorgomes pushed a commit that referenced this pull request Mar 4, 2024
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
pthier pushed a commit that referenced this pull request Mar 21, 2024
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
victorgomes pushed a commit that referenced this pull request Apr 23, 2024
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
victorgomes added a commit that referenced this pull request Jun 3, 2024
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
# Conflicts:
#	test/parallel/parallel.status
pthier pushed a commit that referenced this pull request Jul 15, 2024
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
# Conflicts:
#	test/parallel/parallel.status
victorgomes added a commit that referenced this pull request Aug 22, 2024
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
# Conflicts:
#	test/parallel/parallel.status
pthier pushed a commit that referenced this pull request Oct 2, 2024
The failing test is a regression test for nodejs#39717, which is about a crash that occurs when the flag is disabled. Given that that will no longer be possible once the flag is gone, this seems safe to disable forever.
# Conflicts:
#	test/parallel/parallel.status
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants