nodejs / nodejs/reliability

CI Reliability 2020-08-11

Aperta
#40 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Lingua principale
Shell
Stelle
57
Fork
20
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Failures in node-test-pull-request/32620 to node-test-pull-request/32713 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
2020-08-11 00:34 2 46 1 7 44 50.55%
Jenkins Failure
Git Failure
Build Failure
Reason fatal error: ld terminated with signal 9 [Killed]
Type BUILD_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/34461/, https://github.com/nodejs/node/pull/34482/, https://github.com/nodejs/node/pull/34659/, https://github.com/nodejs/node/pull/34700/)
Appeared test-joyent-ubuntu1804_sharedlibs_container-x64-3, test-joyent-ubuntu1804_sharedlibs_container-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/32626/
Last CI https://ci.nodejs.org/job/node-test-pull-request/32697/
Example
fatal error: ld terminated with signal 9 [Killed]

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/34625/, https://github.com/nodejs/node/pull/34378/)
Appeared test-requireio_kahwee-debian10-arm64_pi3-1, test-requireio_ceejbot-debian10-armv7l_pi2-1, test-requireio_piccoloaiutante-debian10-arm64_pi3-1, test-requireio_svincent-debian10-armv7l_pi2-2, test-requireio_pivotalagency-debian10-arm64_pi3-2, test-requireio_joeyvandijk-debian10-armv7l_pi2-1, test-requireio_pivotalagency-debian10-arm64_pi3-1, test-requireio_jasnell-debian10-armv7l_pi2-1, test-requireio_williamkapke-debian10-arm64_pi3-1, test-requireio_sambthompson-debian10-armv7l_pi2-1, test-requireio_rvagg-debian10-armv7l_pi2-1, test-requireio_joeyvandijk-debian10-armv7l_pi2-2, test-ibm-rhel7-s390x-4
First CI https://ci.nodejs.org/job/node-test-pull-request/32652/
Last CI https://ci.nodejs.org/job/node-test-pull-request/32703/
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/jenkins470673952733424910.sh
+ '[' -d .git ']'
+ git clean -fdx

Reason Error: Not supported
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/34625/, https://github.com/nodejs/node/pull/34643/)
Appeared test-joyent-smartos18-x64-3, test-rackspace-centos7-x64-1, test-softlayer-debian9-x64-1, test-rackspace-fedora27-x64-1, test-rackspace-ubuntu1604-x64-1, test-joyent-ubuntu1804_sharedlibs_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/32639/
Last CI https://ci.nodejs.org/job/node-test-pull-request/32642/
Example
Error: Not supported
    at vm:module(0):1:1
    at SourceTextModule.evaluate (internal/vm/module.js:224:23)
    at embedder_main_6.js:1:328
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:705115) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

Reason Failed to trigger node-test-commit
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/34629/, https://github.com/nodejs/node/pull/34676/)
Appeared test-ibm-ubuntu1804-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/32633/
Last CI https://ci.nodejs.org/job/node-test-pull-request/32681/
Example
Failed to trigger node-test-commit

Reason fatal: No rebase in progress?
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/34689/, https://github.com/nodejs/node/pull/34625/)
Appeared test-orka-macos10.14-x64-1, test-nearform-macos10.15-x64-2, test-orka-macos10.14-x64-2, test-orka-macos10.15-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/32694/
Last CI https://ci.nodejs.org/job/node-test-pull-request/32711/
Example
fatal: No rebase in progress?

JSTest Failure
Reason parallel/test-repl
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/34648/, https://github.com/nodejs/node/pull/34582/, https://github.com/nodejs/node/pull/34664/)
Appeared test-requireio_piccoloaiutante-debian10-arm64_pi3-1, test-joyent-ubuntu1804-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/32646/
Last CI https://ci.nodejs.org/job/node-test-pull-request/32671/
Example
not ok 493 parallel/test-repl
  ---
  duration_ms: 7.769
  severity: fail
  exitcode: 1
  stack: |-
    out: ""
    in: ""
    out: "message"
    in: "'Read, Eval, Print Loop'"
    out: "invoke_me(987)"
    in: "'invoked 987'"
    out: "a = 12345"
    in: "12345"
    out: "{a:1}"
    in: "{ a: 1 }"
    out: "throw new Error('test error');"
    in: "Uncaught Error: test error"
    out: "throw { foo: 'bar' };"
    in: "Uncaught { foo: 'bar' }"
    out: "function test_func() {"
    in: "... "
    out: ".break"
    in: ""
    out: "eval(\"function test_func() {\")"
    in: "Uncaught SyntaxError: Unexpected end of input"
    out: "`io.js"
    in: "... "
    out: ".break"
    in: ""
    out: "`io.js ${\"1.0\""
    in: "... "
    out: "+ \".2\"}`"
    in: "'io.js 1.0.2'"
    out: "`io.js ${"
    in: "... "
    out: "\"1.0\" + \".2\"}`"
    in: "'io.js 1.0.2'"
    out: "(\"a\""
    in: "... "
    out: ".charAt(0))"
    in: "'a'"
    out: ".1234"
    in: "0.1234"
    out: ".1+.1"
    in: "0.2"
    out: "JSON.parse('{\...

Reason node-api/test_worker_terminate_finalization/test
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/33013/, https://github.com/nodejs/node/pull/34625/)
Appeared test-requireio_sambthompson-debian10-armv7l_pi2-1, test-requireio_pivotalagency-debian10-arm64_pi3-2, test-requireio_pivotalagency-debian10-arm64_pi3-1, test-requireio_joeyvandijk-debian10-armv7l_pi2-2, test-requireio_piccoloaiutante-debian10-arm64_pi3-1, test-requireio_kahwee-debian10-arm64_pi3-1
First CI https://ci.nodejs.org/job/node-test-pull-request/32674/
Last CI https://ci.nodejs.org/job/node-test-pull-request/32712/
Example
not ok 116 node-api/test_worker_terminate_finalization/test
  ---
  duration_ms: 2.45
  severity: fail
  exitcode: 1
  stack: |-
    events.js:291
          throw er; // Unhandled 'error' event
          ^
    
    AssertionError [ERR_ASSERTION]: function should not have been called at /home/iojs/build/workspace/node-test-binary-arm/test/node-api/test_worker_terminate_finalization/test.js:7
    called with arguments: [Error: Invalid argument]
        at Worker.mustNotCall (/home/iojs/build/workspace/node-test-binary-arm/test/common/index.js:425:12)
        at Worker.emit (events.js:314:20)
        at Worker.[kOnErrorMessage] (internal/worker.js:241:10)
        at Worker.[kOnMessage] (internal/worker.js:251:37)
        at MessagePort.<anonymous> (internal/worker.js:167:57)
        at MessagePort.[nodejs.internal.kHybridDispatch] (internal/event_target.js:352:41)
        at MessagePort.exports.emitMessage (internal/per_context/messageport.js:18:26)
    Emitted 'error' event on process instance at:
        at em...

Reason parallel/test-async-hooks-http-parser-destroy
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/34664/, https://github.com/nodejs/node/pull/34662/)
Appeared test-rackspace-win2012r2_vs2017-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/32663/
Last CI https://ci.nodejs.org/job/node-test-pull-request/32666/
Example
not ok 745 parallel/test-async-hooks-http-parser-destroy
  ---
  duration_ms: 120.152
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...


Reason parallel/test-http-destroyed-socket-write2
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/34629/, https://github.com/nodejs/node/pull/34662/)
Appeared test-orka-macos10.14-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/32634/
Last CI https://ci.nodejs.org/job/node-test-pull-request/32666/
Example
not ok 1760 parallel/test-http-destroyed-socket-write2
  ---
  duration_ms: 120.103
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-worker-init-failure
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/34625/, https://github.com/nodejs/node/pull/34672/)
Appeared test-nearform-macos10.15-x64-1, test-orka-macos10.15-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/32673/
Last CI https://ci.nodejs.org/job/node-test-pull-request/32679/
Example
not ok 2469 parallel/test-worker-init-failure
  ---
  duration_ms: 2.469
  severity: fail
  exitcode: 1
  stack: |-
    child stdout: 
    
    child stderr: events.js:291
          throw er; // Unhandled 'error' event
          ^
    
    AssertionError [ERR_ASSERTION]: The input did not match the regular expression /EMFILE/. Input:
    
    'ENOENT: no such file or directory, uv_cwd'
    
        at Worker.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/parallel/test-worker-init-failure.js:38:14)
        at Worker.emit (events.js:314:20)
        at Worker.[kOnErrorMessage] (internal/worker.js:241:10)
        at Worker.[kOnMessage] (internal/worker.js:251:37)
        at MessagePort.<anonymous> (internal/worker.js:167:57)
        at MessagePort.[nodejs.internal.kHybridDispatch] (internal/event_target.js:352:41)
        at MessagePort.exports.emitMessage (internal/per_context/messageport.js:18:26)
        at Worker.[kOnExit] (internal/worker.js:223:5)
        at Worker.<compute...

Reason wasi/test-wasi
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/34622/, https://github.com/nodejs/node/pull/33929/)
Appeared test-digitalocean-freebsd11-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/32632/
Last CI https://ci.nodejs.org/job/node-test-pull-request/32644/
Example
not ok 8 wasi/test-wasi
  ---
  duration_ms: 2.927
  severity: fail
  exitcode: 1
  stack: |-
    executing cant_dotdot
    (node:90112) ExperimentalWarning: WASI is an experimental feature. This feature could change at any time
    (Use `node --trace-warnings ...` to show where the warning was created)
    fd_prestat_get(3, 69720)
    fd_prestat_dir_name(3, 131088, 9)
    fd_prestat_get(4, 69720)
    fd_prestat_dir_name(4, 131152, 5)
    fd_prestat_get(5, 69720)
    environ_sizes_get(69724, 69720)
    environ_get(134464, 131168)
    fd_fdstat_get(3, 69672)
    path_open(3, 1, 1033, 14, 0, 264240830, 268435455, 0, 69668)
    
    executing clock_getres
    (node:90113) ExperimentalWarning: WASI is an experimental feature. This feature could change at any time
    (Use `node --trace-warnings ...` to show where the warning was created)
    fd_prestat_get(3, 69688)
    fd_prestat_dir_name(3, 131088, 9)
    fd_prestat_get(4, 69688)
    fd_prestat_dir_name(4, 131152, 5)
    fd_prestat_get(5, 69688)
    environ_siz...

Progress
  • fatal error: ld terminated with signal 9 [Killed] (4)
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
  • Error: Not supported (2)
  • Failed to trigger node-test-commit (2)
  • fatal: No rebase in progress? (2)
  • parallel/test-repl (3)
  • node-api/test_worker_terminate_finalization/test (2)
  • parallel/test-async-hooks-http-parser-destroy (2)
  • parallel/test-http-destroyed-socket-write2 (2)
  • parallel/test-worker-init-failure (2)
  • wasi/test-wasi (2)

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Inizia con il report ncu-ci walk pr --stats=true e le esecuzioni Jenkins collegate, quindi confronta gli errori di build e dei test JavaScript elencati. L’issue non indica file sorgente né una correzione richiesta; per considerarla conclusa sarebbe necessario concordare una correzione e verificare che i job CI interessati non riproducano più gli errori.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
git, javascript, node.js, shell
Ambito
ci-cd, devops, infrastructure, testing-qa
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.