summaryrefslogtreecommitdiff
path: root/user/node
AgeCommit message (Collapse)AuthorFilesLines
2023-03-21user/node: re-enable flaky tests.Zach van Rijn2-15/+1
These tests fail when /etc/hosts does not contain an IPv6 entry for localhost ('::1 localhost'). It isn't immediately clear to me whether the tests are therefore buggy, or if we want to put the blame on a non-conforming build environment. This was initially discovered on a system that only had an IPv4 entry ('127.0.0.1 localhost'), which occurred because the autobuilder tool copied /etc/{hosts,hostname,resolv.conf} from the host into the rootfs for each build environment, and each host may be running a different Linux distribution. This is being addressed in adelie-infra/autobuilder#33, which will ensure build environments are consistent in this way.
2023-03-21user/node: bump { 18.12.1 --> 18.15.0 }. temporarily disable flaky tests.Zach van Rijn5-109/+30
See #971. It is not clear whether these tests ever passed in their current form. Upstream changed these tests (and relevant code) since v16.15.0: https://github.com/nodejs/node/pull/41431 https://github.com/nodejs/node/issues/43014 In v16.15.0, these tests passed on this platform, but they have been modified in subsequent releases, and we've bumped twice since then: b282640c5353f37b706d3395718e80db244644b2 to v16.19.0 5d1083c1c688a496fbf9565046a1e22309cd9ad5 to v18.12.1 I don't see any binaries for aarch64 for either of these versions, suggesting we never rebuilt node on aarch64 after going to v18.12.1, likely due to the ARM builder being out of service between around 2022-12-27 and 2023-01-03. I think we just didn't catch this since bumping to v18.12.1. Temporarily disabling these tests to unblock progress; the bump to v18.15.0 is for some CVEs and expected to be safe.
2023-01-02user/node: Fix time64 issue on pmmxA. Wilcox2-2/+208
This patch reverts Node MR 43714[1], which broke time64 on pmmx. [1]: https://github.com/nodejs/node/pull/43714 Fixes: #935
2022-12-27user/node: Disable on 32-bit PowerPCA. Wilcox1-1/+1
Unfortunately V8 does not support ppc and seemingly has no interest in adopting a port. In the future we will look for alternative JS runtimes for running workloads on ppc. We may also be able to package Node 12 since it has ppc support, with the caveat that it is not well-supported upstream and will stop receiving security updates. This is still useful for some workloads (Firefox builds, internal Homebridge, and such), perhaps. Closes: #837
2022-12-23user/node: fix link failure on 32-bit platforms.Zach van Rijn1-0/+6
2022-12-23user/node: Update to 18.12.1A. Wilcox1-2/+2
2022-12-23user/node: Update to 16.19.0; fix test, NULL derefA. Wilcox4-3/+127
* The worker-stdio test no longer raises RangeError on 32-bit Intel. * The sigint test is no longer flaky (backported from 18 branch). * The C++ Environment handler no longer segfaults when /proc is unmounted. (Submitted upstream.) Fixes: #795
2022-10-21user/node: Use system ICUA. Wilcox1-1/+1
2022-10-21user/node: bump { 10.21.0 --> 16.15.0 }. fixes #604.Zach van Rijn9-4426/+15
2022-10-21user/node: patch several all-caps booleans. fixes #557.Zach van Rijn2-2/+88
2020-06-15user/node: [CVE] bump to 10.21.0 (#300), unvendor opensslMax Rees1-7/+20
2020-03-22user/node: Bump to 10.19.0A. Wilcox1-2/+2
2020-01-14user/node: Bump to 10.18.0A. Wilcox1-5/+2
2019-08-16user/node: [CVE] bump to 10.16.3A. Wilcox2-3/+25
2019-08-09user/node: bump to 10.16.2A. Wilcox1-2/+2
2019-04-06user/node: ensure PPC32 fix doesn't break PPC64A. Wilcox2-5/+8
2019-04-06user/node: fix building on ppc32, and don't rebuild in package()A. Wilcox3-2/+38
2019-04-06user/node: new packageA. Wilcox6-0/+4312