Thanks to Daniel, we have a new home for the validator buildbot. Thanks,
Daniel!
Go to http://google1.osuosl.org:8080 and have a look.
-Dave
Looks like the x86_64 buildsbots are failing:
/.AUTO/cray/iss.compiler/cost/tools/llvm-tools/x86_64-unknown-linux-gnu/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.1.2/../../../../x86_64-unknown-linux-gnu/bin/ld: /.AUTO/cray/iss.compiler/cost/tools/llvm-tools/x86_64-unknown-linux-gnu/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.1.2/../../../../lib64/libstdc++.a(ctype.o): relocation R_X86_64_32S against `vtable for std::ctype<char>' can not be used when making a shared object; recompile with -fPIC
/.AUTO/cray/iss.compiler/cost/tools/llvm-tools/x86_64-unknown-linux-gnu/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.1.2/../../../../lib64/libstdc++.a: could not read symbols: Bad value
Are those files from llvm-gcc, or system's gcc?
Also this one seems to be a successful build, yet buildbot flagged it as failed:
http://google1.osuosl.org:8080/builders/llvm-validate-debug-northwood-linux/builds/1/steps/llvm-gcc-4.2_compile/logs/stdio
Best regards,
--Edwin
> Go to http://google1.osuosl.org:8080 and have a look.
Looks like the x86_64 buildsbots are failing:
/.AUTO/cray/iss.compiler/cost/tools/llvm-tools/x86_64-unknown-linux-gnu/bin
/../lib/gcc/x86_64-unknown-linux-gnu/4.1.2/../../../../x86_64-unknown-linux-
gnu/bin/ld:
/.AUTO/cray/iss.compiler/cost/tools/llvm-tools/x86_64-unknown-linux-gnu/bin
/../lib/gcc/x86_64-unknown-linux-gnu/4.1.2/../../../../lib64/libstdc++.a(cty
pe.o): relocation R_X86_64_32S against `vtable for std::ctype<char>' can not
be used when making a shared object; recompile with -fPIC
/.AUTO/cray/iss.compiler/cost/tools/llvm-tools/x86_64-unknown-linux-gnu/bin
/../lib/gcc/x86_64-unknown-linux-gnu/4.1.2/../../../../lib64/libstdc++.a:
could not read symbols: Bad valueAre those files from llvm-gcc, or system's gcc?
I was a slave problem. It's fixed now.
Also this one seems to be a successful build, yet buildbot flagged it as
failed:
http://google1.osuosl.org:8080/builders/llvm-validate-debug-northwood-linux
/builds/1/steps/llvm-gcc-4.2_compile/logs/stdio
Yep, I noticed that too. I've got to investigate why that's happening.
google1 went down so I had to restart everything.
-Dave
Google1 didn't actually go down
dannyb@google1:~$ uptime
20:34:12 up 61 days, 2:41, 1 user, load average: 0.00, 0.00, 0.00
Not sure what happened
Looks like someone restarted buildbot using restart instead of reconfig.