Libcxx buildbot

Project Infrastructure LLVM Dev List Archives
1

Hi folks,

I've updated the configuration for my libcxx buildbot (r220701) to
pass some additional flags to compilation, including setting the CPU
(so it won't need to use soft divide) and link flags + compiler-rt
dependency to lit (so it won't fail with __aeabi_* symbols missing).

Most problems should be all fixed once we reload the configuration in
the build master.

Right now, there's only one failure remaining, which I'm investigating.

backtrace_test.cpp:59: int main(): Assertion `nothrow_ntraced > 1' failed.

cheers,
--renato

2

Right now, there's only one failure remaining, which I'm investigating.

backtrace_test.cpp:59: int main(): Assertion `nothrow_ntraced > 1' failed.

See also: http://lists.cs.uiuc.edu/pipermail/cfe-dev/2014-October/039746.html

3

I’m not sure that test have ever been run through LIT. It was tested on Android, but I don’t have LIT tweaked for libc++abi the same way I do for libc++, so it was built outside of LIT and run manually.

4

+ismail

5

Sadly I have no idea either because this is the first time I enabled check-libcxx{abi} on ARM. But one idea is to try without llvm unwinder.

6

I still have a similar error when using libstdc++ + libgcc_s + libgcc_eh... :frowning:

--renato

7

FYI,

The bot is now updated and the last failure is showing publicly. The
first to have a look at this can use the bot as a final check.

http://lab.llvm.org:8011/builders/libcxx-libcxxabi-arm-linux/builds/23/steps/test.libcxxabi/logs/stdio

cheers,
--renato

8

Hijacking this thread to also mention that the libcxx bot now respects the max number of jobs specified for each bot.
Before LIT would always use all the threads on the machine. This should have been enabled with the latest update.

/Eric