ci: use nextest for unit tests, disable grcov collation and codecov o…

[kantai]

Description

Units tests are currently taking ~5 hours to run. This PR alters the execution of the unit tests CI task to use cargo nextest instead of cargo test. This should speed things up pretty significantly (from 5 hours down to 1.5). I can't get grcov to work quite right with this yet, but since pretty much all PRs are stalled due to the unit test run time, getting this change out seems important enough to disable unit test coverage for now.

Applicable issues

• Use nextest and faster action runners for unit tests task #3808

[codecov]

Codecov Report

Merging #3811 (8c62f91) into develop (e150653) will decrease coverage by 0.01%.
Report is 1 commits behind head on develop.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           develop    #3811      +/-   ##
===========================================
- Coverage     0.18%    0.18%   -0.01%     
===========================================
  Files          301      301              
  Lines       278533   278555      +22     
===========================================
  Hits           512      512              
- Misses      278021   278043      +22     

Files Changed	Coverage Δ
src/clarity_vm/tests/analysis_costs.rs	0.00% <0.00%> (ø)
src/clarity_vm/tests/costs.rs	0.00% <0.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[wileyj]

Interesting. i'll have to double check my fork - i was under the impression this was working in that fork's workflows. lack of an error != it's working though, so i'll verify that.

[wileyj]

shipit

[kantai]

@wileyj -- this doesn't really seem like it's going to be sufficient, unfortunately. It looks like the unit tests are still taking a pretty long time, but also the github runner is just dying or disconnecting without any logging.

[kantai]

[kantai]

Just to reiterate, getting this fixed is blocking basically any progress on the blockchain workstreams at the moment -- there's > 30 open PRs, many of which could be merged, but cannot be progressed because the CI testing is broken.

[wileyj]

@wileyj -- this doesn't really seem like it's going to be sufficient, unfortunately. It looks like the unit tests are still taking a pretty long time, but also the github runner is just dying or disconnecting without any logging.

I think this was a transient error, i've never seen an error like this on any workflow run.
i've restarted the workflow that failed in your screenshot to see what happens, if there's any signal of what might have happened.