Skip to content

[v13.x] deps: deactivate failing tests corresponding to experimental features - #31289

Closed
BridgeAR wants to merge 1 commit into
nodejs:v13.x-stagingfrom
BridgeAR:2020-01-09-deactivate-failing-tests
Closed

[v13.x] deps: deactivate failing tests corresponding to experimental features#31289
BridgeAR wants to merge 1 commit into
nodejs:v13.x-stagingfrom
BridgeAR:2020-01-09-deactivate-failing-tests

Conversation

@BridgeAR

@BridgeARBridgeAR commented Jan 9, 2020

Copy link
Copy Markdown
Member

This comments out three tests that consistently fail on v13.x.
The test can be activated again in case the necessary code change
lands on v13.x for the tests to pass.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

@BridgeAR
BridgeAR requested a review from addaleaxJanuary 9, 2020 21:57
@nodejs-github-botnodejs-github-bot added v13.x v8 engine Issues and PRs related to the V8 dependency. labels Jan 9, 2020
Comment threaddeps/v8/test/cctest/interpreter/test-bytecode-generator.cc Outdated
@addaleaxaddaleax changed the title deps: deactivate failing tests corresponding to experimental features[v13.x] deps: deactivate failing tests corresponding to experimental featuresJan 10, 2020
@BridgeAR
BridgeARforce-pushed the 2020-01-09-deactivate-failing-tests branch from 37fb1ca to 79113aeCompareJanuary 10, 2020 08:06
@BridgeAR

Copy link
Copy Markdown
MemberAuthor

This comments out three tests that consistently fail on v13.x.
The test can be activated again in case the necessary code change
lands on v13.x for the tests to pass.
@BridgeAR
BridgeARforce-pushed the 2020-01-09-deactivate-failing-tests branch from 79113ae to 4ce0365CompareJanuary 11, 2020 12:56
@BridgeAR

Copy link
Copy Markdown
MemberAuthor

@richardlau the tests seem to be executed even though I used DISABLED_ as described. See https://ci.nodejs.org/job/node-test-commit-v8-linux/2779/nodes=ppcle-ubuntu1404,v8test=v8test/

I therefore went back to commenting them out.

@BridgeAR

BridgeAR commented Jan 11, 2020

Copy link
Copy Markdown
MemberAuthor

@BridgeARBridgeAR added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Jan 11, 2020
Trott pushed a commit that referenced this pull request Jan 11, 2020
This comments out three tests that consistently fail on v13.x.
The test can be activated again in case the necessary code change
lands on v13.x for the tests to pass.
PR-URL: #31289
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
@Trott

Copy link
Copy Markdown
Member

Landed in 6f95f01

@TrottTrott closed this Jan 11, 2020
@codebyterecodebytere mentioned this pull request Jan 16, 2020
@codebytere

Copy link
Copy Markdown
Member

@BridgeAR should this go to v12.x? It doesn't land cleanly but also may be a dont-land. I'll add the label for now but feel free to swap it out!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.v8 engineIssues and PRs related to the V8 dependency.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@BridgeAR@Trott@codebytere@addaleax@targos@richardlau@nodejs-github-bot