Uh oh!
There was an error while loading. Please reload this page.
[v16.x backport] test runner additions - #44873
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
targos
commented
Oct 3, 2022
If possible, we prefer to keep separated commits in backports, so we know from the git log what landed in the release line |
b6d316e to
f44fcd9CompareMoLow
commented
Oct 3, 2022
@targos I am not sure what you meant - but you commented before I have committed. I just wanted to have a backport pr URL before cherry-picking the relevant commits. |
targos
commented
Oct 3, 2022
@MoLow Looks like I was too fast indeed. This looks ok 👍🏻 (btw, you can add the Backport-PR-URL yourself, but that would be already done automatically when we land it with |
f44fcd9 to
d351059CompareMoLow
commented
Oct 3, 2022
v16 linter seems broken regardless of this PR |
d351059 to
23ab7feCompare
@juanarbol it seems to be broken since the last push to |
PR-URL: nodejs#44520 Backport-PR-URL: nodejs#44873 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
PR-URL: nodejs#44620 Backport-PR-URL: nodejs#44873Fixes: nodejs#44600 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
PR-URL: nodejs#44592 Backport-PR-URL: nodejs#44873 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
ea19306 to
36be71eComparenodejs-github-bot
commented
Nov 23, 2022
MoLow
commented
Nov 24, 2022
@richardlau CI is running #44873 (comment) |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
nodejs-github-bot
commented
Nov 24, 2022
nodejs-github-bot
commented
Nov 27, 2022
This was confirmed flaky on those platforms: - Windows x64 - Windows on Arm - Linux - Freebsd Tests randomly fail because of bad order in messages expected, which seems related to threads scheduling at execution. PR-URL: nodejs#45049 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
nodejs-github-bot
commented
Nov 30, 2022
nodejs-github-bot
commented
Dec 1, 2022
MoLow
commented
Dec 1, 2022
@richardlau can this be merged? |
richardlau
commented
Dec 7, 2022
Landed in 5a776d4...821d832. |
backports:
--test#44241duration_msto be milliseconds #44450--inspectwith--test#44520