| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
The certificates in test fixtures were set to expire in 999 days since they were generated. That time has passed, and they have to be reissued. Bump expiration time to 9999 days for all of them to prevent this from happening again in near future. Fix: #22182
|
@indutny build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/455/pipeline |
Sorry, something went wrong.
|
cc @MylesBorins @nodejs/crypto @bnoordhuis |
Sorry, something went wrong.
| ca3-csr.pem: ca3.cnf ca3-key.pem | ||
| openssl req -new \ | ||
| -extensions v3_ca \ | ||
| -days 9999 \ |
There was a problem hiding this comment.
Gosh, this slipped my quick review. It isn't really necessary, since the days are set in ca3.cnf.
Sorry, something went wrong.
There was a problem hiding this comment.
Should we remove it or just leave it?
Sorry, something went wrong.
There was a problem hiding this comment.
Removed.
Sorry, something went wrong.
Sorry, something went wrong.
|
@indutny no bueno test.parallel/test-crypto-sign-verify all failing https://ci.nodejs.org/job/node-test-commit-linux/20522/nodes=alpine-latest-x64/ |
Sorry, something went wrong.
|
Should be fixed now. |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
we should fast track this as it is breaking lots of things
Sorry, something went wrong.
There was a problem hiding this comment.
😅
Sorry, something went wrong.
|
I wonder if we shouldn't look at potentially dynamically generating these every so often |
Sorry, something went wrong.
|
one last ci with sn extra 9... giving us 273 years to figure this out instead of 27 |
Sorry, something went wrong.
|
Ah yes, good ole Node.js 557.0.0 |
Sorry, something went wrong.
|
@indutny still getting failures on arm https://ci.nodejs.org/job/node-test-binary-arm/2608/RUN_SUBSET=5,label=pi3-docker/console |
Sorry, something went wrong.
21:53:31 AssertionError [ERR_ASSERTION]: 5 2 agent3 rejected, but should NOT have been 21:53:31 at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-tls-server-verify.js:232:14) 21:53:31 at ChildProcess.emit (events.js:182:13) 21:53:31 at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12) |
Sorry, something went wrong.
|
@mhdawson and I dug in a bunch and it seems like the failures on arm are infra related... potentially during setup @rvagg can you dig into this? One more ci: https://ci.nodejs.org/job/node-test-pull-request/16265/ landing if green |
Sorry, something went wrong.
There was a problem hiding this comment.
Rubber-stamp LGTM if CI is green. +1 to fast-tracking
Sorry, something went wrong.
|
parallel/test-tls-server-verify still failing on Raspberry Pi... |
Sorry, something went wrong.
|
oops... I did the status file wrong re-running arm https://ci.nodejs.org/job/node-test-commit-arm-fanned/2721/ |
Sorry, something went wrong.
|
Diagnosis & fix nodejs/build#1432 |
Sorry, something went wrong.
The certificates in test fixtures were set to expire in 999 days since they were generated. That time has passed, and they have to be reissued. Bump expiration time to 99999 days for all of them to prevent this from happening again in near future. PR-URL: #22184 Fixes: #22182 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Rod Vagg <rod@vagg.org>
|
Custom suites failed to git clone again. Re-running (again): https://ci.nodejs.org/job/node-test-commit-custom-suites/524/ (Not that it's relevant, since in node-daily-master, I'm pretty sure it only runs the internet suite.) |
Sorry, something went wrong.
|
Backporting to all staging branches v11.x-staging 6efbe1a |
Sorry, something went wrong.
|
Unrelated flaky on LinuxONE, re-running: https://ci.nodejs.org/job/node-test-commit-linuxone/3652/ |
Sorry, something went wrong.
|
Custom suites passed. |
Sorry, something went wrong.
|
LinuxONE passed. |
Sorry, something went wrong.
|
Argh, the --worker custom suite run also failed. Re-run: https://ci.nodejs.org/job/node-test-commit-custom-suites/528/ |
Sorry, something went wrong.
|
--worker custom suite re-run passed. |
Sorry, something went wrong.
The certificates in test fixtures were set to expire in 999 days since they were generated. That time has passed, and they have to be reissued. Bump expiration time to 99999 days for all of them to prevent this from happening again in near future. PR-URL: #22184 Fixes: #22182 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Rod Vagg <rod@vagg.org>
The certificates in test fixtures were set to expire in 999 days since they were generated. That time has passed, and they have to be reissued. Bump expiration time to 99999 days for all of them to prevent this from happening again in near future. PR-URL: #22184 Fixes: #22182 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Rod Vagg <rod@vagg.org>
The certificates in test fixtures were set to expire in 999 days since they were generated. That time has passed, and they have to be reissued. Bump expiration time to 99999 days for all of them to prevent this from happening again in near future. PR-URL: #22184 Fixes: #22182 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Rod Vagg <rod@vagg.org>
The certificates in test fixtures were set to expire in 999 days since they were generated. That time has passed, and they have to be reissued. Bump expiration time to 99999 days for all of them to prevent this from happening again in near future. PR-URL: nodejs/node#22184 Fixes: nodejs/node#22182 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Rod Vagg <rod@vagg.org>
| Back | FazBrowse Home | New Git URL |
The certificates in test fixtures were set to expire in 999 days since
they were generated. That time has passed, and they have to be reissued.
Bump expiration time to 9999 days for all of them to prevent this from
happening again in near future.
Fix: #22182
Checklist