benchmark: fix EventTarget benchmark#34004
Conversation
|
On a related note, is there a reason why we aren't running /cc @nodejs/collaborators |
People complained that they took too long and timed out too much, so we moved them to node-daily-master. I wouldn't be opposed to adding them back to regular CI runs if we can get regular CI to be less unreliable. The current situation is pretty bad. |
|
I suggest to run the benchmark tests on our CI but not locally. |
As far as I can tell, the node-daily-master CI job isn't currently failing on the |
|
Benchmark CI as a test: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/621/ |
I check it every day. (Sam Roberts did for a while too, but I think he stopped checking a week or three ago.) However I have not had the time to follow up on the various issues. I just see what's failing, feel a pang of guilt that I don't have time to dig in on it right now, and move on. It's my once-a-day guilt-shot. |
Fixes: #33782
Instead of removing the benchmark completely, I've opted to simply tweak it as little as possible so that it no longer crashes.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes