[
https://issues.apache.org/jira/browse/DISPATCH-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172452#comment-17172452
]
ASF GitHub Bot commented on DISPATCH-1739:
------------------------------------------
gemmellr commented on pull request #809:
URL: https://github.com/apache/qpid-dispatch/pull/809#issuecomment-669987352
Give it time ;)
Everyone will flock to GHA, the apache org might have not have a shared
quota big enough to avoid huge projects from causing queues for the rest, and
then Travis/other could become more responsive. Repeat cycle.
It happens every time something becomes the shiny new CI Env hehe. The ASF
Jenkins servers long used to be uselessly overloaded - now they too easily beat
Travis / Appveyor most of the time as enough bigger jobs moved away from using
Jenkins to using those.
Hence why I like having CI jobs in all the envs. Invariably at any given
point at least one of them is backlogged, down, or walking wounded, but others
are in a better state.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Use GitHub Actions w/ sharding and bubblewrap for some fast CI
> --------------------------------------------------------------
>
> Key: DISPATCH-1739
> URL: https://issues.apache.org/jira/browse/DISPATCH-1739
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 1.12.0
> Reporter: Jiri Daněk
> Assignee: Jiri Daněk
> Priority: Major
> Fix For: 1.13.0
>
>
> GitHub Actions is a task runner associated with a GitHub project. It is
> conceptually similar to Travis, except that it has some extra features, and
> the waits for computational resources are much shorter (currently).
> Sharding is a technique to speed up the execution of tests. Instead of
> running the tests on one machine one after another, copy the build directory
> over to multiple machines, say two, and have the first execute the
> odd-numbered and the second one the even-numbered tests. With luck (if
> copying the build directory is relatively fast, and the tests all take
> approximately the same time), this will cut the execution time in half.
> Bubblewrap (https://github.com/containers/bubblewrap) is a sandboxing tool
> available on Ubuntu and other systems. It is similar to systemd-nspawn except
> it does not require sudo or user namespace support in the kernel. It is
> similar to docker, except it does not use images, instead it selectively
> mounts directories from the host. Bubblewrap can create an isolated network
> namespace, which allows running multiple tests at the same time, each in its
> own bubblewrap sandbox, and they don't clash on ports. With bubblewrap,
> running {{ctest -j4}} is safe.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
