gemmellr commented on pull request #809: URL: https://github.com/apache/qpid-dispatch/pull/809#issuecomment-668642821
> 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 logs. Or not use -j2? How much of a difference does it make? You commented later its mainly for excercising bwrap and is more useful on Travis. > Using four shards, as adding more does not help much. Presumably due to all the setup costs relative to the time spent on tests, or the fact 1 shard is clearly longer than others and maybe still ends up that way? Also, did you try less than 4? I see one of them has a test run around twice as long as most others, so unless all the long-running tests are perfectly spaced to fall in that shard, is it possible having less shards might actually distribute the test time more evenly such that it isnt much slower overall (if at all; it could even be faster if the tests group better), while giving less different output areas to look at (not personally a huge fan of the sharding, significantly complicates the build config and results, may point to some inefficient tests that it seems needed to begin with) > I also couldn't find a way to use here the artifacts that the Proton pipeline is building. I think thats fine, possibly even preferable. Its not that lengthy a build, and its likely to eventually want different versions as e.g the Travis tests use. ---------------------------------------------------------------- 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]
