Investigate flaky crash in test/pummel/test-repl-empty-maybelocal-crash.js on freebsd
#42719
Labels
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
Comments
RaisinTen
added
the
flaky-test
RaisinTen
added a commit
to RaisinTen/node
that referenced
this issue
Apr 13, 2022
Refs: nodejs#42719 Signed-off-by: Darshan Sen <raisinten@gmail.com>
RaisinTen
added a commit
to RaisinTen/node
that referenced
this issue
Apr 13, 2022
Refs: nodejs#42719 Signed-off-by: Darshan Sen <raisinten@gmail.com>
|
The issue seems similar to #41513 (review) |
|
@targos if you're talking about the freebsd error in this CI run - #41513 (comment), i.e., the |
|
I have suspicions that the new test is causing the disconnects on fedora-latest, e.g. https://ci.nodejs.org/job/node-test-commit-linux/nodes=fedora-latest-x64/45410/console -- it looks like the OOM Killer is stepping in. I don't have definitive proof it is this test, but we're in the area of executing the pummel tests and this has only started happening recently. journalctl logsThe droplet has 4 GB of memory. Also this is different from the NIO disconnects we've seen elsewhere caused by Jenkins ping timeouts -- there's no corresponding ping thread timeout message in the Jenkins server log. |
RaisinTen
added a commit
to RaisinTen/node
that referenced
this issue
Apr 14, 2022
It was disconnecting the runners from the CI server. Not worth having a resource-intensive test for this kind of an edge cases. Fixes: nodejs#42719 Signed-off-by: Darshan Sen <raisinten@gmail.com>
|
Landed in 19064be |
xtx1130
pushed a commit
to xtx1130/node
that referenced
this issue
Apr 25, 2022
It was disconnecting the runners from the CI server. Not worth having a resource-intensive test for this kind of an edge cases. Fixes: nodejs#42719 Signed-off-by: Darshan Sen <raisinten@gmail.com> PR-URL: nodejs#42720 Fixes: nodejs#42719 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Beth Griggs <bgriggs@redhat.com> Reviewed-By: Stewart X Addison <sxa@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Dossar
pushed a commit
to Dossar/node
that referenced
this issue
May 26, 2022
It was disconnecting the runners from the CI server. Not worth having a resource-intensive test for this kind of an edge cases. Fixes: nodejs#42719 Signed-off-by: Darshan Sen <raisinten@gmail.com> PR-URL: nodejs#42720 Fixes: nodejs#42719 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Beth Griggs <bgriggs@redhat.com> Reviewed-By: Stewart X Addison <sxa@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Dossar
pushed a commit
to Dossar/node
that referenced
this issue
May 26, 2022
It was disconnecting the runners from the CI server. Not worth having a resource-intensive test for this kind of an edge cases. Fixes: nodejs#42719 Signed-off-by: Darshan Sen <raisinten@gmail.com> PR-URL: nodejs#42720 Fixes: nodejs#42719 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Beth Griggs <bgriggs@redhat.com> Reviewed-By: Stewart X Addison <sxa@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol
pushed a commit
that referenced
this issue
May 31, 2022
It was disconnecting the runners from the CI server. Not worth having a resource-intensive test for this kind of an edge cases. Fixes: #42719 Signed-off-by: Darshan Sen <raisinten@gmail.com> PR-URL: #42720 Fixes: #42719 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Beth Griggs <bgriggs@redhat.com> Reviewed-By: Stewart X Addison <sxa@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol
pushed a commit
that referenced
this issue
Jun 1, 2022
It was disconnecting the runners from the CI server. Not worth having a resource-intensive test for this kind of an edge cases. Fixes: #42719 Signed-off-by: Darshan Sen <raisinten@gmail.com> PR-URL: #42720 Backport-PR-URL: #42967 Fixes: #42719 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Beth Griggs <bgriggs@redhat.com> Reviewed-By: Stewart X Addison <sxa@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
BethGriggs
pushed a commit
that referenced
this issue
Jun 1, 2022
It was disconnecting the runners from the CI server. Not worth having a resource-intensive test for this kind of an edge cases. Fixes: #42719 Signed-off-by: Darshan Sen <raisinten@gmail.com> PR-URL: #42720 Backport-PR-URL: #42967 Fixes: #42719 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Beth Griggs <bgriggs@redhat.com> Reviewed-By: Stewart X Addison <sxa@redhat.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
The problem doesn't seem completely fixed. New test crashes sometimes on freebsd:
https://ci.nodejs.org/job/node-test-commit-freebsd/43628/
https://ci.nodejs.org/job/node-test-commit-freebsd/43633/
Originally posted by @targos in #42409 (comment)
The text was updated successfully, but these errors were encountered: