Hans Wennborg via llvm-dev
2017-Feb-09 22:33 UTC
[llvm-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged
On Thu, Feb 9, 2017 at 2:23 PM, Dimitry Andric <dimitry at andric.com> wrote:> On 9 Feb 2017, at 01:33, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> 4.0.0-rc2 was just tagged from the branch at r294535. > > Building on FreeBSD 10 at least didn't crash this time, and lld built just fine. :) I uploaded the following: > > SHA256 (clang+llvm-4.0.0-rc2-i386-unknown-freebsd10.tar.xz) = 0725eed8060a1a9983432a547a51c78e155584575120e449c41bebd80eb64652 > SHA256 (clang+llvm-4.0.0-rc2-amd64-unknown-freebsd10.tar.xz) = 0b71197a3288b4c7c54f12497b4907257eda71d9be0cb26f9497b25539b5a3c3 > > On i386-freebsd10 there were some interesting test results: > > ******************** > Unexpected Passing Tests (1): > lldb :: Expr/TestCallStdStringFunction.test > > ******************** > Failing Tests (4): > LLVM :: tools/llvm-xray/X86/convert-with-debug-syms.txt > lldb :: Expr/TestCallStopAndContinue.test > lldb :: Expr/TestCallUserAnonTypedef.test > lldb :: Expr/TestCallUserDefinedFunction.test > > On amd64-freebsd10 the lldb failures didn't occur, but the 'unexpected passing' one did, as did the one xray failure. > > The xray failure looks like this: > > FAIL: LLVM :: tools/llvm-xray/X86/convert-with-debug-syms.txt (31351 of 33866) > ******************** TEST 'LLVM :: tools/llvm-xray/X86/convert-with-debug-syms.txt' FAILED ******************** > Script: > -- > /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/llvm-xray convert -m /home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/Inputs/elf64-sample-o2.bin -y /home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/Inputs/naive-log-simple.xray -f=yaml -o - 2>&1 | /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0 > .0-rc2.obj/./bin/FileCheck /home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/convert-with-debug-syms.txt > -- > Exit Code: 1 > > Command Output (stderr): > -- > /home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/convert-with-debug-syms.txt:13:15: error: expected string not found in input > ; CHECK-NEXT: - { type: 0, func-id: 2, function: {{.*foo.*}}, cpu: 37, thread: 84697, kind: function-enter, > ^ > <stdin>:11:2: note: scanning from here > - { type: 0, func-id: 2, function: 'foo(void)', cpu: 37, thread: 84697, > ^ > <stdin>:19:2: note: possible intended match here > - { type: 0, func-id: 3, function: main, cpu: 37, thread: 84697, kind: function-exit, > ^ > > -- > > ******************** > > The lldb test failures look like this: > > FAIL: lldb :: Expr/TestCallUserAnonTypedef.test (32116 of 32394) > ******************** TEST 'lldb :: Expr/TestCallUserAnonTypedef.test' FAILED ******************** > Script: > -- > /home/dim/llvm-4.0.0/rc2/Phase2/Release/llvmCore-4.0.0-rc2.install/usr/local/bin/clang++ /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/Inputs/anonymous-struct.cpp -g -o /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserAnonTypedef.test.tmp && /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/lldb -b -s /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserAnonTypedef.test -- /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserAnonTypedef.test.tmp | /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/FileCheck /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserAnonTypedef.test > -- > Exit Code: 1 > > Command Output (stderr): > -- > error: Can't run the expression locally: Interpreter doesn't handle one of the expression's opcodes > /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserAnonTypedef.test:11:10: error: expected string not found in input > # CHECK: $0 = 1 > ^ > <stdin>:1:1: note: scanning from here > (lldb) target create "/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserAnonTypedef.test.tmp" > ^ > <stdin>:10:18: note: possible intended match here > Breakpoint 1: where = TestCallUserAnonTypedef.test.tmp`main + 55 at anonymous-struct.cpp:25, address = 0x080486b7 > ^ > > -- > > ******************** > > FAIL: lldb :: Expr/TestCallUserDefinedFunction.test (32117 of 32394) > ******************** TEST 'lldb :: Expr/TestCallUserDefinedFunction.test' FAILED ******************** > Script: > -- > /home/dim/llvm-4.0.0/rc2/Phase2/Release/llvmCore-4.0.0-rc2.install/usr/local/bin/clang++ /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/Inputs/call-function.cpp -g -o /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserDefinedFunction.test.tmp && /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/lldb -b -s /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserDefinedFunction.test -- /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserDefinedFunction.test.tmp | /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/FileCheck /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserDefinedFunction.test > -- > Exit Code: 1 > > Command Output (stderr): > -- > error: Can't run the expression locally: Interpreter doesn't handle one of the expression's opcodes > /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserDefinedFunction.test:9:10: error: expected string not found in input > # CHECK: $0 = 5 > ^ > <stdin>:1:1: note: scanning from here > (lldb) target create "/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserDefinedFunction.test.tmp" > ^ > <stdin>:9:18: note: possible intended match here > Breakpoint 1: where = TestCallUserDefinedFunction.test.tmp`main + 591 at call-function.cpp:52, address = 0x0804906f > ^ > > -- > > ******************** > > FAIL: lldb :: Expr/TestCallStopAndContinue.test (32119 of 32394) > ******************** TEST 'lldb :: Expr/TestCallStopAndContinue.test' FAILED ******************** > Script: > -- > /home/dim/llvm-4.0.0/rc2/Phase2/Release/llvmCore-4.0.0-rc2.install/usr/local/bin/clang++ /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/Inputs/call-function.cpp -g -o /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallStopAndContinue.test.tmp && /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/lldb -b -s /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallStopAndContinue.test -o continue -o "thread list" -- /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallStopAndContinue.test.tmp 2>&1 | /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/FileCheck /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallStopAndContinue.test > -- > Exit Code: 1 > > Command Output (stderr): > -- > /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallStopAndContinue.test:10:10: error: expected string not found in input > # CHECK: Execution was interrupted, reason: breakpoint > ^ > <stdin>:1:1: note: scanning from here > (lldb) target create "/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallStopAndContinue.test.tmp" > ^ > <stdin>:15:4: note: possible intended match here > * thread #1, stop reason = breakpoint 1.1 > ^ > > -- > > ******************** > > I don't have enough lldb clue to figure out what's wrong with it, though.What's the status of lldb on FreeBSD, i.e. is it used? Did the tests pass for 3.9?
Pavel Labath via llvm-dev
2017-Feb-10 11:38 UTC
[llvm-dev] [cfe-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged
Ed may be able to elaborate on lldb+freebsd state of things. All I can say is these tests did not exist in 3.9, so I wouldn't call this a regression. (Well... technically, a similar test existed, but it was run by a different test runner which I believe is not hooked up to the command you are running). cheers, pavel On 9 February 2017 at 22:33, Hans Wennborg via cfe-dev <cfe-dev at lists.llvm.org> wrote:> On Thu, Feb 9, 2017 at 2:23 PM, Dimitry Andric <dimitry at andric.com> wrote: >> On 9 Feb 2017, at 01:33, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >>> >>> 4.0.0-rc2 was just tagged from the branch at r294535. >> >> Building on FreeBSD 10 at least didn't crash this time, and lld built just fine. :) I uploaded the following: >> >> SHA256 (clang+llvm-4.0.0-rc2-i386-unknown-freebsd10.tar.xz) = 0725eed8060a1a9983432a547a51c78e155584575120e449c41bebd80eb64652 >> SHA256 (clang+llvm-4.0.0-rc2-amd64-unknown-freebsd10.tar.xz) = 0b71197a3288b4c7c54f12497b4907257eda71d9be0cb26f9497b25539b5a3c3 >> >> On i386-freebsd10 there were some interesting test results: >> >> ******************** >> Unexpected Passing Tests (1): >> lldb :: Expr/TestCallStdStringFunction.test >> >> ******************** >> Failing Tests (4): >> LLVM :: tools/llvm-xray/X86/convert-with-debug-syms.txt >> lldb :: Expr/TestCallStopAndContinue.test >> lldb :: Expr/TestCallUserAnonTypedef.test >> lldb :: Expr/TestCallUserDefinedFunction.test >> >> On amd64-freebsd10 the lldb failures didn't occur, but the 'unexpected passing' one did, as did the one xray failure. >> >> The xray failure looks like this: >> >> FAIL: LLVM :: tools/llvm-xray/X86/convert-with-debug-syms.txt (31351 of 33866) >> ******************** TEST 'LLVM :: tools/llvm-xray/X86/convert-with-debug-syms.txt' FAILED ******************** >> Script: >> -- >> /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/llvm-xray convert -m /home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/Inputs/elf64-sample-o2.bin -y /home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/Inputs/naive-log-simple.xray -f=yaml -o - 2>&1 | /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0 >> .0-rc2.obj/./bin/FileCheck /home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/convert-with-debug-syms.txt >> -- >> Exit Code: 1 >> >> Command Output (stderr): >> -- >> /home/dim/llvm-4.0.0/rc2/llvm.src/test/tools/llvm-xray/X86/convert-with-debug-syms.txt:13:15: error: expected string not found in input >> ; CHECK-NEXT: - { type: 0, func-id: 2, function: {{.*foo.*}}, cpu: 37, thread: 84697, kind: function-enter, >> ^ >> <stdin>:11:2: note: scanning from here >> - { type: 0, func-id: 2, function: 'foo(void)', cpu: 37, thread: 84697, >> ^ >> <stdin>:19:2: note: possible intended match here >> - { type: 0, func-id: 3, function: main, cpu: 37, thread: 84697, kind: function-exit, >> ^ >> >> -- >> >> ******************** >> >> The lldb test failures look like this: >> >> FAIL: lldb :: Expr/TestCallUserAnonTypedef.test (32116 of 32394) >> ******************** TEST 'lldb :: Expr/TestCallUserAnonTypedef.test' FAILED ******************** >> Script: >> -- >> /home/dim/llvm-4.0.0/rc2/Phase2/Release/llvmCore-4.0.0-rc2.install/usr/local/bin/clang++ /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/Inputs/anonymous-struct.cpp -g -o /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserAnonTypedef.test.tmp && /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/lldb -b -s /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserAnonTypedef.test -- /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserAnonTypedef.test.tmp | /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/FileCheck /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserAnonTypedef.test >> -- >> Exit Code: 1 >> >> Command Output (stderr): >> -- >> error: Can't run the expression locally: Interpreter doesn't handle one of the expression's opcodes >> /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserAnonTypedef.test:11:10: error: expected string not found in input >> # CHECK: $0 = 1 >> ^ >> <stdin>:1:1: note: scanning from here >> (lldb) target create "/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserAnonTypedef.test.tmp" >> ^ >> <stdin>:10:18: note: possible intended match here >> Breakpoint 1: where = TestCallUserAnonTypedef.test.tmp`main + 55 at anonymous-struct.cpp:25, address = 0x080486b7 >> ^ >> >> -- >> >> ******************** >> >> FAIL: lldb :: Expr/TestCallUserDefinedFunction.test (32117 of 32394) >> ******************** TEST 'lldb :: Expr/TestCallUserDefinedFunction.test' FAILED ******************** >> Script: >> -- >> /home/dim/llvm-4.0.0/rc2/Phase2/Release/llvmCore-4.0.0-rc2.install/usr/local/bin/clang++ /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/Inputs/call-function.cpp -g -o /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserDefinedFunction.test.tmp && /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/lldb -b -s /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserDefinedFunction.test -- /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserDefinedFunction.test.tmp | /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/FileCheck /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserDefinedFunction.test >> -- >> Exit Code: 1 >> >> Command Output (stderr): >> -- >> error: Can't run the expression locally: Interpreter doesn't handle one of the expression's opcodes >> /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallUserDefinedFunction.test:9:10: error: expected string not found in input >> # CHECK: $0 = 5 >> ^ >> <stdin>:1:1: note: scanning from here >> (lldb) target create "/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallUserDefinedFunction.test.tmp" >> ^ >> <stdin>:9:18: note: possible intended match here >> Breakpoint 1: where = TestCallUserDefinedFunction.test.tmp`main + 591 at call-function.cpp:52, address = 0x0804906f >> ^ >> >> -- >> >> ******************** >> >> FAIL: lldb :: Expr/TestCallStopAndContinue.test (32119 of 32394) >> ******************** TEST 'lldb :: Expr/TestCallStopAndContinue.test' FAILED ******************** >> Script: >> -- >> /home/dim/llvm-4.0.0/rc2/Phase2/Release/llvmCore-4.0.0-rc2.install/usr/local/bin/clang++ /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/Inputs/call-function.cpp -g -o /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallStopAndContinue.test.tmp && /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/lldb -b -s /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallStopAndContinue.test -o continue -o "thread list" -- /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallStopAndContinue.test.tmp 2>&1 | /home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/./bin/FileCheck /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallStopAndContinue.test >> -- >> Exit Code: 1 >> >> Command Output (stderr): >> -- >> /home/dim/llvm-4.0.0/rc2/llvm.src/tools/lldb/lit/Expr/TestCallStopAndContinue.test:10:10: error: expected string not found in input >> # CHECK: Execution was interrupted, reason: breakpoint >> ^ >> <stdin>:1:1: note: scanning from here >> (lldb) target create "/home/dim/llvm-4.0.0/rc2/Phase3/Release/llvmCore-4.0.0-rc2.obj/tools/lldb/lit/Expr/Output/TestCallStopAndContinue.test.tmp" >> ^ >> <stdin>:15:4: note: possible intended match here >> * thread #1, stop reason = breakpoint 1.1 >> ^ >> >> -- >> >> ******************** >> >> I don't have enough lldb clue to figure out what's wrong with it, though. > > What's the status of lldb on FreeBSD, i.e. is it used? Did the tests > pass for 3.9? > _______________________________________________ > cfe-dev mailing list > cfe-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Renato Golin via llvm-dev
2017-Feb-10 11:56 UTC
[llvm-dev] [cfe-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged
On 10 February 2017 at 11:38, Pavel Labath via llvm-dev <llvm-dev at lists.llvm.org> wrote:> All I can say is these tests did not exist in 3.9, so I wouldn't call > this a regression. (Well... technically, a similar test existed, but > it was run by a different test runner which I believe is not hooked up > to the command you are running).We're on a similar state for libc++ / openmp / lld on ARM and AArch64. libc++ works well on ARM and AArch64, but some of the tests fail (always have), and I think Eric said it has to do with how we run them or which ones should be disabled. LLD works well on AArch64 but not yet on ARM (though there were no test failures this time). OpenMP kind of works, but there are many failures, which we won't look into this cycle. Regardless of that state, we though it was a good idea to ship it as an experimental status, so that people can try out and report bugs. All the components above are included in both ARM and AArch64 releases. Hans, Do you think we should have a table of production vs. experimental quality per target on the release notes, so that users know what to expect? Or should we just let users know that when they report bugs? cheers, --renato