Anton Whalley

Not sure why we want to close it @tony-go I opened it to capture that we have set JSArrayBuffer to optional which isn't ideal and should be looked at. That...

Funny enough not having the right node version is a common error even among experienced developers so I would aim for adding a test.

Also I'm at collab summit today I'll confirm with @mhdawson best way to formally add you to the repo so you can edit labels etc

@kvakil This is failing because 19.x doesn't exist in https://nodejs.org/dist/ I'll take a look around the issues in core and update here with more info as I find it.

@kvakil So this was easy. There is no `19.x` because it's not due out until Oct 18th https://github.com/nodejs/node/issues/44650 The issue states that `latest` releases are built against on `V8 10.2`...

Now that 19 is released i re-ran the tests The Ubuntu 18 are failing with: ``` node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node) Error: Process completed with exit...

Thanks for this PR. My initial reaction is that if the zip is corrupting the core dumps then it should just be turned off rather than having a flag. That...

Thanks for the update. Let me see if I can reproduce this over the weekend and get back to you.

Haven't had the bandwidth to look at it yet. Too much happening at this time of year. If you have some bandwidth can you create a large core file (could...

Excellent thanks for looking into this and providing reproduction steps. The hickup is intentional for a failed test. It's good to have the failed artifacts when it breaks but it...