CI Reliability 2022-01-20

オープン
#177 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
20/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
停滞
技術スタック
javascript, node.js, shell

調査の方向性

生成された ncu-ci レポートと、一覧にある CI コンソールの例、特に test/parallel/test-fs-rmdir-recursive、test/parallel/test-common-expect-warning、test/parallel/test-fs-readfile から始めてください。どの失敗が再現可能かを追跡し、影響を受けるジョブ全体で繰り返し発生している CI の失敗がいつ解消されるかを特定してください。

索引モデルが issue の本文から書いたものです。

説明

Failures in node-test-pull-request/41939 to node-test-pull-request/42035 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-20 00:07 1 3 25 1 70 3.06%
JSTest Failure
Reason parallel/test-fs-rmdir-recursive
Type JS_TEST_FAILURE
Failed PR 10 (https://github.com/nodejs/node/pull/41414/, https://github.com/nodejs/node/pull/41412/, https://github.com/nodejs/node/pull/41408/, https://github.com/nodejs/node/pull/41323/, https://github.com/nodejs/node/pull/41571/, https://github.com/nodejs/node/pull/41517/, https://github.com/nodejs/node/pull/41276/, https://github.com/nodejs/node/pull/41566/, https://github.com/nodejs/node/pull/41493/, https://github.com/nodejs/node/pull/41599/)
Appeared 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/41953/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42031/
Example
not ok 259 parallel/test-fs-rmdir-recursive
  ---
  duration_ms: 0.820
  severity: fail
  exitcode: 1
  stack: |-
    (node:20232) [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)
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.256
    Files blocking: [ 'rmdir-recursive-0', 'rmdir-recursive-4', 'rmdir-recursive-5' ]
    
    node:assert:991
        throw newErr;
        ^
    
    AssertionError [ERR_ASSERTION]: ifError got unwanted exception: ENOTEMPTY: directory not empty, rmdir 'C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.256\rmdir-recursive-0\d-3-2\d-2-1\d-1-1'
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:364:12
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:401:15
        at node:fs:18...

Reason parallel/test-common-expect-warning
Type JS_TEST_FAILURE
Failed PR 8 (https://github.com/nodejs/node/pull/41545/, https://github.com/nodejs/node/pull/41424/, https://github.com/nodejs/node/pull/41276/, https://github.com/nodejs/node/pull/41553/, https://github.com/nodejs/node/pull/40424/, https://github.com/nodejs/node/pull/41571/, https://github.com/nodejs/node/pull/41263/, https://github.com/nodejs/node/pull/41596/)
Appeared test-equinix-ubuntu2004_container-arm64-2, test-equinix-ubuntu2004_sharedlibs_container-arm64-4, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu1804_sharedlibs_container-arm64-3, test-equinix-ubuntu1804_sharedlibs_container-arm64-1, test-equinix-centos7_container-arm64-2, test-equinix-ubuntu1804_sharedlibs_container-arm64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/41949/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42032/
Example
not ok 318 parallel/test-common-expect-warning
  ---
  duration_ms: 0.473
  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-fs-readfile
Type JS_TEST_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/41412/, https://github.com/nodejs/node/pull/41408/, https://github.com/nodejs/node/pull/41276/, https://github.com/nodejs/node/pull/41569/, https://github.com/nodejs/node/pull/41517/)
Appeared test-rackspace-win2012r2_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/41954/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41977/
Example
not ok 259 parallel/test-fs-readfile
  ---
  duration_ms: 0.945
  severity: fail
  exitcode: 1
  stack: |-
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.251
    Files blocking: [
      '.removeme-fs-readfile-6028-1K.txt',
      '.removeme-fs-readfile-6028-1M.txt',
      '.removeme-fs-readfile-6028-1MPlusOne.txt',
      '.removeme-fs-readfile-6028-64K.txt',
      '.removeme-fs-readfile-6028-64KLessOne.txt'
    ]
    
    node:internal/fs/utils:344
        throw err;
        ^
    
    Error: ENOSPC: no space left on device, ftruncate
        at Object.ftruncateSync (node:fs:1078:3)
        at Object.truncateSync (node:fs:1037:14)
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-fs-readfile.js:61:6)
        at Module._compile (node:internal/modules/cjs/loader:1097:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
        at Module.load (node:internal/modules/cjs/loader:975:32)
   ...

Reason parallel/test-trace-events-fs-sync
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/41570/, https://github.com/nodejs/node/pull/41408/, https://github.com/nodejs/node/pull/41566/, https://github.com/nodejs/node/pull/41487/)
Appeared test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win10_vs2019-x64-4, test-azure_msft-win10_vcbt2015-x64-4, test-azure_msft-win10_vcbt2015-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/41946/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41984/
Example
not ok 690 parallel/test-trace-events-fs-sync
  ---
  duration_ms: 2.473
  severity: fail
  exitcode: 1
  stack: |-
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.682
    Files blocking: [ 'fs.txt', 'node_trace.1.log' ]
    
    C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-trace-events-fs-sync.js:133
        throw new Error(`${tr}:\n${util.inspect(proc)}`);
        ^
    
    Error: fs.sync.fstat:
    {
      status: 1,
      signal: null,
      output: [
        null,
        '',
        'node:internal/fs/utils:344\r\n' +
          '    throw err;\r\n' +
          '    ^\r\n' +
          '\r\n' +
          "Error: EPERM: operation not permitted, open 'fs.txt'\r\n" +
          '    at Object.openSync (node:fs:585:3)\r\n' +
          '    at Object.writeFileSync (node:fs:2155:35)\r\n' +
          '    at [eval]:1:4\r\n' +
          '    at Script.runInThisContext (node:vm:129:12)\r\n' +
          '    at Object.runInThisContext (node:vm:305:38)...

Reason parallel/test-child-process-pipe-dataflow
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/40424/, https://github.com/nodejs/node/pull/41571/, https://github.com/nodejs/node/pull/41263/)
Appeared 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/42029/
Example
not ok 815 parallel/test-child-process-pipe-dataflow
  ---
  duration_ms: 120.128
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...


Reason parallel/test-crypto-dh-odd-key
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/41545/, https://github.com/nodejs/node/pull/41493/, https://github.com/nodejs/node/pull/40622/)
Appeared test-requireio_svincent-debian10-armv7l_pi2-2, test-requireio_svincent-debian10-armv7l_pi2-3, test-requireio_mininodes-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/41941/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42027/
Example
not ok 224 parallel/test-crypto-dh-odd-key
  ---
  duration_ms: 240.77
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason node-api/test_threadsafe_function/test
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41571/, https://github.com/nodejs/node/pull/41276/)
Appeared test-equinix-centos7_container-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/41947/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41981/
Example
not ok 3341 node-api/test_threadsafe_function/test
  ---
  duration_ms: 240.100
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-crypto-dh-constructor
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/38590/, https://github.com/nodejs/node/pull/41513/)
Appeared test-requireio_ceejbot-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/41956/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41994/
Example
not ok 206 parallel/test-crypto-dh-constructor
  ---
  duration_ms: 240.136
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-crypto-secure-heap
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41571/, https://github.com/nodejs/node/pull/41569/)
Appeared test-requireio_jasnell-debian10-armv7l_pi2-1, test-requireio_svincent-debian10-armv7l_pi2-2
First CI https://ci.nodejs.org/job/node-test-pull-request/41971/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41976/
Example
not ok 208 parallel/test-crypto-secure-heap
  ---
  duration_ms: 240.60
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-http-outgoing-end-cork
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41502/, https://github.com/nodejs/node/pull/41603/)
Appeared test-requireio_pivotalagency-debian10-arm64_pi3-2, test-requireio_mcollina-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/41943/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42035/
Example
not ok 301 parallel/test-http-outgoing-end-cork
  ---
  duration_ms: 3.484
  severity: fail
  exitcode: 1
  stack: |-
    Sending req no 1
    assert.js:166
      throw err;
      ^
    
    AssertionError [ERR_ASSERTION]: () => {
        reject(new Error('Request timed out'));
      } at /home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-http-outgoing-end-cork.js:53
        at Timeout.mustNotCall [as _onTimeout] (/home/iojs/build/workspace/node-test-binary-arm/test/common/index.js:458:12)
        at listOnTimeout (internal/timers.js:557:17)
        at processTimers (internal/timers.js:500:7) {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
      actual: undefined,
      expected: undefined,
      operator: 'fail'
    }
  ...


Reason parallel/test-stdout-to-file
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41566/, https://github.com/nodejs/node/pull/41571/)
Appeared test-azure_msft-win10_vs2019-x64-4, test-azure_msft-win10_vs2019-x64-1, test-azure_msft-win10_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/41957/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42024/
Example
not ok 588 parallel/test-stdout-to-file
  ---
  duration_ms: 1.948
  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 pummel/test-fs-largefile
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41566/, https://github.com/nodejs/node/pull/41493/)
Appeared test-rackspace-win2012r2_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/41988/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42012/
Example
not ok 793 pummel/test-fs-largefile
  ---
  duration_ms: 0.941
  severity: fail
  exitcode: 1
  stack: |-
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.793
    Files blocking: [ 'large.txt' ]
    
    node:internal/fs/utils:344
        throw err;
        ^
    
    Error: ENOSPC: no space left on device, ftruncate
        at Object.ftruncateSync (node:fs:1078:3)
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\pummel\test-fs-largefile.js:37:4)
        at Module._compile (node:internal/modules/cjs/loader:1097:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
        at Module.load (node:internal/modules/cjs/loader:975:32)
        at Function.Module._load (node:internal/modules/cjs/loader:822:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
        at node:internal/main/run_main_module:17:47 {
      errno: -4055,
      syscall: 'ftruncate',
     ...

Jenkins Failure
Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/41566/, https://github.com/nodejs/node/pull/41572/, https://github.com/nodejs/node/pull/41545/, https://github.com/nodejs/node/pull/41513/)
Appeared test-digitalocean-freebsd12-x64-2, test-digitalocean-freebsd12-x64-1, test-equinix-ubuntu2004_container-armv7l-1, test-azure_msft-win10_vs2019-x64-4, test-equinix-centos7_container-arm64-2, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu2004_container-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/41940/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41994/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 107.170.28.213/107.170.28.213:22973' 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 (https://github.com/nodejs/node/pull/40424/, https://github.com/nodejs/node/pull/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 (https://github.com/nodejs/node/pull/41553/, https://github.com/nodejs/node/pull/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: The process with PID 7792 (child process of PID 7176) could not be terminated.
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41571/, https://github.com/nodejs/node/pull/41493/)
Appeared test-rackspace-win2012r2_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/41959/
Last CI https://ci.nodejs.org/job/node-test-pull-request/41973/
Example
ERROR: The process with PID 7792 (child process of PID 7176) could not be terminated.
Reason: There is no running instance of the task.

> taskkill /t /f /fi "IMAGENAME eq cctest.exe" 

INFO: No tasks running with the specified criteria.

undefined
Reason Unknown
Type undefined
Failed PR 15 (https://github.com/nodejs/node/pull/41545/, https://github.com/nodejs/node/pull/41424/, https://github.com/nodejs/node/pull/38590/, https://github.com/nodejs/node/pull/41571/, https://github.com/nodejs/node/pull/41493/, https://github.com/nodejs/node/pull/41569/, https://github.com/nodejs/node/pull/41276/, https://github.com/nodejs/node/pull/41513/, https://github.com/nodejs/node/pull/40424/, https://github.com/nodejs/node/pull/41502/, https://github.com/nodejs/node/pull/41553/, https://github.com/nodejs/node/pull/41595/, https://github.com/nodejs/node/pull/40622/, https://github.com/nodejs/node/pull/41263/, https://github.com/nodejs/node/pull/41603/)
Appeared test-equinix-ubuntu2004_container-armv7l-1, test-equinix-ubuntu2004_sharedlibs_container-arm64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/41941/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42035/
Example
Unknown

Git Failure
Progress
  • parallel/test-fs-rmdir-recursive (10)
  • parallel/test-common-expect-warning (8)
  • parallel/test-fs-readfile (5)
  • parallel/test-trace-events-fs-sync (4)
  • parallel/test-child-process-pipe-dataflow (3)
  • parallel/test-crypto-dh-odd-key (3)
  • node-api/test_threadsafe_function/test (2)
  • parallel/test-crypto-dh-constructor (2)
  • parallel/test-crypto-secure-heap (2)
  • parallel/test-http-outgoing-end-cork (2)
  • parallel/test-stdout-to-file (2)
  • pummel/test-fs-largefile (2)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (4)
  • 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: The process with PID 7792 (child process of PID 7176) could not be terminated. (2)
  • Unknown (15)
主要言語
Shell
スター
57
フォーク
20
PR マージ指標
30日以内にマージされた PR はありません

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

nodejs/reliability のほかの issue

nodejs/reliability の issue をすべて見る

似ている issue

Shell/Bash の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。