test: mark test-watch-mode* as flaky on all platforms · nodejs/node@82e6043 · GitHub

nodejs / node Public

• Notifications You must be signed in to change notification settings
• Fork 36.6k
• Star 120k

• Code
• Issues 635
• Pull requests 754
• Actions
• Projects
• Security and quality
• Insights

Additional navigation options

Commit 82e6043

Browse filesBrowse the repository at this point in the historyBrowse files

p-b-o

authored and

RafaelGSS

committed

test: mark test-watch-mode* as flaky on all platforms

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: #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>

1 parent 26a2ae2 commit 82e6043
Copy full SHA for 82e6043

1 file changed

+3Lines changed: 3 additions & 0 deletions

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

• test/sequential
  • sequential.status

Expand file treeCollapse file tree

Open diff view settings

Collapse file

‎test/sequential/sequential.status‎

Copy file name to clipboardExpand all lines: test/sequential/sequential.status

+3Lines changed: 3 additions & 0 deletions

Original file line number	Diff line number	Diff line change
@@ -7,6 +7,9 @@ prefix sequential
7	7	[true] # This section applies to all platforms
8	8	# https://github.com/nodejs/node/issues/27611#issuecomment-613100468
9	9	test-cpu-prof-dir-worker: PASS, FLAKY
	10	+ # https://github.com/nodejs/node/issues/44898
	11	+ test-watch-mode: PASS, FLAKY
	12	+ test-watch-mode-inspect: PASS, FLAKY
10	13
11	14	[$system==win32]
12	15

0 commit comments

Comments

0 (0)