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

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

Conversation

BridgeAR
Copy link
Member

@BridgeAR BridgeAR commented Jan 9, 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.

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 addaleax January 9, 2020 21:57
@nodejs-github-bot nodejs-github-bot added v13.x v8 engine Issues and PRs related to the V8 dependency. labels Jan 9, 2020
@addaleax addaleax changed the title deps: deactivate failing tests corresponding to experimental features [v13.x] deps: deactivate failing tests corresponding to experimental features Jan 10, 2020
@BridgeAR BridgeAR force-pushed the 2020-01-09-deactivate-failing-tests branch from 37fb1ca to 79113ae Compare January 10, 2020 08:06
@BridgeAR BridgeAR requested a review from richardlau January 10, 2020 08:07
@BridgeAR
Copy link
Member Author

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 BridgeAR force-pushed the 2020-01-09-deactivate-failing-tests branch from 79113ae to 4ce0365 Compare January 11, 2020 12:56
@BridgeAR
Copy link
Member Author

@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
Copy link
Member Author

BridgeAR commented Jan 11, 2020

@BridgeAR BridgeAR 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
Member

Trott commented Jan 11, 2020

Landed in 6f95f01

@Trott Trott closed this Jan 11, 2020
@codebytere codebytere mentioned this pull request Jan 16, 2020
@codebytere
Copy link
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 free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. v8 engine Issues and PRs related to the V8 dependency.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants