Use nextest for CI test jobs

[Dandandan]

Which issue does this PR close?

N/A.

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Yes:

Are there any user-facing changes?

No. This only changes CI test execution.

[Omega359]

I think I tried this in the past ... do the ci machines have enough cores and memory to actually do this effectively?

[2010YOUY01]

Thank you for working on this!

I’m wondering if you’ve tried connecting the sqllogictest harness to nextest. This might need some work, but it could make tests easier to run.

[Omega359]

Thank you for working on this!

I’m wondering if you’ve tried connecting the sqllogictest harness to nextest. This might need some work, but it could make tests easier to run.

I think @alamb had tried originally to get it hooked up in #13045 but was blocked by a nextest behaviour.

[alamb]

I think @alamb had tried originally to get it hooked up in #13045 but was blocked by a nextest behaviour.

As I recall, what is needed is to mimic the output of cargo test 's default runner to list the tests that are run. This might be straightforward with claude /codex now

[alamb]

this is a nice way to avoid having to rebuild nextest each run

[Dandandan]

I think @alamb had tried originally to get it hooked up in #13045 but was blocked by a nextest behaviour.

As I recall, what is needed is to mimic the output of cargo test 's default runner to list the tests that are run. This might be straightforward with claude /codex now

We can do this in a separate pass I think.

[Dandandan]

Thank you for working on this!

I’m wondering if you’ve tried connecting the sqllogictest harness to nextest. This might need some work, but it could make tests easier to run.

How would it make tests easier to run? Or do you mean that it could use nextest for all?

[Dandandan]

I think I tried this in the past ... do the ci machines have enough cores and memory to actually do this effectively?

They have 4 cores it seems, so it should help.

AFAIK the biggest speedup with nextest comes from running tests in parallel across binaries, instead of waiting for each binary to finish sequentially.