Uh oh!
There was an error while loading. Please reload this page.
test: skip test-benchmark-os.js on IBM i - #50208
Conversation
nodejs-github-bot
commented
Oct 17, 2023
Fast-track has been requested by @mhdawson. Please 👍 to approve. |
mhdawson
commented
Oct 17, 2023
I have an idea on how to be more specific, but think it's good to land this quickly to get the nightly build back to green. |
nodejs-github-bot
commented
Oct 17, 2023
Uzlopak
commented
Oct 17, 2023
I didnt know that the uptime is not working on ibm :/ |
Uzlopak
left a comment
There was a problem hiding this comment.
I created the benchmark and it is not a critical benchmark. It was just for demonstrating that the corresponding PR improves the performance.
We.should simply skip it.
nodejs-github-bot
commented
Oct 18, 2023
nodejs-github-bot
commented
Oct 18, 2023
nodejs-github-bot
commented
Oct 18, 2023
abmusse
commented
Oct 18, 2023
Yes we will look into how to skip this one individually but for now we will skip the benchmark until we get a patch ready. |
PR-URL: #50208 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
mhdawson
commented
Oct 18, 2023
Landed in 286fdaf |
PR-URL: #50208 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
PR-URL: #50208 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
This change skips the entire test-benchmark-os.js suite on IBM i. Currently this is failing due to os.uptime call:
node/benchmark/os/uptime.js
Line 4 in ea595eb
Instead of skipping the entire os benchmark suite, I would rather skip just the uptime benchmark
but I'm not sure how to achieve this. Anyone have any ideas to skip one of the os benchmarks?
CC
@nodejs/platform-ibmi
@richardlau
Fixes#50207