Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI Reliability 2022-09-08 #371

Open
12 tasks
github-actions bot opened this issue Sep 8, 2022 · 0 comments
Open
12 tasks

CI Reliability 2022-09-08 #371

github-actions bot opened this issue Sep 8, 2022 · 0 comments

Comments

@github-actions
Copy link

github-actions bot commented Sep 8, 2022

Failures in node-test-pull-request/46375 to node-test-pull-request/46467 that failed more than 2 PRs
(Generated with ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2022-09-08 00:18 4 6 25 7 58 6.74%

Jenkins Failure

Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 9 (nodejs/node#44473, nodejs/node#44366, nodejs/node#44379, nodejs/node#44327, nodejs/node#44480, nodejs/node#44479, nodejs/node#44427, nodejs/node#44412, nodejs/node#44247)
Appeared test-equinix-ubuntu2004_container-armv7l-2, test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46375/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46461/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 145.40.99.31/145.40.99.31:51854' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
	at jdk.proxy2/jdk.proxy2.$Proxy87.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1215)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1207)

Git Failure

Reason ERROR: Error fetching remote repo 'origin'
Type GIT_FAILURE
Failed PR 2 (nodejs/node#44473, nodejs/node#44366)
Appeared test-osuosl-rhel8-ppc64_le-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46375/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46381/
Example
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from git@github.com:nodejs/node.git
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:1003)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1244)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1308)
	at hudson.scm.SCM.checkout(SCM.java:540)

Build Failure

Reason ERROR: Build step failed with exception
Type BUILD_FAILURE
Failed PR 6 (nodejs/node#44500, nodejs/node#44509, nodejs/node#44366, nodejs/node#44387, nodejs/node#44392, nodejs/node#44496)
Appeared test-equinix-ubuntu2004_container-armv7l-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46396/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46423/
Example
ERROR: Build step failed with exception
java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave[test-equinix-ubuntu2004_container-armv7l-2] which is computer hudson.slaves.SlaveComputer@4a73d9df and has channel null
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:114)
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:92)
	at org.jenkinsci.plugins.postbuildscript.processor.Processor.processBuildSteps(Processor.java:180)
	at org.jenkinsci.plugins.postbuildscript.processor.Processor.processScripts(Processor.java:91)

Reason dtrace: failed to compile script src/v8ustack.d: Preprocessor failed to process input program
Type BUILD_FAILURE
Failed PR 4 (nodejs/node#44530, nodejs/node#44247, nodejs/node#44358, nodejs/node#44521)
Appeared test-joyent-smartos20-x64-3, test-joyent-smartos20-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/46442/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46447/
Example
dtrace: failed to compile script src/v8ustack.d: Preprocessor failed to process input program

Reason ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 3 (nodejs/node#44418, nodejs/node#44412, nodejs/node#44376)
Appeared test-equinix-debian10_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-2, test-equinix-debian10_container-armv7l-1, test-equinix-ubuntu1804_sharedlibs_container-arm64-3, test-osuosl-aix72-ppc64_be-3, test-equinix-rhel8_container-arm64-1, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu2004_container-arm64-2, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46394/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46467/
Example
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
[PostBuildScript] - [INFO] Executing post build scripts.
[node-test-binary-armv7l] $ /bin/bash -ex /tmp/jenkins16479718837328816378.sh
+ '[' -d .git ']'
+ git clean -fdx

Reason error: remote GitHub already exists.
Type BUILD_FAILURE
Failed PR 3 (nodejs/node#44524, nodejs/node#44488, nodejs/node#44412)
Appeared test-rackspace-win2012r2_vs2017-x64-1, test-rackspace-win2012r2_vs2019-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/46433/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46458/
Example
error: remote GitHub already exists.

> git fetch --prune --no-tags GitHub 

> git fetch --prune --no-tags https://github.com/nodejs/build.git +refs/heads/main:refs/remotes/jenkins_tmp

Reason Error: module '_bootlocale' has no attribute 'getpreferredencoding'
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#44412, nodejs/node#44524)
Appeared test-rackspace-win2012r2_vs2017-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/46430/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46433/
Example
Error: module '_bootlocale' has no attribute 'getpreferredencoding'
  [716] Failed to execute script clcache_main
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(423,5): error MSB6006: "clcache_main.exe" exited with code -1. [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_libplatform.vcxproj]
  http_parser.c
  zlib.vcxproj -> ..\..\out\Release\lib\zlib.lib
  http_parser.vcxproj -> ..\..\out\Release\lib\http_parser.lib

JSTest Failure

Reason parallel/test-bootstrap-modules
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#44530, nodejs/node#44358, nodejs/node#44247, nodejs/node#44521)
Appeared undefined
First CI https://ci.nodejs.org/job/node-test-pull-request/46442/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46457/
Example
not ok 400 parallel/test-bootstrap-modules
  ---
  duration_ms: 0.422
  severity: fail
  exitcode: 1
  stack: |-
    (node:31892) internal/test/binding: These APIs are for internal testing only. Do not use them.
    (Use `node --trace-warnings ...` to show where the warning was created)
    
    node:internal/event_target:1006
      process.nextTick(() => { throw err; });
                               ^
    AssertionError [ERR_ASSERTION]: These modules were unexpectedly loaded:
      NativeModule diagnostics_channel
    
        at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-custom-suites-freestyle/test/parallel/test-bootstrap-modules.js:251:8)
        at Module._compile (node:internal/modules/cjs/loader:1119:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1173:10)
        at Module.load (node:internal/modules/cjs/loader:997:32)
        at Module._load (node:internal/modules/cjs/loader:838:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/mo...

Reason parallel/test-watch-mode
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#44366, nodejs/node#44247, nodejs/node#44358, nodejs/node#44536)
Appeared test-orka-macos10.15-x64-1, test-orka-macos11-x64-2, test-digitalocean-freebsd12-x64-2, test-softlayer-alpine311_container-x64-1, test-digitalocean-alpine312_container-x64-2, test-rackspace-debian10-x64-1, test-rackspace-fedora32-x64-1, test-digitalocean-fedora34-x64-2, test-ibm-rhel8-x64-1, test-digitalocean-ubuntu1804-x64-1, test-equinix-debian10_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-2, test-osuosl-rhel8-ppc64_le-4, test-softlayer-ubi81_container-x64-1, test-softlayer-ubuntu1804_sharedlibs_container-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-6, test-digitalocean-ubuntu1804_sharedlibs_container-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-digitalocean-ubuntu1804_sharedlibs_container-x64-4, test-softlayer-ubuntu1804_sharedlibs_container-x64-4, test-digitalocean-ubuntu1804_sharedlibs_container-x64-8, test-equinix-rhel8_container-arm64-1, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu2004_container-arm64-2, test-equinix-ubuntu2004_container-armv7l-1, test-ibm-rhel8-s390x-4, test-osuosl-aix72-ppc64_be-2, test-nearform-macos11.0-arm64-1, test-equinix-ubuntu1804_sharedlibs_container-arm64-2, test-azure_msft-win10_vs2019-x64-3, test-rackspace-win2012r2_vs2013-x64-1, undefined, test-azure_msft-win10_vs2019-x64-2, test-rackspace-win2012r2_vs2019-x64-5, test-azure_msft-win10_vs2019-x64-4, test-rackspace-win2012r2_vs2019-x64-4, test-osuosl-aix72-ppc64_be-3, test-softlayer-ubuntu1804_sharedlibs_container-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/46409/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46449/
Example
not ok 3382 parallel/test-watch-mode
  ---
  duration_ms: 120.64
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    TAP version 13
    # Subtest: watch mode
        # Subtest: should watch changes to a file - event loop ended
        ok 1 - should watch changes to a file - event loop ended
          ---
          duration_ms: 460.322248
          ...


Reason wpt/test-webcrypto
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44486, nodejs/node#44500, nodejs/node#44327)
Appeared test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46384/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46401/
Example
not ok 898 wpt/test-webcrypto
  ---
  duration_ms: 720.980
  severity: fail
  exitcode: 1
  stack: |-
    timeout
    ---- algorithm-discards-context.https.window.js ----
    [SKIPPED] Not relevant in Node.js context
    ---- historical.any.js ----
    [SKIPPED] Not relevant in Node.js context
    ---- idlharness.https.any.js ----
    [SKIPPED] Various non-IDL-compliant things
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    [PASS] setup - define tests
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    [PASS] X25519 good parameters
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    [PASS] X25519 mixed case parameters
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    [PASS] X25519 with null length
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    [PASS] X25519 short result
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    [PASS] X25519 non-multiple of 8 bits
    ---- derive_bits_keys\cfrg_curves_bits.https.any.js ----
    ...

Reason addons/request-interrupt/test
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44493, nodejs/node#44412)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/46390/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46404/
Example
not ok 3450 addons/request-interrupt/test
  ---
  duration_ms: 300.127
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-heapsnapshot-near-heap-limit-worker
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44498, nodejs/node#44543)
Appeared test-orka-macos11-x64-1, test-ibm-rhel8-s390x-1
First CI https://ci.nodejs.org/job/node-test-pull-request/46427/
Last CI https://ci.nodejs.org/job/node-test-pull-request/46453/
Example
not ok 942 parallel/test-heapsnapshot-near-heap-limit-worker
  ---
  duration_ms: 5.152
  severity: fail
  exitcode: 1
  stack: |-
    
    Invoked NearHeapLimitCallback, processing=false, current_limit=52428800, initial_limit=52428800
    max_young_gen_size=50331648, young_gen_size=0, old_gen_size=51044080, total_size=51044080
    Estimated available memory=6793760768, estimated overhead=50331648
    Start generating Heap.20220906.132207.52234.1.001.heapsnapshot...
    Wrote snapshot to /Users/iojs/node-tmp/.tmp.923/Heap.20220906.132207.52234.1.001.heapsnapshot
    
    <--- Last few GCs --->
    
    [52234:0x7f8e989f6000]     3759 ms: Mark-sweep (reduce) 48.5 (52.0) -> 48.5 (51.8) MB, 11.9 / 0.0 ms  (average mu = 0.365, current mu = -0.022) heap profiler; GC in old space requested
    
    
    <--- JS stacktrace --->
    
    FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
     1: 0x1031ab415 node::Abort() [/Users/iojs/build/workspace/node-test-comm...

Progress

  • Backing channel 'JNLP4-connect connection from ... is disconnected. (9)
  • ERROR: Error fetching remote repo 'origin' (2)
  • ERROR: Build step failed with exception (6)
  • dtrace: failed to compile script src/v8ustack.d: Preprocessor failed to process input program (4)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (3)
  • error: remote GitHub already exists. (3)
  • Error: module '_bootlocale' has no attribute 'getpreferredencoding' (2)
  • parallel/test-bootstrap-modules (4)
  • parallel/test-watch-mode (4)
  • wpt/test-webcrypto (3)
  • addons/request-interrupt/test (2)
  • parallel/test-heapsnapshot-near-heap-limit-worker (2)
nodejs-github-bot pushed a commit to nodejs/node that referenced this issue Sep 11, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: #44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Fyko pushed a commit to Fyko/node that referenced this issue Sep 15, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: nodejs#44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 26, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: #44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 26, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: #44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
RafaelGSS pushed a commit to nodejs/node that referenced this issue Sep 26, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: #44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 4, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: #44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 4, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: #44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 4, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: #44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 7, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: #44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
panva pushed a commit to panva/node that referenced this issue Oct 9, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: nodejs#44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 10, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: #44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 10, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
PR-URL: #44574
Backport-PR-URL: #44872
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 11, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: #44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
juanarbol pushed a commit to nodejs/node that referenced this issue Oct 11, 2022
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
PR-URL: #44574
Backport-PR-URL: #44872
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: nodejs/node#44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
PR-URL: nodejs/node#44574
Backport-PR-URL: nodejs/node#44872
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

PR-URL: nodejs/node#44574
Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
guangwong pushed a commit to noslate-project/node that referenced this issue Jan 3, 2023
We run all WPT from one subset in the same process using workers.
As the number of the tests grow, it can take longer to run some of the
subsets, but it's still overall faster than running them in different
processes. This patch increases the timeout
for WPT to prevent the test from failing because it takes longer
to run (even though it would still complete at some point).

Refs: nodejs/reliability#371
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
PR-URL: nodejs/node#44574
Backport-PR-URL: nodejs/node#44872
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants