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 failures: 20190612-20190615 #23

Closed
joyeecheung opened this issue Jun 16, 2019 · 4 comments
Closed

CI failures: 20190612-20190615 #23

joyeecheung opened this issue Jun 16, 2019 · 4 comments

Comments

@joyeecheung
Copy link
Member

joyeecheung commented Jun 16, 2019

Failures in node-test-pull-request/23814 to node-test-pull-request/23911 that failed more than 2 PRs
(Generated with ncu-ci walk pr --stats=true --cache=true --markdown results.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2019-06-16 15:36 0 1 44 1 54 1.01%

JSTest Failure

Reason parallel/test-tls-cli-min-version-1.1
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#27850, nodejs/node#28021, nodejs/node#28006, nodejs/node#20077, nodejs/node#28209)
Appeared test-softlayer-ubuntu1604_sharedlibs_container-x64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/23836/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23869/
Example
not ok 1812 parallel/test-tls-cli-min-version-1.1
  ---
  duration_ms: 0.416
  severity: fail
  exitcode: 1
  stack: |-
    openssl 1.1.0j
    default min TLSv1.1 max TLSv1.2
    test: U U U U U SSLv2_method expect U U ERR_TLS_INVALID_PROTOCOL_METHOD
        (/home/iojs/build/workspace/node-test-commit-linux-containered/test/parallel/test-tls-min-max-version.js:111:1)
    client undefined
    server SSLv2 methods disabled
    test: U U U U U SSLv3_method expect U U ERR_TLS_INVALID_PROTOCOL_METHOD
        (/home/iojs/build/workspace/node-test-commit-linux-containered/test/parallel/test-tls-min-max-version.js:113:1)
    client undefined
    server SSLv3 methods disabled
    test: U U U U U hokey-pokey expect U U ERR_TLS_INVALID_PROTOCOL_METHOD
        (/home/iojs/build/workspace/node-test-commit-linux-containered/test/parallel/test-tls-min-max-version.js:121:1)
    client undefined
    server Unknown method
    test: U U U U TLSv1.2 TLS1_2_method expect U U ERR_TLS_PROTOCOL_VERSION_CONFLICT
        (/home/iojs/...

Reason parallel/test-tls-cli-min-version-1.2
Type JS_TEST_FAILURE
Failed PR 5 (nodejs/node#27850, nodejs/node#28021, nodejs/node#28006, nodejs/node#20077, nodejs/node#28209)
Appeared test-softlayer-ubuntu1604_sharedlibs_container-x64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/23836/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23869/
Example
not ok 1817 parallel/test-tls-cli-min-version-1.2
  ---
  duration_ms: 0.436
  severity: fail
  exitcode: 1
  stack: |-
    openssl 1.1.0j
    default min TLSv1.2 max TLSv1.2
    test: U U U U U SSLv2_method expect U U ERR_TLS_INVALID_PROTOCOL_METHOD
        (/home/iojs/build/workspace/node-test-commit-linux-containered/test/parallel/test-tls-min-max-version.js:111:1)
    client undefined
    server SSLv2 methods disabled
    test: U U U U U SSLv3_method expect U U ERR_TLS_INVALID_PROTOCOL_METHOD
        (/home/iojs/build/workspace/node-test-commit-linux-containered/test/parallel/test-tls-min-max-version.js:113:1)
    client undefined
    server SSLv3 methods disabled
    test: U U U U U hokey-pokey expect U U ERR_TLS_INVALID_PROTOCOL_METHOD
        (/home/iojs/build/workspace/node-test-commit-linux-containered/test/parallel/test-tls-min-max-version.js:121:1)
    client undefined
    server Unknown method
    test: U U U U TLSv1.2 TLS1_2_method expect U U ERR_TLS_PROTOCOL_VERSION_CONFLICT
        (/home/iojs/...

Reason parallel/test-cpu-prof-dir-and-name
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#28179, nodejs/node#28150, nodejs/node#28234, nodejs/node#28189)
Appeared test-digitalocean-freebsd11-x64-2, test-digitalocean-freebsd11-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/23826/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23910/
Example
not ok 350 parallel/test-cpu-prof-dir-and-name
  ---
  duration_ms: 0.451
  severity: fail
  exitcode: 1
  stack: |-
    Dispatching message { "id": 1, "method": "Profiler.enable" }
    Receive CPU profile message, ending = false
    Dispatching message { "id": 2, "method": "Profiler.start" }
    Receive CPU profile message, ending = false
    Dispatching message { "id": 3, "method": "Profiler.setSamplingInterval", "params": { "interval": 50 } }
    Receive CPU profile message, ending = false
    EndStartedProfilers
    Ending cpu profiling
    Dispatching message { "id": 4, "method": "Profiler.stop" }
    Receive CPU profile message, ending = true
    Written result to /usr/home/iojs/node-tmp/.tmp.0/prof/test.cpuprofile
    
    [
      {
        id: 1,
        callFrame: {
          functionName: '(root)',
          scriptId: '0',
          url: '',
          lineNumber: -1,
          columnNumber: -1
        },
        hitCount: 0,
        children: [ 2, 3 ]
      },
      {
        id: 2,
        callFram...

Reason parallel/test-cpu-prof-dir-worker
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#27850, nodejs/node#28207, nodejs/node#28179, nodejs/node#28232)
Appeared test-digitalocean-freebsd11-x64-2, test-digitalocean-freebsd11-x64-1, test-softlayer-ubuntu1604_sharedlibs_container-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/23836/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23892/
Example
not ok 353 parallel/test-cpu-prof-dir-worker
  ---
  duration_ms: 0.647
  severity: fail
  exitcode: 1
  stack: |-
    Dispatching message { "id": 1, "method": "Profiler.enable" }
    Receive CPU profile message, ending = false
    Dispatching message { "id": 2, "method": "Profiler.start" }
    Receive CPU profile message, ending = false
    Dispatching message { "id": 3, "method": "Profiler.setSamplingInterval", "params": { "interval": 50 } }
    Receive CPU profile message, ending = false
    Dispatching message { "id": 1, "method": "Profiler.enable" }
    Receive CPU profile message, ending = false
    Dispatching message { "id": 2, "method": "Profiler.start" }
    Receive CPU profile message, ending = false
    Dispatching message { "id": 3, "method": "Profiler.setSamplingInterval", "params": { "interval": 50 } }
    Receive CPU profile message, ending = false
    EndStartedProfilers
    Ending cpu profiling
    Dispatching message { "id": 4, "method": "Profiler.stop" }
    Receive CPU profile message, en...

Reason parallel/test-cpu-prof-worker-argv
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#27850, nodejs/node#28224, nodejs/node#28155, nodejs/node#27791)
Appeared test-digitalocean-ubuntu1604_sharedlibs_container-x64-3, test-digitalocean-freebsd11-x64-2, test-softlayer-ubuntu1604_sharedlibs_container-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/23836/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23911/
Example
not ok 415 parallel/test-cpu-prof-worker-argv
  ---
  duration_ms: 1.592
  severity: fail
  exitcode: 1
  stack: |-
    
    [
      {
        id: 1,
        callFrame: {
          functionName: '(root)',
          scriptId: '0',
          url: '',
          lineNumber: -1,
          columnNumber: -1
        },
        hitCount: 0,
        children: [ 2, 3, 43, 55 ]
      },
      {
        id: 2,
        callFrame: {
          functionName: '(program)',
          scriptId: '0',
          url: '',
          lineNumber: -1,
          columnNumber: -1
        },
        hitCount: 2
      },
      {
        id: 3,
        callFrame: {
          functionName: '',
          scriptId: '8',
          url: 'internal/bootstrap/node.js',
          lineNumber: 0,
          columnNumber: 0
        },
        hitCount: 1,
        children: [ 4, 9, 13, 14, 32 ],
        positionTicks: [ [Object] ]
      },
      {
        id: 4,
        callFrame: {
          functionName: 'setupPrepareStackTrace',
          scriptId: '8',...

Reason parallel/test-stdout-close-catch
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#28150, nodejs/node#28102, nodejs/node#28224, nodejs/node#28206)
Appeared test-digitalocean-freebsd11-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/23827/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23902/
Example
not ok 1946 parallel/test-stdout-close-catch
  ---
  duration_ms: 120.185
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-worker-message-port-message-before-close
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#28150, nodejs/node#28102, nodejs/node#28224, nodejs/node#28206)
Appeared test-digitalocean-freebsd11-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/23827/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23902/
Example
not ok 2330 parallel/test-worker-message-port-message-before-close
  ---
  duration_ms: 120.113
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-child-process-pipe-dataflow
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#28058, nodejs/node#27984, nodejs/node#20077)
Appeared test-azure_msft-win10-x64-2, test-azure_msft-win10-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/23831/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23881/
Example
not ok 130 parallel/test-child-process-pipe-dataflow
  ---
  duration_ms: 0.212
  severity: fail
  exitcode: 1
  stack: |-
    assert.js:89
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: child 1 exited with code 1
        at ChildProcess.<anonymous> (c:\workspace\node-test-binary-windows-2\test\parallel\test-child-process-pipe-dataflow.js:49:14)
        at ChildProcess.<anonymous> (c:\workspace\node-test-binary-windows-2\test\common\index.js:374:15)
        at ChildProcess.emit (events.js:200:13)
        at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12) {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
      actual: 1,
      expected: 0,
      operator: 'strictEqual'
    }
  ...


Reason parallel/test-child-process-server-close
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#28179, nodejs/node#28118, nodejs/node#28224)
Appeared test-rackspace-win2008r2-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/23830/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23905/
Example
not ok 132 parallel/test-child-process-server-close
  ---
  duration_ms: 0.157
  severity: fail
  exitcode: 1
  stack: |-
    The directory is not empty.
    c:\workspace\node-test-binary-windows-2\test\common\tmpdir.js:60
            throw e;
            ^
    
    Error: ENOTEMPTY: directory not empty, rmdir 'c:\workspace\node-test-binary-windows-2\test\.tmp.4'
        at Object.rmdirSync (fs.js:693:3)
        at rmdirSync (c:\workspace\node-test-binary-windows-2\test\common\tmpdir.js:82:10)
        at rimrafSync (c:\workspace\node-test-binary-windows-2\test\common\tmpdir.js:40:7)
        at Object.refresh (c:\workspace\node-test-binary-windows-2\test\common\tmpdir.js:96:3)
        at Object.<anonymous> (c:\workspace\node-test-binary-windows-2\test\parallel\test-child-process-server-close.js:8:8)
        at Module._compile (internal/modules/cjs/loader.js:779:30)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:790:10)
        at Module.load (internal/modules/cjs/loader.js:642:32)
   ...

Reason doctool/test-make-doc
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#28179, nodejs/node#28246)
Appeared test-digitalocean-fedora30-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/23816/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23903/
Example
not ok 2491 doctool/test-make-doc
  ---
  duration_ms: 0.91
  severity: fail
  exitcode: 1
  stack: |-
    assert.js:375
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: repl.html does not exist
        at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux/nodes/fedora-latest-x64/test/doctool/test-make-doc.js:50:10)
        at Module._compile (internal/modules/cjs/loader.js:779:30)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:790:10)
        at Module.load (internal/modules/cjs/loader.js:642:32)
        at Function.Module._load (internal/modules/cjs/loader.js:555:12)
        at Function.Module.runMain (internal/modules/cjs/loader.js:842:10)
        at internal/main/run_main_module.js:17:11 {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
  ...


Reason known_issues/test-vm-timeout-escape-nexttick
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#27984, nodejs/node#28021)
Appeared test-digitalocean-ubuntu1604_sharedlibs_container-x64-9, test-digitalocean-alpine38_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/23839/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23846/
Example
not ok 2580 known_issues/test-vm-timeout-escape-nexttick
  ---
  duration_ms: 0.411
  severity: fail
  stack: |-
  ...


Reason parallel/test-cli-node-options
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#27744, nodejs/node#28224)
Appeared test-rackspace-win2008r2-x64-3, test-requireio_svincent-debian9-armv7l_pi2-3, test-requireio_piccoloaiutante-debian9-arm64_pi3-1
First CI https://ci.nodejs.org/job/node-test-pull-request/23850/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23905/
Example
not ok 147 parallel/test-cli-node-options
  ---
  duration_ms: 0.174
  severity: fail
  exitcode: 1
  stack: |-
    c:\workspace\node-test-binary-windows-2\test\.tmp.4\node-copy.exe - Access is denied.
    c:\workspace\node-test-binary-windows-2\test\common\tmpdir.js:60
            throw e;
            ^
    
    Error: ENOTEMPTY: directory not empty, rmdir 'c:\workspace\node-test-binary-windows-2\test\.tmp.4'
        at Object.rmdirSync (fs.js:693:3)
        at rmdirSync (c:\workspace\node-test-binary-windows-2\test\common\tmpdir.js:82:10)
        at rimrafSync (c:\workspace\node-test-binary-windows-2\test\common\tmpdir.js:40:7)
        at Object.refresh (c:\workspace\node-test-binary-windows-2\test\common\tmpdir.js:96:3)
        at Object.<anonymous> (c:\workspace\node-test-binary-windows-2\test\parallel\test-cli-node-options.js:12:8)
        at Module._compile (internal/modules/cjs/loader.js:779:30)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:790:10)
        at Module.load (int...

Reason parallel/test-cpu-prof-exit
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#28058, nodejs/node#28234)
Appeared test-azure_msft-win2016-x64-2, test-azure_msft-win2012r2-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/23814/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23900/
Example
not ok 202 parallel/test-cpu-prof-exit
  ---
  duration_ms: 0.874
  severity: fail
  exitcode: 1
  stack: |-
    Dispatching message { "id": 1, "method": "Profiler.enable" }
    Receive CPU profile message, ending = false
    Dispatching message { "id": 2, "method": "Profiler.start" }
    Receive CPU profile message, ending = false
    Dispatching message { "id": 3, "method": "Profiler.setSamplingInterval", "params": { "interval": 50 } }
    Receive CPU profile message, ending = false
    EndStartedProfilers
    Ending cpu profiling
    Dispatching message { "id": 4, "method": "Profiler.stop" }
    Receive CPU profile message, ending = true
    Written result to c:\workspace\node-test-binary-windows-2\test\.tmp.0\CPU.20190615.035458.4432.0.001.cpuprofile
    
    [
      {
        id: 1,
        callFrame: {
          functionName: '(root)',
          scriptId: '0',
          url: '',
          lineNumber: -1,
          columnNumber: -1
        },
        hitCount: 0,
        children: [ 2, 3 ]
      },
     ...

Jenkins Failure

Reason Build timed out (after 15 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 4 (nodejs/node#28058, nodejs/node#28188, nodejs/node#28197, nodejs/node#28189)
Appeared test-rackspace-win2008r2-x64-3, test-rackspace-win2008r2-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/23819/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23895/
Example
Build timed out (after 15 minutes). Marking the build as failed.

Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 2 (nodejs/node#28006, nodejs/node#28212)
Appeared test-macstadium-macos10.11-x64-2, test-macstadium-macos10.10-x64-1, test-azure_msft-win10-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/23848/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23888/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 207.254.58.162/207.254.58.162:49853' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)
	at com.sun.proxy.$Proxy93.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1144)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1136)

Build Failure

Reason ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...
Type BUILD_FAILURE
Failed PR 4 (nodejs/node#20077, nodejs/node#27808, nodejs/node#28225, nodejs/node#28188)
Appeared test-macstadium-macos10.11-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/23881/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23884/
Example
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for node-test-commit-osx/nodes=osx1011 #27448
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

Reason ERROR: Step ?Publish JUnit test result report? failed: no workspace for ...
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#28222, nodejs/node#28230)
Appeared test-macstadium-macos10.11-x64-2, test-osuosl-aix61-ppc64_be-1
First CI https://ci.nodejs.org/job/node-test-pull-request/23876/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23887/
Example
ERROR: Step ?Publish JUnit test result report? failed: no workspace for node-test-commit-osx/nodes=osx1011 #27451
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: 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#28209, nodejs/node#28232)
Appeared test-packetnet-centos7-arm64-1, test-packetnet-centos7-arm64-2, test-packetnet-ubuntu1604-arm64-1, test-linuxonecc-rhel72-s390x-1
First CI https://ci.nodejs.org/job/node-test-pull-request/23869/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23892/
Example
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

Reason Error: No module named 'tap13'
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#28209, nodejs/node#28232)
Appeared test-digitalocean-fedora30-x64-1, test-digitalocean-ubuntu1604_sharedlibs_container-x64-5, test-softlayer-ubuntu1604_sharedlibs_container-x64-3, test-digitalocean-ubuntu1604_sharedlibs_container-x64-2, test-digitalocean-ubuntu1604_sharedlibs_container-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/23869/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23892/
Example
Error: No module named 'tap13'
POST BUILD TASK : FAILURE
END OF POST BUILD TASK : 0
Recording test results
Recording fingerprints
Collecting metadata...

Reason Failed to trigger node-test-commit
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#28188, nodejs/node#21387)
Appeared test-softlayer-ubuntu1604-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/23822/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23862/
Example
Failed to trigger node-test-commit

Reason fatal: No rebase in progress?
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#28209, nodejs/node#28232)
Appeared test-macstadium-macos10.11-x64-1, test-digitalocean-alpine39_container-x64-2, test-rackspace-ubuntu1604-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/23869/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23892/
Example
fatal: No rebase in progress?

Reason sh: line 42: pgrep: command not found
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#28209, nodejs/node#28230)
Appeared test-osuosl-aix61-ppc64_be-1
First CI https://ci.nodejs.org/job/node-test-pull-request/23869/
Last CI https://ci.nodejs.org/job/node-test-pull-request/23887/
Example
sh: line 42: pgrep: command not found

@joyeecheung
Copy link
Member Author

joyeecheung commented Jun 16, 2019

In progress

nodejs/node#28210

  • parallel/test-cpu-prof-dir-and-name (4)
  • parallel/test-cpu-prof-dir-worker (4)
  • parallel/test-cpu-prof-exit (2)
  • parallel/test-cpu-prof-worker-argv (4)

???

  • parallel/test-tls-cli-min-version-1.1 (5)
  • parallel/test-tls-cli-min-version-1.2 (5)
  • parallel/test-stdout-close-catch (4)
  • parallel/test-worker-message-port-message-before-close (4)
  • parallel/test-child-process-pipe-dataflow (3)
  • parallel/test-child-process-server-close (3)
  • doctool/test-make-doc (2)
  • known_issues/test-vm-timeout-escape-nexttick (2)
  • parallel/test-cli-node-options (2)
  • Build timed out (after 15 minutes). Marking the build as failed. (4)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (4)
  • ERROR: Step ?Publish JUnit test result report? failed: no workspace for ... (2)
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
  • Error: No module named 'tap13' (2)
  • Failed to trigger node-test-commit (2)
  • fatal: No rebase in progress? (2)
  • sh: line 42: pgrep: command not found (2)

@joaocgreis
Copy link
Member

Build timed out (after 15 minutes). Marking the build as failed. is being tracked in nodejs/build#1829

@joyeecheung
Copy link
Member Author

The TLS flakes are false negatives: nodejs/node-core-utils#357

@Trott
Copy link
Member

Trott commented Oct 15, 2019

Seems like this is sufficiently idle that it can be closed, but doctool/test-doctool-html failures have gotten much more frequent. The fix is in nodejs/node#29979, so please review and approve for fast-tracking.

@Trott Trott closed this as completed Oct 15, 2019
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

3 participants