[
https://issues.apache.org/jira/browse/DISPATCH-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171402#comment-17171402
]
ASF GitHub Bot commented on DISPATCH-1739:
------------------------------------------
jiridanek commented on pull request #809:
URL: https://github.com/apache/qpid-dispatch/pull/809#issuecomment-669110060
I am now thinking of these opportunities for speedup
* fix Proton build to not build test and example programs (either there
isn't an option for it, or it does not work, not sure now)
* set Dispatch build not to build the console, as that takes about 2
minutes, caching npm does not help much, and is already tested on Travis and in
Console GH Action
* run the Action with all reasonable combinations of shard cound and -j, to
see what the run times are
* shard the tests smarter, based on the knowledge of their past duration,
with some provision not to forget running newly added tests
Having a target goal for the test runtime would help. I am now thinking of
aiming for <10 minutes for the ASan instrumented run.
Using larger -j values is risky as it increases the probability of spurious
failures in the tests, caused by timeouts.
Long term, it would help to have more efficient tests. A lot of what's there
now is something a QE team would traditionally write; orchestrated end-to-end
system tests, except it is better integrated with the build process, and
therefore somewhat easier to debug than a stand-alone test suite (possibly
running on multiple machines or docker containers) would be.
----------------------------------------------------------------
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]
