Repository navigation
CI Failures: 20180817 #14
Copy link
Copy link
Closed
Description
Activity
Progress
In Progress:
sequential/test-http2-large-file: Investigate flaky test-http2-large-file node#22327bash: line 2: syntax error near unexpected token newline': GitHub network inconsistancy build#1458sequential/test-performance: Investigate flaky parallel/test-performance node#19197 opened when it was inparallel, fix in test: harden sequential/test-performance node#22404Build timed out (after 120 minutes). Marking the build as failed.: test-digitalocean-fedora27-x64-1 keeps timing out build#1463
Fixed
parallel/test-gc-http-client: Investigate flaky parallel/test-gc-http-client node#22336, fix in test: harden test-gc-http-client node#22373ERROR: Error fetching remote repo 'jenkins_tmp': Git lock in test-azure_msft-win10-x64-3 exists build#1460parallel/test-timers-throw-reschedule(v8.x only): Windows intermittent ? - parallel/test-timers-throw-reschedule node#21188 fix in test: move test-timers-throw-reschedule to sequential node#22379 (marked it as flaky)parallel/test-stdio-pipe-redirect(v8.x only): Investigate flaky parallel/test-stdio-pipe-redirect node#22378parallel/test-crypto-scryptby Upgrade to OpenSSL-1.1.0i node#22318parallel/test-tls-passphraseby Upgrade to OpenSSL-1.1.0i node#22318addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binaryby test: call gc() explicitly to avoid OOM node#22301 (pending a real fix in Investigate flaky addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary on FreeBSD 11 node#22317)Changes not staged for commit:by deps: fix CRLF in text file not present in upstream node#22340ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?: should be fixed by deps: fix CRLF in text file not present in upstream node#22340
???
FATAL: Could not checkout ...: looks like some temporary git failure, I think it's gone now?fatal: Couldn't find remote ref refs/heads/v4.x-staging: see CI failures: 20180815 #13 I think it's gone now
- added a commit that references this issue
on Aug 17, 2018 - added a commit that references this issue
on Aug 22, 2018 - added a commit that references this issue
on Aug 24, 2018 - added a commit that references this issue
on Sep 3, 2018 - added a commit that references this issue
on Nov 2, 2022 - added a commit that references this issue
on Nov 10, 2022 - added a commit that references this issue
on Jan 27, 2023 - added a commit that references this issue
on Jan 27, 2023 - added a commit that references this issue
on Sep 14, 2023
Metadata
Metadata
Assignees
Labels
No labels
Failures in node-test-pull-request/16453 to node-test-pull-request/16516 that failed more than 2 PRs
JSTest Failure
parallel/test-crypto-scryptExample
parallel/test-tls-passphraseExample
parallel/test-gc-http-clientExample
parallel/test-stdio-pipe-redirectExample
sequential/test-http2-large-fileExample
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binaryExample
parallel/test-timers-throw-rescheduleExample
sequential/test-performanceExample
Jenkins Failure
Build timed out (after 120 minutes). Marking the build as failed.Example
Git Failure
Changes not staged for commit:Example
ERROR: Error fetching remote repo 'jenkins_tmp'Example
FATAL: Could not checkout ...Example
Build Failure
bash: line 2: syntax error near unexpected token `newline'Example
fatal: Couldn't find remote ref refs/heads/v4.x-stagingExample
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?Example