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 crypto test on arm buildbots #32636

Closed
wants to merge 0 commits into from

Conversation

bnoordhuis
Copy link
Member

The Raspberry Pis are too slow to run this computationally expensive
test in a timely manner, it times out after 240 seconds.

@nodejs-github-bot nodejs-github-bot added the test Issues and PRs related to the tests. label Apr 3, 2020
@Trott
Copy link
Member

Trott commented Apr 3, 2020

For other computationally-expensive tests, we do this in the code:

if (!common.enoughTestCpu)
  common.skip('test is CPU-intensive');

Maybe do that for consistency and so we don't have to remember to move the .status file entry in case this test gets moved out of known_issues at some point?

@bnoordhuis
Copy link
Member Author

I somehow thought that didn't work with known_issues tests but it does. Updated, thanks for the suggestion.

@mmarchini
Copy link
Contributor

Fast track?

@addaleax addaleax added 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. labels Apr 4, 2020
@nodejs-github-bot
Copy link
Collaborator

@Trott
Copy link
Member

Trott commented Apr 4, 2020

I somehow thought that didn't work with known_issues tests but it does. Updated, thanks for the suggestion.

Judging from the CI results, apparently it doesn't work. Force-pushing out my suggestion and re-running CI....

@Trott Trott force-pushed the skip-crypto-test-on-arm branch from 0e4a968 to 84e86bc Compare April 4, 2020 13:52
@nodejs-github-bot

This comment has been minimized.

@nodejs-github-bot
Copy link
Collaborator

Trott pushed a commit to bnoordhuis/io.js that referenced this pull request Apr 4, 2020
The Raspberry Pis are too slow to run this computationally expensive
test in a timely manner, it times out after 240 seconds.

PR-URL: nodejs#32636
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matheus Marchini <mat@mmarchini.me>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@Trott Trott closed this Apr 4, 2020
@Trott Trott force-pushed the skip-crypto-test-on-arm branch from 84e86bc to 251b08d Compare April 4, 2020 14:47
@Trott
Copy link
Member

Trott commented Apr 4, 2020

Landed in 251b08d

BethGriggs pushed a commit that referenced this pull request Apr 7, 2020
The Raspberry Pis are too slow to run this computationally expensive
test in a timely manner, it times out after 240 seconds.

PR-URL: #32636
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matheus Marchini <mat@mmarchini.me>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Rich Trott <rtrott@gmail.com>
targos pushed a commit that referenced this pull request Apr 12, 2020
The Raspberry Pis are too slow to run this computationally expensive
test in a timely manner, it times out after 240 seconds.

PR-URL: #32636
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matheus Marchini <mat@mmarchini.me>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Rich Trott <rtrott@gmail.com>
targos pushed a commit that referenced this pull request Apr 22, 2020
The Raspberry Pis are too slow to run this computationally expensive
test in a timely manner, it times out after 240 seconds.

PR-URL: #32636
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matheus Marchini <mat@mmarchini.me>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Rich Trott <rtrott@gmail.com>
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. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants