jiridanek edited a comment 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.
   
   edit: I like splitting the compile and test phases into separate GHA jobs. I 
think the complexity from that is actually outweighed by the clear separation 
of the two phases and the knowledge of what precisely is needed to compile, and 
what files are needed to run the tests, and the ability to fetch the workspace, 
replicate environment (There is PPA repository with Python3.6 for Focal) and 
run what tests I want on my machine from sources compiled in Travis.


----------------------------------------------------------------
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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to