Conversation
09d9eb3 to
5b42dd3
Compare
|
Looks great, much faster. I saw a few retries I gathered all the retries below. In one case it failed twice in a row so we had 2 retries and 3rd one passed (on noble): They don't seem to have any repeated patterns in them, all different tests. What I haven't looked at is if these happen about as often in non-parallel tests. If these are worse with parallel test we could try a -j2 first perhaps and see if we get fewer of them |
5b42dd3 to
c6bf8c9
Compare
I cloned the noble entry (excluded jammy) with a non-parallel eunit setting to have a direct comparison of two runs. Maybe we get some hints ... |
c6bf8c9 to
56e966d
Compare
build-aux/Jenkinsfile
Outdated
| INTERMEDIATE_ERLANG_VERSION = '27.3.4.8' | ||
|
|
||
| // Default GNU Make Eunit Options for supported platforms | ||
| DEFAULT_GNU_MAKE_EUNIT_OPTS = '-j4 --output-sync=target' |
There was a problem hiding this comment.
What do you think about just trying -j2 first? If that gives us a good enough boost without too many retries that can be a good first step. Then we can try moving on to -j3 and -j4 later.
b6d2da8 to
61be08e
Compare
61be08e to
4fea8a6
Compare
|
Thanks for taking a look at this Ronny. I am looking at the results and I wonder if it's just some hardware nodes that are the problem: In this case it's |
No description provided.