1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
nodejs/test/sequential/sequential.status

64 lines
2.1 KiB
Plaintext
Raw Normal View History

test: add test configuration templates Template configuration files for marking tests as flaky. PR-URL: https://github.com/nodejs/node/pull/2424 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: João Reis <reis@janeasystems.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
2015-08-18 14:04:14 +02:00
prefix sequential
# To mark a test as flaky, list the test name in the appropriate section
# below, without ".js", followed by ": PASS,FLAKY". Example:
# sample-test : PASS,FLAKY
[true] # This section applies to all platforms
test: mark cpu-prof-dir-worker flaky on all Refs: https://github.com/nodejs/node/issues/27611#issuecomment-613100468 PR-URL: https://github.com/nodejs/node/pull/32828 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
2020-04-13 14:12:31 -07:00
# https://github.com/nodejs/node/issues/27611#issuecomment-613100468
test-cpu-prof-dir-worker: PASS, FLAKY
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: https://github.com/nodejs/node/pull/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>
2022-10-20 11:06:09 +02:00
# https://github.com/nodejs/node/issues/44898
test-watch-mode: PASS, FLAKY
test-watch-mode-inspect: PASS, FLAKY
test: mark test-http2-large-file as flaky Refs: https://github.com/nodejs/node/issues/47409 PR-URL: https://github.com/nodejs/node/pull/51549 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz.nizipli@sentry.io>
2024-01-25 12:59:53 +01:00
# https://github.com/nodejs/node/issues/47409
test-http2-large-file: PASS, FLAKY
test: add test configuration templates Template configuration files for marking tests as flaky. PR-URL: https://github.com/nodejs/node/pull/2424 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: João Reis <reis@janeasystems.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
2015-08-18 14:04:14 +02:00
[$system==win32]
test: mark test-http-max-sockets as flaky on win32 Refs: https://github.com/nodejs/node/issues/47116 PR-URL: https://github.com/nodejs/node/pull/47134 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Beth Griggs <bethanyngriggs@gmail.com>
2023-03-17 17:33:03 +01:00
# https://github.com/nodejs/node/issues/47116
test-http-max-sockets: PASS, FLAKY
test: set sea snapshot tests as flaky PR-URL: https://github.com/nodejs/node/pull/50223 Refs: https://github.com/nodejs/node/issues/49630 Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
2023-10-18 10:05:39 -04:00
# https://github.com/nodejs/node/issues/49630
test-single-executable-application-snapshot: PASS, FLAKY
test-single-executable-application-snapshot-and-code-cache: PASS, FLAKY
test: set `test-http2-large-file` as flaky PR-URL: https://github.com/nodejs/node/pull/54802 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Matthew Aitken <maitken033380023@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
2024-09-06 11:00:34 -04:00
# https://github.com/nodejs/node/issues/47409
test-http2-large-file: PASS, FLAKY
test: add test configuration templates Template configuration files for marking tests as flaky. PR-URL: https://github.com/nodejs/node/pull/2424 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: João Reis <reis@janeasystems.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
2015-08-18 14:04:14 +02:00
[$system==linux]
[$system==macos]
[$system==solaris] # Also applies to SmartOS
[$system==freebsd]
test: disable fs watch tests for AIX fs watch currently needs special configuration on AIX and we want to improve under https://github.com/nodejs/node/issues/5085. Tests are disabled so CI can be green and we can spot other regressions until this work is complete. test-async-wrap-check-providers does not aim to test fs watch but part of the test uses it so that part has been skipped for AIX PR-URL: https://github.com/nodejs/node/pull/5187 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
2016-02-10 15:56:26 -05:00
[$system==aix]
test: unskip tests that now pass on AIX One skipped test remains, it creates very large Buffer objects, triggering the AIX OOM to kill node and its parent processes. See: https://github.com/nodejs/build/issues/1849#issuecomment-514414165 PR-URL: https://github.com/nodejs/node/pull/29054 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
2019-08-08 11:01:42 -07:00
# https://github.com/nodejs/node/pull/29054
test: skip tests related to CI failures on AIX These tests seem to trigger failures in the entire CI job (not just the test) on AIX. Skip them to see if that helps alleviate spurious failures in node-test-commit-aix (and the upstream PR and commit test jobs). See: - https://github.com/nodejs/build/issues/1820#issuecomment-505998851 - https://github.com/nodejs/build/issues/1847#issuecomment-504210708 PR-URL: https://github.com/nodejs/node/pull/28469 Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
2019-06-28 09:36:30 -07:00
test-buffer-creation-regression: SKIP
test: mark `test-http2-session-timeout` as flake on ARM PR-URL: https://github.com/nodejs/node/pull/23639 Refs: https://github.com/nodejs/node/issues/20628 Reviewed-By: Rich Trott <rtrott@gmail.com>
2018-10-13 10:20:02 -04:00
test: skip the unsupported test cases for IBM i This is a following PR of #30714. PR-URL: https://github.com/nodejs/node/pull/30819 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
2019-12-06 01:08:57 -06:00
[$system==ibmi]
# https://github.com/nodejs/node/pull/29054
test-buffer-creation-regression: SKIP
# https://github.com/nodejs/node/pull/30819
test-perf-hooks: SKIP
test: exclude ibm i tests until we resolve Refs: https://github.com/nodejs/node/issues/39683 These are being worked, but we really should have marked flaky a long time ago in ordert to make then nightlies non-red. Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: https://github.com/nodejs/node/pull/41812 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
2022-02-01 10:15:05 -05:00
# https://github.com/nodejs/node/issues/39683
test-tls-psk-client: PASS, FLAKY
test-tls-securepair-client: PASS, FLAKY
test: skip the unsupported test cases for IBM i This is a following PR of #30714. PR-URL: https://github.com/nodejs/node/pull/30819 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
2019-12-06 01:08:57 -06:00
test: mark `test-http2-session-timeout` as flake on ARM PR-URL: https://github.com/nodejs/node/pull/23639 Refs: https://github.com/nodejs/node/issues/20628 Reviewed-By: Rich Trott <rtrott@gmail.com>
2018-10-13 10:20:02 -04:00
[$arch==arm]
test: set `test-watch-mode-inspect` as flaky PR-URL: https://github.com/nodejs/node/pull/50259 Refs: https://github.com/nodejs/node/issues/49933 Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Vinícius Lourenço Claro Cardoso <contact@viniciusl.com.br>
2023-10-22 16:10:41 -04:00
# https://github.com/nodejs/node/issues/49933
test: skip test-watch-mode-inspect on arm Refs: https://github.com/nodejs/node/issues/49933 - SKIP instead of mark FLAKY as tests seems to fail builds through left over processe Signed-off-by: Michael Dawson <midawson@redhat.com> PR-URL: https://github.com/nodejs/node/pull/51210 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
2023-12-21 23:35:41 -05:00
test-watch-mode-inspect: SKIP
test: mark test-performance-eventloopdelay flaky Refs: https://github.com/nodejs/node/issues/41286 This is one of the remaining high indicende failures in the CI. Mark as flaky while it is investigated. Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: https://github.com/nodejs/node/pull/41409 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
2022-01-05 20:14:28 -05:00
[$arch==s390x]
# https://github.com/nodejs/node/issues/41286
test-performance-eventloopdelay: PASS, FLAKY
test: mark SEA tests as flaky on PowerPC PR-URL: https://github.com/nodejs/node/pull/50750 Refs: https://github.com/nodejs/node/issues/50740 Refs: https://github.com/nodejs/reliability/issues/718 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
2023-11-15 19:14:57 +01:00
test: fix flaky conditions for ppc64 SEA tests In test status files, `$system` will be the OS and not the arch (which would be `$arch`). Add missing single-executable-application test to the list of tests marked flaky on Linux ppc64le. PR-URL: https://github.com/nodejs/node/pull/51422 Refs: https://github.com/nodejs/node/pull/50828 Refs: https://github.com/nodejs/node/issues/50740 Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz.nizipli@sentry.io> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
2024-01-11 12:31:14 +00:00
[$system==linux && $arch==ppc64]
test: mark SEA tests as flaky on PowerPC PR-URL: https://github.com/nodejs/node/pull/50750 Refs: https://github.com/nodejs/node/issues/50740 Refs: https://github.com/nodejs/reliability/issues/718 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
2023-11-15 19:14:57 +01:00
# https://github.com/nodejs/node/issues/50740
sea: support sea.getRawAsset() This patch adds support for `sea.getRawAsset()` which is similar to `sea.getAsset()` but returns the raw asset in an array buffer without copying. Users should avoid writing to the returned array buffer. If the injected section is not marked as writable or not aligned, writing to the raw asset is likely to result in a crash. PR-URL: https://github.com/nodejs/node/pull/50960 Refs: https://github.com/nodejs/single-executable/issues/68 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
2023-11-28 18:58:15 +01:00
test-single-executable-application-assets-raw: PASS, FLAKY
sea: support embedding assets With this patch: Users can now include assets by adding a key-path dictionary to the configuration as the `assets` field. At build time, Node.js would read the assets from the specified paths and bundle them into the preparation blob. In the generated executable, users can retrieve the assets using the `sea.getAsset()` and `sea.getAssetAsBlob()` API. ```json { "main": "/path/to/bundled/script.js", "output": "/path/to/write/the/generated/blob.blob", "assets": { "a.jpg": "/path/to/a.jpg", "b.txt": "/path/to/b.txt" } } ``` The single-executable application can access the assets as follows: ```cjs const { getAsset } = require('node:sea'); // Returns a copy of the data in an ArrayBuffer const image = getAsset('a.jpg'); // Returns a string decoded from the asset as UTF8. const text = getAsset('b.txt', 'utf8'); // Returns a Blob containing the asset. const blob = getAssetAsBlob('a.jpg'); ``` Drive-by: update the documentation to include a section dedicated to the injected main script and refer to it as "injected main script" instead of "injected module" because it's a script, not a module. PR-URL: https://github.com/nodejs/node/pull/50960 Refs: https://github.com/nodejs/single-executable/issues/68 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
2023-11-14 19:13:03 +01:00
test-single-executable-application-assets: PASS, FLAKY
test: fix flaky conditions for ppc64 SEA tests In test status files, `$system` will be the OS and not the arch (which would be `$arch`). Add missing single-executable-application test to the list of tests marked flaky on Linux ppc64le. PR-URL: https://github.com/nodejs/node/pull/51422 Refs: https://github.com/nodejs/node/pull/50828 Refs: https://github.com/nodejs/node/issues/50740 Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Yagiz Nizipli <yagiz.nizipli@sentry.io> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
2024-01-11 12:31:14 +00:00
test-single-executable-application-disable-experimental-sea-warning: PASS, FLAKY
test: mark SEA tests as flaky on PowerPC PR-URL: https://github.com/nodejs/node/pull/50750 Refs: https://github.com/nodejs/node/issues/50740 Refs: https://github.com/nodejs/reliability/issues/718 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
2023-11-15 19:14:57 +01:00
test-single-executable-application-empty: PASS, FLAKY
test-single-executable-application-snapshot-and-code-cache: PASS, FLAKY
test-single-executable-application-snapshot: PASS, FLAKY
test-single-executable-application-use-code-cache: PASS, FLAKY
test-single-executable-application: PASS, FLAKY
Reference in New Issue Copy Permalink