ci(napi/oxlint): run tests with coverage profile

[overlookmotel]

The bug fixed in #12299 went unnoticed originally because we build the napi/oxlint2 crate for tests in release mode, with debug assertions disabled.

Instead, build with --profile coverage which enables debug assertions. It's also faster to compile.

[overlookmotel]

• feat(allocator): add Allocator::end_ptr method #12330
• feat(allocator): AllocatorPool store IDs in Allocators #12310
• refactor(allocator): move all fixed size allocator code into 1 file #12309
• ci(napi/oxlint): run tests with coverage profile #12308 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Boshen]

Merge activity

• Jul 16, 10:31 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jul 16, 10:31 AM UTC: Boshen added this pull request to the Graphite merge queue.
• Jul 16, 10:48 AM UTC: Merged by the Graphite merge queue.

[camc314]

should we do this for all napi packages?

[overlookmotel]

should we do this for all napi packages?

Not sure.

oxc-parser tests already take ~9 seconds to run locally, probably more in CI. It'd be ideal not to slow them down further if we can avoid it, and the compile time is pretty decent already. But maybe enabling debug assertions and -O 2 optimizations wouldn't affect runtime much? We could try it.

The rest of the napi packages I know nothing about!