Michael Dawson

The website now reports "Benchmark data is not currently maintained" for "https://benchmarking.nodejs.org/" but we still have some config to remove so that it does not respond at all.

@sxa, All sounds good to me as well. One this is that with the security release next week it might make sense to try to hold on to the old...

Just one container for centos7 ? Sounds like we had a couple of machines before?

@richardlau k, got it.

> Also, the status page is still in the experimenting-with-it phase, but just as a heads up, its not going to get used without docs on how and when to...

We moved this job to our larger arm machines, so I think this can be closed. Please let us know if you think that was not the right thing to...

Agreed, an ES.next benchmark would be interesting and it would be better if it was turned to reflect Node.js usage. If we can end up with something that has a...

@bmeurer is this still relevant ?

I assume it would just contribute the coverage to https://app.codecov.io/gh/nodejs/node, right? If so then I don't see any issue and seems like a good idea.

I wonder if we are running out of memory. Does the failure occur more often on any particular machine/type of machine?