node-sha.js autopkgtest failures on ppc64el with nodejs 12.18.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
node-create-hash (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
node-crypto-browserify (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
node-sha.js (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
nodejs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug 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-
- 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:/
Upstream (sha.js) bug report: https:/
Upstream (Node.js) bug report: https:/
affects: | node-sha (Ubuntu) → node-sha.js (Ubuntu) |
description: | updated |
description: | updated |
summary: |
- autopkgtest failures on ppc64el with nodejs 12.18.1 + autopkgtest failures on ppc64el with nodejs 12.18.2 |
And testing in a ppc64el cloud instance, I reverted nodejs to 10.19.0~ dfsg-3ubuntu1 and the tests reliably pass. This confirms that something in node-sha broke with the update to nodejs 12.18.1~ dfsg-1ubuntu1.