-
-
Notifications
You must be signed in to change notification settings - Fork 33.1k
Closed
Labels
benchmarkIssues and PRs related to the benchmark subsystem.Issues and PRs related to the benchmark subsystem.ibm iIssues and PRs related to the IBM i platform.Issues and PRs related to the IBM i platform.
Description
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.
Welcome to Node.js v20.5.1.
Type ".help" for more information.
> require('os').uptime()
Uncaught:
SystemError [ERR_SYSTEM_ERROR]: A system error occurred: uv_uptime returned ENOSYS (function not implemented)
at __node_internal_captureLargerStackTrace (node:internal/errors:496:5)
at new SystemError (node:internal/errors:256:5)
at new NodeError (node:internal/errors:367:7)
at Object.__node_internal_checkError [as uptime] (node:os:68:13) {
code: 'ERR_SYSTEM_ERROR',
info: {
errno: -109,
code: 'ENOSYS',
message: 'function not implemented',
syscall: 'uv_uptime'
},
errno: [Getter/Setter: -109],
syscall: [Getter/Setter: 'uv_uptime']
}
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).
Metadata
Metadata
Assignees
Labels
benchmarkIssues and PRs related to the benchmark subsystem.Issues and PRs related to the benchmark subsystem.ibm iIssues and PRs related to the IBM i platform.Issues and PRs related to the IBM i platform.