Will Schmidt
2014-Mar-14 18:10 UTC
[LLVMdev] clang/lnt buildbot on F20 "lnt: error: no such option: -m" ...
Hi Since the buildbot host was updated to Fedora F20 levels, the clang buildbot has been failing with the following: $ /home/clangbuild/clang-ppc64-1/lnt.venv/bin/lnt runtest --verbose --submit http://llvm.org/perf/submitRun --commit=1 nt --sandbox nt --no-timestamp --cc /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang --cxx /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang++ --without-llvm --test-suite /home/clangbuild/clang-ppc64-1/test-suite --no-machdep-info chinook-clangslave1__O3-plain --multisample=3 -mcpu=native main.py:147: warning: --commit should be passed directly to the test suite. main.py:147: warning: --verbose should be passed directly to the test suite. main.py:147: warning: --submit should be passed directly to the test suite. Usage: lnt runtest nt [options] tester-name .... lnt: error: no such option: -m I have removed the clang-ppc64-1 subdirectory, and the buildbot has entirely recreated and refreshed it's contents. I'm wondering if there is a python version or other incompatibility that has been introduced here, but it's not obvious to me. Any suggestions on how to (easily?) identify the issue? Host is currently running python-2.7.5-9.fc20, python-virtualenv-1.10.1-1. Thanks, -Will
Hal Finkel
2014-May-29 18:15 UTC
[LLVMdev] clang/lnt buildbot on F20 "lnt: error: no such option: -m" ...
Hi,
Will, is this still a problem?
http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux/builds/8555/steps/svn-llvm/logs/stdio:
svn: E000028: Can't write to file
'/home/buildbots/clang-ppc64-1/llvm.src/.svn/tmp/svn-Iiv67n': No space
left on device
http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux2/builds/15025/steps/check-all_1/logs/stdio:
Failing Tests (4):
Clang :: CodeGenCXX/debug-info-same-line.cpp
Clang :: Modules/cxx-irgen.cpp
Clang :: OpenMP/parallel_codegen.cpp
LLVM-Unit :: ADT/Release+Asserts/ADTTests/HashingTest.HashCombineBasicTest
For these, we need to figure out if these are test problems or miscompiles.
-Hal
----- Original Message -----> From: "Will Schmidt" <will_schmidt at vnet.ibm.com>
> To: "Lista LLVM-dev" <llvmdev at cs.uiuc.edu>
> Sent: Friday, March 14, 2014 1:10:35 PM
> Subject: [LLVMdev] clang/lnt buildbot on F20 "lnt: error: no such
option: -m" ...
>
> Hi
> Since the buildbot host was updated to Fedora F20 levels, the clang
> buildbot has been failing with the following:
>
> $ /home/clangbuild/clang-ppc64-1/lnt.venv/bin/lnt runtest --verbose
> --submit http://llvm.org/perf/submitRun --commit=1 nt --sandbox nt
> --no-timestamp --cc
> /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang --cxx
> /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang++
> --without-llvm --test-suite
> /home/clangbuild/clang-ppc64-1/test-suite --no-machdep-info
> chinook-clangslave1__O3-plain --multisample=3 -mcpu=native
> main.py:147: warning: --commit should be passed directly to the test
> suite.
> main.py:147: warning: --verbose should be passed directly to the test
> suite.
> main.py:147: warning: --submit should be passed directly to the test
> suite.
> Usage: lnt runtest nt [options] tester-name
> ....
> lnt: error: no such option: -m
>
> I have removed the clang-ppc64-1 subdirectory, and the buildbot has
> entirely recreated and refreshed it's contents. I'm wondering if
> there is a python version or other incompatibility that has been
> introduced here, but it's not obvious to me.
>
> Any suggestions on how to (easily?) identify the issue?
> Host is currently running python-2.7.5-9.fc20,
> python-virtualenv-1.10.1-1.
>
> Thanks,
> -Will
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
--
Hal Finkel
Assistant Computational Scientist
Leadership Computing Facility
Argonne National Laboratory
Will Schmidt
2014-May-29 19:11 UTC
[LLVMdev] clang/lnt buildbot on F20 "lnt: error: no such option: -m" ...
On Thu, 2014-05-29 at 13:15 -0500, Hal Finkel wrote:> Hi, > > Will, is this still a problem? > > http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux/builds/8555/steps/svn-llvm/logs/stdio: > svn: E000028: Can't write to file '/home/buildbots/clang-ppc64-1/llvm.src/.svn/tmp/svn-Iiv67n': No space left on deviceI've just moved the bots to a different box, and cleaned up a bunch (~ 20G worth) of core.* files, so the disk space issue should be cleared up, at least for the moment. Not sure if the F20/LNT issue will magically clear up on this new host, or not. If it' doesn't, i'll need to dig in. Once the current builds finish, i'll have a better feel for whats broken..> > http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux2/builds/15025/steps/check-all_1/logs/stdio: > Failing Tests (4): > Clang :: CodeGenCXX/debug-info-same-line.cpp> Clang :: Modules/cxx-irgen.cpp > Clang :: OpenMP/parallel_codegen.cppIIRC the fail for those two is due to a signext attribute showing up for ppc*. I'll see if I can verify that and get something pushed soonish.> LLVM-Unit :: ADT/Release+Asserts/ADTTests/HashingTest.HashCombineBasicTest > > For these, we need to figure out if these are test problems or miscompiles. > > -Hal > > ----- Original Message ----- > > From: "Will Schmidt" <will_schmidt at vnet.ibm.com> > > To: "Lista LLVM-dev" <llvmdev at cs.uiuc.edu> > > Sent: Friday, March 14, 2014 1:10:35 PM > > Subject: [LLVMdev] clang/lnt buildbot on F20 "lnt: error: no such option: -m" ... > > > > Hi > > Since the buildbot host was updated to Fedora F20 levels, the clang > > buildbot has been failing with the following: > > > > $ /home/clangbuild/clang-ppc64-1/lnt.venv/bin/lnt runtest --verbose > > --submit http://llvm.org/perf/submitRun --commit=1 nt --sandbox nt > > --no-timestamp --cc > > /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang --cxx > > /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang++ > > --without-llvm --test-suite > > /home/clangbuild/clang-ppc64-1/test-suite --no-machdep-info > > chinook-clangslave1__O3-plain --multisample=3 -mcpu=native > > main.py:147: warning: --commit should be passed directly to the test > > suite. > > main.py:147: warning: --verbose should be passed directly to the test > > suite. > > main.py:147: warning: --submit should be passed directly to the test > > suite. > > Usage: lnt runtest nt [options] tester-name > > .... > > lnt: error: no such option: -m > > > > I have removed the clang-ppc64-1 subdirectory, and the buildbot has > > entirely recreated and refreshed it's contents. I'm wondering if > > there is a python version or other incompatibility that has been > > introduced here, but it's not obvious to me. > > > > Any suggestions on how to (easily?) identify the issue? > > Host is currently running python-2.7.5-9.fc20, > > python-virtualenv-1.10.1-1. > > > > Thanks, > > -Will > > > > _______________________________________________ > > LLVM Developers mailing list > > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > >