[LLVMdev] LNT BenchmarkGame
daniel at zuster.org
Tue Mar 12 09:43:47 PDT 2013
This is probably a platform specific dependency where the Linux output file
differs from the Darwin one. I fixed up a lot of those in the past but the
random number issue blocks some others. For reference see LLVM r111522.
On my machine I get output that matches the reference output:
ddunbar at ozzy-2:BenchmarkGame (master)$ clang puzzle.c && ./a.out
Found duplicate: 4
Found duplicate: 485365
Found duplicate: 417267
Found duplicate: 436989
Found duplicate: 60067
The best solution is that which I mention in r111522 - build some extra
runtime support code that each benchmark can use, and include a platform
stable RNG in it.
On Tue, Mar 12, 2013 at 6:56 AM, Renato Golin <renato.golin at linaro.org>wrote:
> Hi folks,
> I'm investigating the LNT failures on our bot and found that I cannot
> reproduce BenchmarkGame pass.
> I've compiled it with GCC, Clang on both ARM and x86_64, with -O3 or with
> the arguments that the test-suite passes to it and all I can get is the
> result below:
> Found duplicate: 420094
> Found duplicate: 341335
> Found duplicate: 150397
> Found duplicate: 157527
> Found duplicate: 269724
> But not the one that is on the reference output:
> Found duplicate: 4
> Found duplicate: 485365
> Found duplicate: 417267
> Found duplicate: 436989
> Found duplicate: 60067
> If I run the LNT on my machine (x86_64) that test fails, and if I change
> the reference output to the one above, it passes.
> On the ARM buildbot I'm also getting the same results, so I'm really
> surprised that the x86_64 LNT buildbot is passing. PowerPC is also failing,
> and I suspect for the same reason.
> Is there any chance that the results are not being checked correctly? Any
> other ideas? I'm tempted to just change the reference output and see what
> happens with the other bots...
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev