upload encrypted core dumps from CI #19189
Conversation
|
Updated 1:45 PM PT - Apr 25th, 2025
❌ @190n, your commit ac9eb8a has 4 failures in
Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. Hello WorldThis is an example. 🧪 try this PR locally: bunx bun-pr 19189 |
What does this PR do?
Makes
runner.node.mjsupload core dumps from any crashes that occurred in testing as a Buildkite artifact. These are uploaded as a gzipped tarball, encrypted with an age public key. They can only be decrypted with the private key which our team will have (these contain env vars and therefore API keys so they need to be secret).I've added a test that intentionally crashes so I can see if this works.
I will write down exact commands once this is really working, but the workflow will look something like:
bun-profilebinary for the samegdb/lldb -q path/to/bun-profile path/to/bun-profile-XYZ.coreIf parts of the stack trace are in a dynamic library (libc, libc++, Node-API module...) you may need to have that library (the same exact version that was used by the CI runner) downloaded too to get the best debugging experience.
It will be nice to have these on macOS and Windows, too, but I'm not as familiar with core dumps on those so I will do that later.
How did you verify your code works?
CI, plus some manual testing with
machine.mjsbefore I opened this PR