-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Investigate flaky parallel/test-process-wrap on macos #45805
Labels
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
Comments
bnoordhuis
added
the
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
label
Dec 10, 2022
bnoordhuis
added a commit
to bnoordhuis/io.js
that referenced
this issue
Dec 10, 2022
It's an old test (added when switching from libev to libuv) that tests implementation details of the internal process_wrap bindings. That kind of thing doesn't need testing in this day and age, and since the test is flaky, simply remove it instead of sinking time in fixing it up. Fixes: nodejs#45805
nodejs-github-bot
pushed a commit
that referenced
this issue
Dec 12, 2022
It's an old test (added when switching from libev to libuv) that tests implementation details of the internal process_wrap bindings. That kind of thing doesn't need testing in this day and age, and since the test is flaky, simply remove it instead of sinking time in fixing it up. Fixes: #45805 PR-URL: #45806 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
ErickWendel
pushed a commit
to ErickWendel/node
that referenced
this issue
Dec 12, 2022
It's an old test (added when switching from libev to libuv) that tests implementation details of the internal process_wrap bindings. That kind of thing doesn't need testing in this day and age, and since the test is flaky, simply remove it instead of sinking time in fixing it up. Fixes: nodejs#45805 PR-URL: nodejs#45806 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
targos
pushed a commit
that referenced
this issue
Dec 12, 2022
It's an old test (added when switching from libev to libuv) that tests implementation details of the internal process_wrap bindings. That kind of thing doesn't need testing in this day and age, and since the test is flaky, simply remove it instead of sinking time in fixing it up. Fixes: #45805 PR-URL: #45806 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
targos
pushed a commit
that referenced
this issue
Dec 13, 2022
It's an old test (added when switching from libev to libuv) that tests implementation details of the internal process_wrap bindings. That kind of thing doesn't need testing in this day and age, and since the test is flaky, simply remove it instead of sinking time in fixing it up. Fixes: #45805 PR-URL: #45806 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
danielleadams
pushed a commit
that referenced
this issue
Dec 30, 2022
It's an old test (added when switching from libev to libuv) that tests implementation details of the internal process_wrap bindings. That kind of thing doesn't need testing in this day and age, and since the test is flaky, simply remove it instead of sinking time in fixing it up. Fixes: #45805 PR-URL: #45806 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
danielleadams
pushed a commit
that referenced
this issue
Dec 30, 2022
It's an old test (added when switching from libev to libuv) that tests implementation details of the internal process_wrap bindings. That kind of thing doesn't need testing in this day and age, and since the test is flaky, simply remove it instead of sinking time in fixing it up. Fixes: #45805 PR-URL: #45806 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
danielleadams
pushed a commit
that referenced
this issue
Jan 3, 2023
It's an old test (added when switching from libev to libuv) that tests implementation details of the internal process_wrap bindings. That kind of thing doesn't need testing in this day and age, and since the test is flaky, simply remove it instead of sinking time in fixing it up. Fixes: #45805 PR-URL: #45806 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
danielleadams
pushed a commit
that referenced
this issue
Jan 4, 2023
It's an old test (added when switching from libev to libuv) that tests implementation details of the internal process_wrap bindings. That kind of thing doesn't need testing in this day and age, and since the test is flaky, simply remove it instead of sinking time in fixing it up. Fixes: #45805 PR-URL: #45806 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
danielleadams
pushed a commit
that referenced
this issue
Jan 5, 2023
It's an old test (added when switching from libev to libuv) that tests implementation details of the internal process_wrap bindings. That kind of thing doesn't need testing in this day and age, and since the test is flaky, simply remove it instead of sinking time in fixing it up. Fixes: #45805 PR-URL: #45806 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seems to time out frequently as of late.
Example run: https://ci.nodejs.org/job/node-test-commit-osx/49092/nodes=osx1015/console
It's a really old test (f01b241 from 2011) that's testing internal implementation details that don't need testing so maybe it should just go.
The text was updated successfully, but these errors were encountered: