| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Review requested:
|
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
@rluvaton the new tests seem to be failing https://ci.nodejs.org/job/node-test-commit-linux/nodes=fedora-latest-x64/53007/consoleText not ok 7 - test-runner/output/timeout_in_before_each_should_not_affect_further_tests.js
---
duration_ms: 772.821225
failureType: 'testCodeFailure'
error: |-
Expected values to be strictly equal:
+ actual - expected ... Lines skipped
'gonna timeout\n' +
'TAP version 13\n' +
...
'# Subtest: after each timeout\n' +
' # Subtest: second describe first test\n' +
+ ' ok 1 - second describe first test\n' +
- ' not ok 1 - second describe first test\n' +
' ---\n' +
' duration_ms: *\n' +
+ ' ...\n' +
+ ' # Subtest: second describe second test\n' +
+ ' ok 2 - second describe second test\n' +
+ ' ---\n' +
+ ' duration_ms: *\n' +
- " failureType: 'hookFailed'\n" +
- " error: 'failed running afterEach hook'\n" +
- " code: 'ERR_TEST_FAILURE'\n" +
- ' stack: |-\n' +
- ' async Promise.all (index 0)\n' +
' ...\n' +
+ ' 1..2\n' +
+ 'ok 2 - after each timeout\n' +
+ ' ---\n' +
+ ' duration_ms: *\n' +
+ " type: 'suite'\n" +
+ ' ...\n' +
+ '1..2\n' +
+ '# tests 4\n' +
+ '# suites 2\n' +
+ '# pass 3\n' +
+ '# fail 1\n' +
- ' # Subtest: second describe second test\n' +
- ' ok 2 - second describe second test\n' +
- ' ---\n' +
- ' duration_ms: *\n' +
- ' ...\n' +
- ' 1..2\n' +
- 'not ok 2 - after each timeout\n' +
- ' ---\n' +
- ' duration_ms: *\n' +
- " type: 'suite'\n" +
- " failureType: 'subtestsFailed'\n" +
- " error: '1 subtest failed'\n" +
- " code: 'ERR_TEST_FAILURE'\n" +
- ' ...\n' +
- '1..2\n' +
- '# tests 4\n' +
- '# suites 2\n' +
- '# pass 2\n' +
- '# fail 2\n' +
'# cancelled 0\n' +
'# skipped 0\n' +
'# todo 0\n' +
'# duration_ms *\n'
code: 'ERR_ASSERTION'
name: 'AssertionError'
expected: |-
gonna timeout
TAP version 13
not gonna timeout
before each test second
after each test first
gonna timeout
# Subtest: before each timeout
# Subtest: first describe first test
not ok 1 - first describe first test
---
duration_ms: *
failureType: 'hookFailed'
error: 'failed running beforeEach hook'
code: 'ERR_TEST_FAILURE'
stack: |-
async Promise.all (index 0)
...
# Subtest: first describe second test
ok 2 - first describe second test
---
duration_ms: *
...
1..2
not ok 1 - before each timeout
---
duration_ms: *
type: 'suite'
failureType: 'subtestsFailed'
error: '1 subtest failed'
code: 'ERR_TEST_FAILURE'
...
after each test second
not gonna timeout
# Subtest: after each timeout
# Subtest: second describe first test
not ok 1 - second describe first test
---
duration_ms: *
failureType: 'hookFailed'
error: 'failed running afterEach hook'
code: 'ERR_TEST_FAILURE'
stack: |-
async Promise.all (index 0)
...
# Subtest: second describe second test
ok 2 - second describe second test
---
duration_ms: *
...
1..2
not ok 2 - after each timeout
---
duration_ms: *
type: 'suite'
failureType: 'subtestsFailed'
error: '1 subtest failed'
code: 'ERR_TEST_FAILURE'
...
1..2
# tests 4
# suites 2
# pass 2
# fail 2
# cancelled 0
# skipped 0
# todo 0
# duration_ms *
actual: |-
gonna timeout
TAP version 13
not gonna timeout
before each test second
after each test first
gonna timeout
# Subtest: before each timeout
# Subtest: first describe first test
not ok 1 - first describe first test
---
duration_ms: *
failureType: 'hookFailed'
error: 'failed running beforeEach hook'
code: 'ERR_TEST_FAILURE'
stack: |-
async Promise.all (index 0)
...
# Subtest: first describe second test
ok 2 - first describe second test
---
duration_ms: *
...
1..2
not ok 1 - before each timeout
---
duration_ms: *
type: 'suite'
failureType: 'subtestsFailed'
error: '1 subtest failed'
code: 'ERR_TEST_FAILURE'
...
after each test second
not gonna timeout
# Subtest: after each timeout
# Subtest: second describe first test
ok 1 - second describe first test
---
duration_ms: *
...
# Subtest: second describe second test
ok 2 - second describe second test
---
duration_ms: *
...
1..2
ok 2 - after each timeout
---
duration_ms: *
type: 'suite'
...
1..2
# tests 4
# suites 2
# pass 3
# fail 1
# cancelled 0
# skipped 0
# todo 0
# duration_ms *
operator: 'strictEqual'
stack: |-
assertSnapshot (/home/iojs/build/workspace/node-test-commit-linux/test/common/assertSnapshot.js:38:12)
async Module.spawnAndAssert (/home/iojs/build/workspace/node-test-commit-linux/test/common/assertSnapshot.js:66:3)
async TestContext.<anonymous> (file:///home/iojs/build/workspace/node-test-commit-linux/test/parallel/test-runner-output.mjs:66:5)
async Test.run (node:internal/test_runner/test:582:9)
async Promise.all (index 6)
async Suite.run (node:internal/test_runner/test:849:7)
async startSubtest (node:internal/test_runner/harness:204:3)
...
|
Sorry, something went wrong.
|
@atlowChemi This is really weird as it passed in the GitHub Actions CI and locally... Is there any difference between Jenkins and GitHub Actions |
Sorry, something went wrong.
IMHO if we know it is flaky we should attempt to fix it and avoid merging a flaky test 🙂 |
Sorry, something went wrong.
I truly don't know enough to answer that. What I can say is searching for test runner output in all the Github actions showed no results EDIT: OK, took the time to have a look at this 🙂 node/.github/workflows/test-linux.yml Line 4 in 4b3d964 Lines 578 to 579 in 4b3d964 Lines 545 to 559 in 4b3d964 Lines 511 to 515 in 4b3d964
|
Sorry, something went wrong.
|
Thank you @atlowChemi for the detailed explanation! |
Sorry, something went wrong.
|
@atlowChemi JS_SUITES is default - that does include parallel tests. |
Sorry, something went wrong.
so it is running? |
Sorry, something went wrong.
of course, just wanna know what I'm dealing with... if it's flaky running 1K times would help fail the test locally, if not then other things should be done... |
Sorry, something went wrong.
That is defined in test.py? Thanks for clarifying 🙂 |
Sorry, something went wrong.
yes, here: Lines 1562 to 1563 in 48345d0 it doesn't show up since the reporter/process indicator used (via -p actions) prints just dots, and the test passed in gh actions. |
Sorry, something went wrong.
PR-URL: nodejs#48925 Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
PR-URL: nodejs#48925 Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
PR-URL: nodejs#48925 Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
PR-URL: #48925 Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
PR-URL: nodejs#48925 Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
|
Due to fact, #48877 didn't land cleanly on v20.x-staging. This PR somehow, depends on it. So we'll need a manual backport. Reference: https://github.com/nodejs/node/blob/main/doc/contributing/backporting-to-release-lines.md |
Sorry, something went wrong.
Sorry, something went wrong.
PR-URL: nodejs#48925 Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
PR-URL: #48925 Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
PR-URL: nodejs/node#48925 Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
PR-URL: nodejs/node#48925 Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
| Back | FazBrowse Home | New Git URL |
Fix #48917