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-01-23 #180

Open
13 tasks
github-actions bot opened this issue Jan 23, 2022 · 0 comments
Open
13 tasks

CI Reliability 2022-01-23 #180

github-actions bot opened this issue Jan 23, 2022 · 0 comments

Comments

@github-actions
Copy link

Failures in node-test-pull-request/41994 to node-test-pull-request/42091 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-01-23 00:07 1 10 28 3 58 10.42%

Jenkins Failure

Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 6 (nodejs/node#41513, nodejs/node#41615, nodejs/node#41263, nodejs/node#41511, nodejs/node#41573, nodejs/node#41619)
Appeared test-equinix-ubuntu1804_sharedlibs_container-arm64-1, test-softlayer-alpine311_container-x64-1, test-softlayer-centos7-x64-1, test-softlayer-ubi81_container-x64-1, test-softlayer-ubuntu1804_sharedlibs_container-x64-1, test-joyent-smartos20-x64-3, test-rackspace-win2012r2_vs2019-x64-3, test-requireio_securogroup-debian10-arm64_pi3-2, test-requireio_williamkapke-debian10-arm64_pi3-1, test-requireio_pivotalagency-debian10-arm64_pi3-2, test-requireio_davglass-debian10-arm64_pi3-1, test-joyent-smartos20-x64-4, test-requireio_svincent-debian10-armv7l_pi2-3, test-requireio_securogroup-debian10-arm64_pi3-1, test-requireio_mininodes-debian10-armv7l_pi2-1, test-requireio_williamkapke-debian10-arm64_pi3-2, test-requireio_jasnell-debian10-armv7l_pi2-1, test-requireio_piccoloaiutante-debian10-arm64_pi3-1, test-requireio_mcollina-debian10-armv7l_pi2-1, test-requireio_joeyvandijk-debian10-armv7l_pi2-1, test-equinix-centos7_container-arm64-2, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu2004_container-arm64-2, test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/41994/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42054/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 145.40.81.219/145.40.81.219:58660' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:216)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286)
	at com.sun.proxy.$Proxy82.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1213)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1205)

Reason Build timed out (after 60 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 2 (nodejs/node#40424, nodejs/node#40907)
Appeared test-rackspace-win2012r2_vs2019-x64-1, test-softlayer-ubi81_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42011/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42015/
Example
Build timed out (after 60 minutes). Marking the build as failed.

Build Failure

Reason ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#41553, nodejs/node#41263)
Appeared test-requireio_ceejbot-debian10-armv7l_pi2-1, test-requireio_davglass-debian10-arm64_pi3-1, test-requireio_joeyvandijk-debian10-armv7l_pi2-2, test-requireio_securogroup-debian10-arm64_pi3-1, test-requireio_svincent-debian10-armv7l_pi2-2, test-requireio_williamkapke-debian10-arm64_pi3-2, test-requireio_mininodes-debian10-armv7l_pi2-1, test-requireio_piccoloaiutante-debian10-arm64_pi3-1, test-requireio_rvagg-debian10-armv7l_pi2-1, test-requireio_securogroup-debian10-arm64_pi3-2, test-requireio_mcollina-debian10-armv7l_pi2-1, test-requireio_pivotalagency-debian10-arm64_pi3-2, test-requireio_svincent-debian10-armv7l_pi2-3, test-requireio_jasnell-debian10-armv7l_pi2-1, test-requireio_williamkapke-debian10-arm64_pi3-1, test-requireio_joeyvandijk-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42023/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42028/
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-arm] $ /bin/bash -ex /tmp/jenkins8013646566027941732.sh
+ '[' -d .git ']'
+ git clean -fdx

Reason ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#41263, nodejs/node#41511)
Appeared test-rackspace-fedora32-x64-1, test-joyent-ubuntu1804-x64-1, test-rackspace-centos7-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42051/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42052/
Example
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for node-test-commit-linux/nodes=fedora-last-latest-x64 #44378
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

Reason error: remote GitHub already exists.
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#40907, nodejs/node#41610)
Appeared test-rackspace-win2012r2_vs2017-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42015/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42040/
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/master:refs/remotes/jenkins_tmp

JSTest Failure

Reason sequential/test-cpu-prof-worker-argv
Type JS_TEST_FAILURE
Failed PR 7 (nodejs/node#41511, nodejs/node#41573, nodejs/node#41623, nodejs/node#41586, nodejs/node#41642, nodejs/node#41600, nodejs/node#41620)
Appeared test-digitalocean-freebsd12-x64-2, test-orka-macos11-x64-2, test-digitalocean-freebsd12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42052/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42089/
Example
not ok 3464 sequential/test-cpu-prof-worker-argv
  ---
  duration_ms: 0.641
  severity: fail
  exitcode: 1
  stack: |-
    
    [
      {
        id: 1,
        callFrame: {
          functionName: '(root)',
          scriptId: '0',
          url: '',
          lineNumber: -1,
          columnNumber: -1
        },
        hitCount: 0,
        children: [ 2, 3, 15, 16, 25, 26 ]
      },
      {
        id: 2,
        callFrame: {
          functionName: '(program)',
          scriptId: '0',
          url: '',
          lineNumber: -1,
          columnNumber: -1
        },
        hitCount: 0
      },
      {
        id: 3,
        callFrame: {
          functionName: '',
          scriptId: '10',
          url: 'node:internal/bootstrap/node',
          lineNumber: 0,
          columnNumber: 0
        },
        hitCount: 0,
        children: [ 4 ]
      },
      {
        id: 4,
        callFrame: {
          functionName: 'nativeModuleRequire',
          scriptId: '9',
          url: 'node:internal/bootstrap/...

Reason parallel/test-common-expect-warning
Type JS_TEST_FAILURE
Failed PR 6 (nodejs/node#40424, nodejs/node#41571, nodejs/node#41263, nodejs/node#41596, nodejs/node#41604, nodejs/node#41301)
Appeared test-equinix-centos7_container-arm64-2, test-equinix-ubuntu2004_container-arm64-2, test-equinix-ubuntu2004_container-armv7l-1, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu2004_sharedlibs_container-arm64-4, test-equinix-ubuntu1804_sharedlibs_container-arm64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/42011/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42077/
Example
not ok 320 parallel/test-common-expect-warning
  ---
  duration_ms: 0.528
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:1026
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The input did not match the regular expression /Unexpected extra warning received/. Input:
    
    ''
    
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/parallel/test-common-expect-warning.js:41:14)
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/common/index.js:401:15)
        at ChildProcess.emit (node:events:522:28)
        at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: '',
      expected: /Unexpected extra warning received/,
      operator: 'match'
    }
    
    Node.js v18.0.0-pre
  ...


Reason parallel/test-stdout-to-file
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#41571, nodejs/node#41502, nodejs/node#41573, nodejs/node#41623, nodejs/node#41612)
Appeared test-azure_msft-win10_vs2019-x64-1, test-azure_msft-win10_vs2019-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/42024/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42088/
Example
not ok 585 parallel/test-stdout-to-file
  ---
  duration_ms: 1.559
  severity: fail
  exitcode: 1
  stack: |-
    1048576 chars to C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt...
    done!
    C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt has 1048576 bytes
    Done printing with string
    1048576 chars to C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt...
    done!
    C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt has 1048576 bytes
    Done printing with buffer
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571
    Files blocking: [ 'stdout.txt' ]
    
    C:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:54
        throw e;
        ^
    
    Error: EPERM: operation not permitted, lstat '\\?\C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt'
        at lstatSync (node:fs:1516:3)
        at r...

Reason parallel/test-child-process-pipe-dataflow
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#40424, nodejs/node#41571, nodejs/node#41263, nodejs/node#41612)
Appeared test-azure_msft-win10_vs2019-x64-4, test-rackspace-win2012r2_vs2015-x64-2, test-rackspace-win2012r2_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/42018/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42074/
Example
not ok 788 parallel/test-child-process-pipe-dataflow
  ---
  duration_ms: 120.360
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...


Reason parallel/test-fs-rmdir-recursive
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#41493, nodejs/node#41599, nodejs/node#41612)
Appeared test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win10_vcbt2015-x64-4, test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42012/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42070/
Example
not ok 259 parallel/test-fs-rmdir-recursive
  ---
  duration_ms: 0.625
  severity: fail
  exitcode: 1
  stack: |-
    (node:11120) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead
    (Use `node --trace-deprecation ...` to show where the warning was created)
    node:internal/process/promises:265
                triggerUncaughtException(err, true /* fromPromise */);
                ^
    
    [Error: ENOTEMPTY: directory not empty, rmdir 'C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.256\rmdir-recursive-4\d-3-2\d-2-2\d-1-2'] {
      errno: -4051,
      code: 'ENOTEMPTY',
      syscall: 'rmdir',
      path: 'C:\\workspace\\node-test-binary-windows-js-suites\\node\\test\\.tmp.256\\rmdir-recursive-4\\d-3-2\\d-2-2\\d-1-2'
    }
    
    Node.js v18.0.0-pre
  ...


Reason parallel/test-crypto-dh-constructor
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#41513, nodejs/node#41263)
Appeared test-requireio_jasnell-debian10-armv7l_pi2-1, test-requireio_ceejbot-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/41994/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42051/
Example
not ok 207 parallel/test-crypto-dh-constructor
  ---
  duration_ms: 240.238
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-crypto-dh-leak
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#41502, nodejs/node#41620)
Appeared test-requireio_davglass-debian10-arm64_pi3-1, test-requireio_williamkapke-debian10-arm64_pi3-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42009/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42089/
Example
not ok 276 parallel/test-crypto-dh-leak
  ---
  duration_ms: 240.65
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-crypto-secure-heap
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#41511, nodejs/node#41604)
Appeared test-requireio_rvagg-debian10-armv7l_pi2-1, test-requireio_ceejbot-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42052/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42069/
Example
not ok 245 parallel/test-crypto-secure-heap
  ---
  duration_ms: 240.146
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Git Failure

Progress

  • Backing channel 'JNLP4-connect connection from ... is disconnected. (6)
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
  • ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ... (2)
  • error: remote GitHub already exists. (2)
  • sequential/test-cpu-prof-worker-argv (7)
  • parallel/test-common-expect-warning (6)
  • parallel/test-stdout-to-file (5)
  • parallel/test-child-process-pipe-dataflow (4)
  • parallel/test-fs-rmdir-recursive (3)
  • parallel/test-crypto-dh-constructor (2)
  • parallel/test-crypto-dh-leak (2)
  • parallel/test-crypto-secure-heap (2)
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