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

test: skip instantiateStreaming-bad-imports WPT #47292

Merged
merged 1 commit into from
Mar 29, 2023

Conversation

targos
Copy link
Member

@targos targos commented Mar 29, 2023

This test is flaky on ARM with V8 >= 11.2.
Skip it so we can update V8 before the release of Nodejs 20.0.0.

Refs: #46815 and #47251

This test is flaky on ARM with V8 >= 11.2.
Skip it so we can update V8 before the release of Nodejs 20.0.0.
@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. test Issues and PRs related to the tests. labels Mar 29, 2023
@targos
Copy link
Member Author

targos commented Mar 29, 2023

/cc @nodejs/v8-update @nodejs/tsc

Copy link
Member

@MoLow MoLow left a comment

Choose a reason for hiding this comment

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

RSLGTM

@targos targos added fast-track PRs that do not need to wait for 48 hours to land. request-ci Add this label to start a Jenkins CI on a PR. labels Mar 29, 2023
@github-actions
Copy link
Contributor

Fast-track has been requested by @targos. Please 👍 to approve.

@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Mar 29, 2023
@nodejs-github-bot
Copy link
Collaborator

@panva
Copy link
Member

panva commented Mar 29, 2023

Is it flaky, or just out right failing/hanging to a point where you want to skip it everywhere?

If just flaky, the flaky test names may just be added like so

{
  "instantiateStreaming-bad-imports.any.js": {
    "fail": {
      "note": "You may leave an optional arbitrary note e.g. with TODOs",
      "flaky": [
        "flaky test name"
      ]
    }
  }
}

If it's hanging, we need to look into the running properly handling such cases.

If you want to skip them on a particular build or configuration, there's no way to do that today, but we could revive #45826 (comment) to be able to do this type of skipping/flaky declaration.

@panva panva added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Mar 29, 2023
@targos
Copy link
Member Author

targos commented Mar 29, 2023

It is hanging but not 100% of the runs. Either it passes or it hangs.

@panva
Copy link
Member

panva commented Mar 29, 2023

It is hanging but not 100% of the runs. Either it passes or it hangs.

Let's skip then but open an issue to investigate why the runner can't deal with it.

@RafaelGSS
Copy link
Member

RafaelGSS commented Mar 29, 2023

It is hanging but not 100% of the runs. Either it passes or it hangs.

Let's skip then but open an issue to investigate why the runner can't deal with it.

We can open a revert PR after landing V8 update on main.

@panva panva added the commit-queue Add this label to land a pull request using GitHub Actions. label Mar 29, 2023
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Mar 29, 2023
@nodejs-github-bot nodejs-github-bot merged commit 3cf65bd into nodejs:main Mar 29, 2023
@nodejs-github-bot
Copy link
Collaborator

Landed in 3cf65bd

@targos targos deleted the skip-wasm-webapi branch March 29, 2023 11:58
RafaelGSS pushed a commit that referenced this pull request Apr 5, 2023
This test is flaky on ARM with V8 >= 11.2.
Skip it so we can update V8 before the release of Nodejs 20.0.0.

PR-URL: #47292
Refs: #46815
Reviewed-By: Rafael Gonzaga <[email protected]>
Reviewed-By: Moshe Atlow <[email protected]>
Reviewed-By: Jiawen Geng <[email protected]>
Reviewed-By: Debadree Chatterjee <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
@RafaelGSS RafaelGSS mentioned this pull request Apr 6, 2023
RafaelGSS pushed a commit that referenced this pull request Apr 6, 2023
This test is flaky on ARM with V8 >= 11.2.
Skip it so we can update V8 before the release of Nodejs 20.0.0.

PR-URL: #47292
Refs: #46815
Reviewed-By: Rafael Gonzaga <[email protected]>
Reviewed-By: Moshe Atlow <[email protected]>
Reviewed-By: Jiawen Geng <[email protected]>
Reviewed-By: Debadree Chatterjee <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
RafaelGSS pushed a commit that referenced this pull request Apr 7, 2023
This test is flaky on ARM with V8 >= 11.2.
Skip it so we can update V8 before the release of Nodejs 20.0.0.

PR-URL: #47292
Refs: #46815
Reviewed-By: Rafael Gonzaga <[email protected]>
Reviewed-By: Moshe Atlow <[email protected]>
Reviewed-By: Jiawen Geng <[email protected]>
Reviewed-By: Debadree Chatterjee <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
danielleadams pushed a commit that referenced this pull request Jul 6, 2023
This test is flaky on ARM with V8 >= 11.2.
Skip it so we can update V8 before the release of Nodejs 20.0.0.

PR-URL: #47292
Refs: #46815
Reviewed-By: Rafael Gonzaga <[email protected]>
Reviewed-By: Moshe Atlow <[email protected]>
Reviewed-By: Jiawen Geng <[email protected]>
Reviewed-By: Debadree Chatterjee <[email protected]>
Reviewed-By: Filip Skokan <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
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. fast-track PRs that do not need to wait for 48 hours to land. needs-ci PRs that need a full CI run. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants