[ 
https://issues.apache.org/jira/browse/DISPATCH-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172397#comment-17172397
 ] 

ASF subversion and git services commented on DISPATCH-1739:
-----------------------------------------------------------

Commit 16ac2c5032c23e6430a1e41d6ff28078c5a17fcc in qpid-dispatch's branch 
refs/heads/master from Jiri Danek
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=16ac2c5 ]

DISPATCH-1739 Add GitHub Action w/ sharding and bubblewrap

This is a CI job triggered by pushes and pull requests sent to GitHub.

Output artifacts include parts of the workspace before running tests; this is
what the machines running test shards get. At the end, each shard outputs
a XML CTest report.

Note that `ctest -j2` results in test log lines being mixed up in stdout.
Refer to the output XML report or use grep (grep for lines starting with
the test number) to get understandable log.

* Using python 3.6 as this is the version that works on all platforms tested.
* Using two shards with -j2, which should balance speed and convenience.
* Using ccache w/ 400MB size limit, to avoid purges during the build.

This closes #809


> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to