-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Conversation
It looks like @ddorgan signed our Contributor License Agreement. 👍 Many thanks, Parity Technologies CLA Bot |
Not looking great so far. Will need to re-test this with a new system to rule out this being an issue with the disks on our existing runners. |
@@ -56,4 +56,4 @@ cd parity-clib-examples/cpp && \ | |||
# Running tests | |||
echo "________Running Parity Full Test Suite________" | |||
git submodule update --init --recursive | |||
time cargo test $OPTIONS --features "$FEATURES" --all $1 -- --test-threads 8 | |||
time cargo test $OPTIONS --features "$FEATURES" --all $1 -- --test-threads 4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why's that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want to time this to check if the builds went faster. Right now the load average is about 16, which is double the amount of CPU's available. Was hoping reducing the amount of threads would cause less resource contention. But the times look about the same :/
Unfortunately, I think this does not solve any of our issues, also conflicts with #9681 |
Some jobs are spending longer on caching than the actual running of tests, e.g. https://gitlab.parity.io/parity/parity-ethereum/-/jobs/101206