-
-
Notifications
You must be signed in to change notification settings - Fork 37.2k
test: benchmark/test-benchmark-os fails on IBM i #50207
Copy link
Copy link
Closed
Labels
benchmarkIssues and PRs related to Node.js benchmarks and benchmarking infrastructure.Issues and PRs related to Node.js benchmarks and benchmarking infrastructure.ibm iIssues and PRs related to the IBM i platform.Issues and PRs related to the IBM i platform.
Description
Activity
Metadata
Metadata
Assignees
Labels
benchmarkIssues and PRs related to Node.js benchmarks and benchmarking infrastructure.Issues and PRs related to Node.js benchmarks and benchmarking infrastructure.ibm iIssues and PRs related to the IBM i platform.Issues and PRs related to the IBM i platform.
CI: https://ci.nodejs.org/job/node-test-commit-ibmi/1332/nodes=ibmi73-ppc64/testReport/(root)/benchmark/test_benchmark_os/
test-benchmark-os.js now includes an os.uptime benchmark.
For reference, this commit adds the uptime benchmark: 0f0dd1a
This test fails is due to the fact that os.uptime returns enosys on IBM i.
https://github.com/libuv/libuv/blame/dc1bb0088e8fbb92c81beb55341dcb7b4079717f/src/unix/ibmi.c#L283
We would need to find a way to skip this uptime benchmark individually (on IBM i) if possible. Otherwise we may need to disable running the test-benchmark-os.js in the meantime (on IBM i).