[LNT] r198453 - In an effort refactor the code to make way for run resampling, move the run submission code into the test suites.

Tobias Grosser tobias at grosser.es
Sat Jan 4 17:55:01 PST 2014


On 01/05/2014 02:42 AM, Chris Matthews wrote:
> I will have to update some of the bots eventually, because they will now throw a warning now about the order of arguments passed in.
>
> I agree about the importance of not breaking the builds.  The way I currently test the commits is in 3 stages, I run the LNT lit tests, then I run a regression script which I made myself which runs LNT in ~10 common configurations and makes sure they all work on a local server.  Once I commit, I fire off a few of the fastest LNT bots at Apple, and make sure they all work, they generally finish in 25 minutes.

I see. This did not seem to have catched the buildbot + LNT 
configuration our five LNT buildbots are using. If we see more often 
failures in this area, it may be worth investigating how we can test 
those configurations before pushing the changes.

> Can you point me to which bots have those failures?

http://lab.llvm.org:8011/builders/clang-native-arm-lnt/builds/4444/steps/lnt.nightly-test/logs/err.text
http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux/builds/5185/steps/lnt.nightly-test/logs/err.text

And some more testers, too.

Tobi



More information about the llvm-commits mailing list