[test] CI and Regression Test Optimizations
I'm a bit conflicted about adding complexity to the regression test wrapper, but with number of tests we've slated to add CI time will shortly become untenable without parallelism so this makes appropriate changes to support that now. If PARALLELISM
is set and DEBUG
is not, the regression tests will be spawned in parallel with the test number added to the RPC / API ports to avoid any conflict.
There are a few additional earmarks:
- Upgrades to
trunk
tooling - Cache
trunk
linters in CI - Avoid regression test image build invalidation on
git
state changes (@Multipartite request) - Enable debug logs in
thornode
for regression tests whenDEBUG
is set (@Multipartite request)