Quantcast

[4.0.0 Release] Release Candidate 2 has been tagged

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[4.0.0 Release] Release Candidate 2 has been tagged

Ammarguellat, Zahira via cfe-dev
Hello testers,

4.0.0-rc2 was just tagged from the branch at r294535.

There are still open relase blocking bugs and merge requests, so this
will not be the last release candidate, but we've had a lot of merges
since the last one, and I'd like to see what the testing looks like.

The test-release.sh script was updated to also include lld. Make sure
you're using the latest version of the script (ideally from the
branch, but the trunk version is identical), and if lld causes any
problems, pass the "-no-lld" flag.

Please build, test, and upload binaries to the sftp. Let me know what
comes up, and I'll publish your binaries plus source and docs when
they're ready.

Thanks,
Hans
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged

Ammarguellat, Zahira via cfe-dev
Hi,

AArch64 good to go.

f27db27da7f75a435d89ba63c8a762885fd86a1a
clang+llvm-4.0.0-rc2-aarch64-linux-gnu.tar.xz

Diana

On 9 February 2017 at 01:33, Hans Wennborg via Release-testers
<[hidden email]> wrote:

> Hello testers,
>
> 4.0.0-rc2 was just tagged from the branch at r294535.
>
> There are still open relase blocking bugs and merge requests, so this
> will not be the last release candidate, but we've had a lot of merges
> since the last one, and I'd like to see what the testing looks like.
>
> The test-release.sh script was updated to also include lld. Make sure
> you're using the latest version of the script (ideally from the
> branch, but the trunk version is identical), and if lld causes any
> problems, pass the "-no-lld" flag.
>
> Please build, test, and upload binaries to the sftp. Let me know what
> comes up, and I'll publish your binaries plus source and docs when
> they're ready.
>
> Thanks,
> Hans
> _______________________________________________
> Release-testers mailing list
> [hidden email]
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [llvm-dev] [4.0.0 Release] Release Candidate 2 has been tagged

Ammarguellat, Zahira via cfe-dev
In reply to this post by Ammarguellat, Zahira via cfe-dev
(stage-3 check-all fails on macOS around libcxxabi but I think it is usual).

I pushed:

9df4d8a9c74ccb1aaaf934f19a48d003917c9d81  rc2/clang+llvm-4.0.0-rc2-x86_64-apple-darwin.tar.xz


Mehdi


> On Feb 8, 2017, at 4:33 PM, Hans Wennborg via llvm-dev <[hidden email]> wrote:
>
> Hello testers,
>
> 4.0.0-rc2 was just tagged from the branch at r294535.
>
> There are still open relase blocking bugs and merge requests, so this
> will not be the last release candidate, but we've had a lot of merges
> since the last one, and I'd like to see what the testing looks like.
>
> The test-release.sh script was updated to also include lld. Make sure
> you're using the latest version of the script (ideally from the
> branch, but the trunk version is identical), and if lld causes any
> problems, pass the "-no-lld" flag.
>
> Please build, test, and upload binaries to the sftp. Let me know what
> comes up, and I'll publish your binaries plus source and docs when
> they're ready.
>
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> [hidden email]
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [4.0.0 Release] Release Candidate 2 has been tagged

Ammarguellat, Zahira via cfe-dev
In reply to this post by Ammarguellat, Zahira via cfe-dev
On Wed, Feb 8, 2017 at 4:33 PM, Hans Wennborg <[hidden email]> wrote:

> Hello testers,
>
> 4.0.0-rc2 was just tagged from the branch at r294535.
>
> There are still open relase blocking bugs and merge requests, so this
> will not be the last release candidate, but we've had a lot of merges
> since the last one, and I'd like to see what the testing looks like.
>
> The test-release.sh script was updated to also include lld. Make sure
> you're using the latest version of the script (ideally from the
> branch, but the trunk version is identical), and if lld causes any
> problems, pass the "-no-lld" flag.
>
> Please build, test, and upload binaries to the sftp. Let me know what
> comes up, and I'll publish your binaries plus source and docs when
> they're ready.
Windows is ready:

1f06e8b327509f36214a224423eb333d48e53be6  LLVM-4.0.0-rc2-win32.exe
f23dcaaf0caf1496300a0e8c00c0f7815c4fb50f  LLVM-4.0.0-rc2-win64.exe

It was built with the attached batch file.

_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

build_llvm_400-rc2._bat_ (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged

Ammarguellat, Zahira via cfe-dev
In reply to this post by Ammarguellat, Zahira via cfe-dev
On 9 Feb 2017, at 01:33, Hans Wennborg via Release-testers <[hidden email]> 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.

-Dimitry



_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

signature.asc (169 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged

Ammarguellat, Zahira via cfe-dev
On Thu, Feb 9, 2017 at 2:23 PM, Dimitry Andric <[hidden email]> wrote:

> On 9 Feb 2017, at 01:33, Hans Wennborg via Release-testers <[hidden email]> 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
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [llvm-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged

Ammarguellat, Zahira via cfe-dev
In reply to this post by Ammarguellat, Zahira via cfe-dev
On 9 February 2017 at 17:55, Diana Picus via llvm-dev
<[hidden email]> wrote:
> Hi,
>
> AArch64 good to go.
>
> f27db27da7f75a435d89ba63c8a762885fd86a1a
> clang+llvm-4.0.0-rc2-aarch64-linux-gnu.tar.xz

No regressions from the ARM side.

f827daf4b0066f74932090cb6309fcf6be594617
clang+llvm-4.0.0-rc2-armv7a-linux-gnueabihf.tar.xz


--renato
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged

Ammarguellat, Zahira via cfe-dev
In reply to this post by Ammarguellat, Zahira via cfe-dev
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
<[hidden email]> wrote:

> On Thu, Feb 9, 2017 at 2:23 PM, Dimitry Andric <[hidden email]> wrote:
>> On 9 Feb 2017, at 01:33, Hans Wennborg via Release-testers <[hidden email]> 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
> [hidden email]
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [llvm-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged

Ammarguellat, Zahira via cfe-dev
On 10 February 2017 at 11:38, Pavel Labath via llvm-dev
<[hidden email]> 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
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [llvm-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged

Ammarguellat, Zahira via cfe-dev
On Fri, Feb 10, 2017 at 3:56 AM, Renato Golin <[hidden email]> wrote:

> On 10 February 2017 at 11:38, Pavel Labath via llvm-dev
> <[hidden email]> 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?

Good question, we're not doing a very good job of documenting this.

And I'm not sure what would be the best way to do it.

A reasonable thing to do would be to put a note on the relaese
downloads page. But I'm not even sure what to put there.  "OpenMP kind
of works on AArch64", what does that mean to a user?

It also comes back to what the nature of the release is. For me, it's
a periodic best-effort-stability snapshot of what we've got, which
packagers and other downstream folks build on.
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [llvm-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged

Ammarguellat, Zahira via cfe-dev
On 10 February 2017 at 22:23, Hans Wennborg <[hidden email]> wrote:
> A reasonable thing to do would be to put a note on the relaese
> downloads page. But I'm not even sure what to put there.  "OpenMP kind
> of works on AArch64", what does that mean to a user?

The idea was to just separate in two classes: supported/not supported.


> It also comes back to what the nature of the release is. For me, it's
> a periodic best-effort-stability snapshot of what we've got, which
> packagers and other downstream folks build on.

That's why I haven't bothered doing it, so far. What we can do is to
continue not doing it until someone really complains, than we try to
find a good solution.

cheers,
--renato
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Openmp-dev] [4.0.0 Release] Release Candidate 2 has been tagged

Ammarguellat, Zahira via cfe-dev
In reply to this post by Ammarguellat, Zahira via cfe-dev
Hi,

I've built, uploaded and partially tested rc2. Looks ok. I'll post if anything crops up.

78afc4479ee0f121ba3080cb04547572  clang+llvm-4.0.0-rc2-mipsel-linux-gnu.tar.xz
9d0aba409e80500224583a6baed6b945  clang+llvm-4.0.0-rc2-mips-linux-gnu.tar.xz
c654db0e66231e2c72c2fcc426e843e5  clang+llvm-4.0.0-rc2-x86_64-linux-gnu-debian8.tar.xz

Thanks,
Simon

> -----Original Message-----
> From: Openmp-dev [mailto:[hidden email]] On Behalf
> Of Hans Wennborg via Openmp-dev
> Sent: 09 February 2017 00:34
> To: Release-testers
> Cc: llvm-dev; cfe-dev; openmp-dev ([hidden email]); LLDB Dev
> Subject: [Openmp-dev] [4.0.0 Release] Release Candidate 2 has been tagged
>
> Hello testers,
>
> 4.0.0-rc2 was just tagged from the branch at r294535.
>
> There are still open relase blocking bugs and merge requests, so this will not
> be the last release candidate, but we've had a lot of merges since the last
> one, and I'd like to see what the testing looks like.
>
> The test-release.sh script was updated to also include lld. Make sure you're
> using the latest version of the script (ideally from the branch, but the trunk
> version is identical), and if lld causes any problems, pass the "-no-lld" flag.
>
> Please build, test, and upload binaries to the sftp. Let me know what comes
> up, and I'll publish your binaries plus source and docs when they're ready.
>
> Thanks,
> Hans
> _______________________________________________
> Openmp-dev mailing list
> [hidden email]
> http://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Loading...