| 2020-07-10 10:29:01 |
Olivier Tilloy |
bug |
|
|
added bug |
| 2020-07-10 10:29:01 |
Olivier Tilloy |
attachment added |
|
node-create-hash.log https://bugs.launchpad.net/bugs/1887144/+attachment/5391266/+files/node-create-hash.log |
|
| 2020-07-10 10:29:24 |
Olivier Tilloy |
bug task added |
|
node-crypto-browserify (Ubuntu) |
|
| 2020-07-10 10:29:37 |
Olivier Tilloy |
bug task added |
|
node-create-hash (Ubuntu) |
|
| 2020-07-10 10:41:41 |
Olivier Tilloy |
affects |
node-sha (Ubuntu) |
node-sha.js (Ubuntu) |
|
| 2020-07-10 10:41:54 |
Olivier Tilloy |
description |
Since nodejs 12.18.1 entered groovy-proposed, autopkgtests that rely on node-sha to compute SHA-1 hashes started failing reliably on ppc64el. This affects the following packages:
- node-sha
- node-crypto-browserify
- node-create-hash
Other architectures do not appear to be affected, and it's only the SHA-1 hashes that are incorrect, other hashing algorithm are not affected.
For reference, I'm attaching the full log for the last failed run of node-create-hash on ppc64el (see https://autopkgtest.ubuntu.com/packages/n/node-create-hash/groovy/ppc64el).
Upstream bug report: https://github.com/crypto-browserify/sha.js/issues/66 |
Since nodejs 12.18.1 entered groovy-proposed, autopkgtests that rely on node-sha to compute SHA-1 hashes started failing reliably on ppc64el. This affects the following packages:
- node-sha.js
- node-crypto-browserify
- node-create-hash
Other architectures do not appear to be affected, and it's only the SHA-1 hashes that are incorrect, other hashing algorithm are not affected.
For reference, I'm attaching the full log for the last failed run of node-create-hash on ppc64el (see https://autopkgtest.ubuntu.com/packages/n/node-create-hash/groovy/ppc64el).
Upstream bug report: https://github.com/crypto-browserify/sha.js/issues/66 |
|
| 2020-07-30 14:45:25 |
Olivier Tilloy |
description |
Since nodejs 12.18.1 entered groovy-proposed, autopkgtests that rely on node-sha to compute SHA-1 hashes started failing reliably on ppc64el. This affects the following packages:
- node-sha.js
- node-crypto-browserify
- node-create-hash
Other architectures do not appear to be affected, and it's only the SHA-1 hashes that are incorrect, other hashing algorithm are not affected.
For reference, I'm attaching the full log for the last failed run of node-create-hash on ppc64el (see https://autopkgtest.ubuntu.com/packages/n/node-create-hash/groovy/ppc64el).
Upstream bug report: https://github.com/crypto-browserify/sha.js/issues/66 |
Since nodejs 12.18.1 entered groovy-proposed, autopkgtests that rely on node-sha.js to compute SHA-1 hashes started failing reliably on ppc64el. This affects the following packages:
- node-sha.js
- node-crypto-browserify
- node-create-hash
Other architectures do not appear to be affected, and it's only the SHA-1 hashes that are incorrect, other hashing algorithm are not affected.
For reference, I'm attaching the full log for the last failed run of node-create-hash on ppc64el (see https://autopkgtest.ubuntu.com/packages/n/node-create-hash/groovy/ppc64el).
Upstream bug report: https://github.com/crypto-browserify/sha.js/issues/66 |
|
| 2020-08-02 04:15:22 |
Bryce Harrington |
bug |
|
|
added subscriber Bryce Harrington |
| 2020-08-06 15:30:30 |
Olivier Tilloy |
summary |
autopkgtest failures on ppc64el with nodejs 12.18.1 |
autopkgtest failures on ppc64el with nodejs 12.18.2 |
|
| 2020-08-06 15:30:43 |
Olivier Tilloy |
bug task added |
|
nodejs (Ubuntu) |
|
| 2020-08-07 12:18:53 |
Olivier Tilloy |
description |
Since nodejs 12.18.1 entered groovy-proposed, autopkgtests that rely on node-sha.js to compute SHA-1 hashes started failing reliably on ppc64el. This affects the following packages:
- node-sha.js
- node-crypto-browserify
- node-create-hash
Other architectures do not appear to be affected, and it's only the SHA-1 hashes that are incorrect, other hashing algorithm are not affected.
For reference, I'm attaching the full log for the last failed run of node-create-hash on ppc64el (see https://autopkgtest.ubuntu.com/packages/n/node-create-hash/groovy/ppc64el).
Upstream bug report: https://github.com/crypto-browserify/sha.js/issues/66 |
Since nodejs 12.18.1 entered groovy-proposed, autopkgtests that rely on node-sha.js to compute SHA-1 hashes started failing reliably on ppc64el. This affects the following packages:
- node-sha.js
- node-crypto-browserify
- node-create-hash
Other architectures do not appear to be affected, and it's only the SHA-1 hashes that are incorrect, other hashing algorithm are not affected.
For reference, I'm attaching the full log for the last failed run of node-create-hash on ppc64el (see https://autopkgtest.ubuntu.com/packages/n/node-create-hash/groovy/ppc64el).
Upstream (sha.js) bug report: https://github.com/crypto-browserify/sha.js/issues/66
Upstream (Node.js) bug report: https://github.com/nodejs/node/issues/34666 |
|
| 2020-08-07 12:19:06 |
Olivier Tilloy |
bug watch added |
|
https://github.com/nodejs/node/issues/34666 |
|
| 2020-08-24 13:22:57 |
Olivier Tilloy |
nodejs (Ubuntu): status |
New |
Fix Committed |
|
| 2020-08-24 13:23:46 |
Olivier Tilloy |
summary |
autopkgtest failures on ppc64el with nodejs 12.18.2 |
node-sha.jsautopkgtest failures on ppc64el with nodejs 12.18.2 |
|
| 2020-08-24 13:23:49 |
Olivier Tilloy |
summary |
node-sha.jsautopkgtest failures on ppc64el with nodejs 12.18.2 |
node-sha.js autopkgtest failures on ppc64el with nodejs 12.18.2 |
|
| 2020-08-24 13:23:52 |
Olivier Tilloy |
node-sha.js (Ubuntu): status |
New |
Invalid |
|
| 2020-08-24 13:23:55 |
Olivier Tilloy |
node-crypto-browserify (Ubuntu): status |
New |
Invalid |
|
| 2020-08-24 13:23:56 |
Olivier Tilloy |
node-create-hash (Ubuntu): status |
New |
Invalid |
|
| 2020-08-30 10:26:29 |
Launchpad Janitor |
nodejs (Ubuntu): status |
Fix Committed |
Fix Released |
|
