Implement reporting unit test timings in CI #2995
Conversation
|
Had a chat with Lukasz, nightly does have a higher chance of inadvertently breaking things, could you use Just for context: the reason we use limited test-threads is to prevent going out of memory. |
|
Looks great! Can you make a PR in snarkOS as well? |
|
@vicsn I tried a few things here (though am mostly trying to make the snarkos version work in the moment) and it seems nextest runs are slower. So, because we are going to try to speed up things anyway either I can try to make |
|
Actually looking around many workflows are passing for the same time, especially in the SnarkOS version. It is specific for the synthesizer-workflow and for some of the others a bit, but not so much, hmmm. |
meddle0x53
force-pushed
the
staging
branch
2 times, most recently
from
8309a34 to
50c40d5
Compare
|
We will surely hit some edge-cases the following days on new PRs, but happy that we have this data to start optimizing |
2 participants
Motivation
Implements #2981 and also stores the timing reports as CSVs so they can be analysed.
Test Plan
The CI passes and the timings of the different tests could be viewed.
Documentation
The PR updates the CI configuration and modifies how tests are ran.
Backwards compatibility
Backwards compatible.