Experiment with Semaphore CI 2.0 #2972
Conversation
kinke
force-pushed
the
semaphore2
branch
3 times, most recently
from
ccf6a27
to
e95dfbb
Compare
|
Errors during git checkout - may need a repo owner to set it up (they require separate v2 accounts...). - Documentation is very scarce, but they now feature a non-dockerized Ubuntu 18.04 image with 8 GB of usable memory (previously: dockerized 18.04 with ~2.4 GB), so that building single-threadedly and splitting the run in 2 jobs shouldn't be required anymore. |
kinke
force-pushed
the
semaphore2
branch
2 times, most recently
from
4d11f0c
to
38adbcc
Compare
|
Okay, a simple The available memory seems to be 4 GB, not 8 GB. The full run (native Ubuntu 18.04 image, using its LLVM 6.0.0, gcc 7 etc., multilib) now succeeds and took about 42 minutes. Can you guys display the CI log without being logged in? |
No, I need to log in, but then I can see it fine. |
|
Oh wow, that's a serious problem. Another one is that they are supposed to prepare a free service for open-source projects; right now we have a free 20$ credit per month, which translates to about one 42-minutes run per day. |
|
A full multilib run with their octacore-machines takes under 20 minutes. I expected a somewhat better scaling; |
kinke
force-pushed
the
semaphore2
branch
3 times, most recently
from
9645edf
to
77216d7
Compare
As the prices scale linearly, the machine with 8 cores and 16 GB RAM costs 4x as much (per second) as the one with 2 cores and 4 GB. Our run should scale pretty well with CPU cores, so the overall cost shouldn't be much higher.
|
This isn't going anywhere; free credit was halved in the meantime, and the only available machine for the free plan has 2 cores now. |
No description provided.