| commit | 45f7b7b9f38f5c4d1529a37c93dedfc26a231bba | |
| author | Thomas Huth <thuth@redhat.com> | |
| Mon, 24 Aug 2020 06:25:21 +0000 (24 08:25 +0200) | ||
| committer | Thomas Huth <thuth@redhat.com> | |
| Thu, 3 Sep 2020 10:46:56 +0000 (3 12:46 +0200) | ||
| tree | 9f807931d376cb95c2f64387889ab3d448fced75 | treesnapshot (tar.gz zip) |
| parent | 7498e6afa103d1e9b71699ebc577d5891eeb6674 | commitdiff |
cirrus.yml: Split FreeBSD job into two parts
The FreeBSD jobs currently hit the 1h time limit in the Cirrus-CI.
We have to split the build targets here to make sure that the job
finishes in time again. According to the Cirrus-CI docs and some
tests that I did, it also seems like the total amount of CPUs that
can be used for FreeBSD jobs is limited to 8, so each job now only
gets 4 CPUs. That increases the compilation time of each job a little
bit, but it still seems to be better to run two jobs with 4 CPUs each
in parallel than to run two jobs with 8 CPUs sequentially.
Message-Id: <20200831154405.229706-1-thuth@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
The FreeBSD jobs currently hit the 1h time limit in the Cirrus-CI.
We have to split the build targets here to make sure that the job
finishes in time again. According to the Cirrus-CI docs and some
tests that I did, it also seems like the total amount of CPUs that
can be used for FreeBSD jobs is limited to 8, so each job now only
gets 4 CPUs. That increases the compilation time of each job a little
bit, but it still seems to be better to run two jobs with 4 CPUs each
in parallel than to run two jobs with 8 CPUs sequentially.
Message-Id: <20200831154405.229706-1-thuth@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
| .cirrus.yml | diffblobblamehistory |