-
Notifications
You must be signed in to change notification settings - Fork 11
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: 20190322 #21
Comments
Progress
|
FTR, a more spesific error identifier is:
i.e.: grep "Makefile.*failed" -C3 |
@refack thanks, this probably should be added in a lower priority (pretty sure |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Failures in node-test-pull-request/21691 (16:00:00 2019-03-20 UTC) to node-test-pull-request/21782 (13:00:00 2019-03-22 UTC) that failed more than 2 PRs
(Generated with
ncu-ci walk pr --stats --copy --cache
)JSTest Failure
parallel/test-inspect-async-hook-setup-at-inspect
Example
parallel/test-https-connect-localport
Example
known_issues/test-vm-timeout-escape-queuemicrotask
Example
parallel/test-async-hooks-http-parser-destroy
Example
parallel/test-gc-http-client-onerror
Example
parallel/test-child-process-pipe-dataflow
Example
parallel/test-fs-stat-bigint
Example
sequential/test-http2-ping-flood
Example
Jenkins Failure
Git Failure
Build Failure
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Example
The text was updated successfully, but these errors were encountered: