llvm dev - Jul 2019 - [cfe-dev] [Release-testers] LLVM 8.0.1-rc3

Hi,

On Wed, 3 Jul 2019 at 13:08, Dimitry Andric via Release-testers
<release-testers at lists.llvm.org> wrote:
>
> On 28 Jun 2019, at 00:56, Tom Stellard via Release-testers
<release-testers at lists.llvm.org> wrote:
> >
> > I've just tagged LLVM 8.0.1-rc3.  Testers, please begin testing
and report
> > results.
No issues with 8.0.1-rc3 for ARM and AArch64, binaries uploaded as:

35a33e21b3c8fec156946f8202447ff0  clang+llvm-8.0.1-rc3-aarch64-linux-gnu.tar.xz
9a705f24201ad1b78fe8c450080c12ad
clang+llvm-8.0.1-rc3-armv7a-linux-gnueabihf.tar.xz

Thanks

Yvan
> As with 8.0.1 rc2, I had to disable compiler-rt for this test run, as most
of the sanitizers are totally broken. This is tracked in PR40761.
>
> Main test results on amd64-freebsd11:
>
> Expected Passes    : 53266 (rc2: 53259)
> Expected Failures  :   213 (rc2:   213)
> Unsupported Tests  :  1718 (rc2:  1719)
> Unresolved Tests   :     8 (rc2:     8)
> Unexpected Passes  :     3 (rc2:     3)
> Unexpected Failures:    59 (rc2:    63)
>
> Main test results on i386-freebsd11:
>
> Expected Passes    : 53113 (rc2: 53108)
> Expected Failures  :   229 (rc2:   229)
> Unsupported Tests  :  1540 (rc2:  1541)
> Unresolved Tests   :     7 (rc2:     9)
> Unexpected Passes  :     5 (rc2:     5)
> Unexpected Failures:   178 (rc2:   178)
>
> Uploaded:
>
> SHA256 (clang+llvm-8.0.1-rc3-amd64-unknown-freebsd11.tar.xz) =
32d1f5882fa2aba7c982347777dba7bc0dcdcb99b20e455da29d2f7ec5063d11
> SHA256 (clang+llvm-8.0.1-rc3-i386-unknown-freebsd11.tar.xz) =
d82d640f3cd9130a80cf2a70094b9b99ebe7192a5b7e8dd091bdcd764ba7f70c
>
> -Dimitry
>
> _______________________________________________
> Release-testers mailing list
> Release-testers at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers

On Thu, 4 Jul 2019 at 22:16, Yvan Roux via cfe-dev
<cfe-dev at lists.llvm.org> wrote:
> > Expected Passes    : 53266 (rc2: 53259)
> > Expected Failures  :   213 (rc2:   213)
> > Unsupported Tests  :  1718 (rc2:  1719)
> > Unresolved Tests   :     8 (rc2:     8)
Does someone knows what unresolved means?

Chris

On Sat, 2019-07-06 at 14:36 +1200, Christian Gagneraud via Release-
testers wrote:
> On Thu, 4 Jul 2019 at 22:16, Yvan Roux via cfe-dev
> <cfe-dev at lists.llvm.org> wrote:
> > > Expected Passes    : 53266 (rc2: 53259)
> > > Expected Failures  :   213 (rc2:   213)
> > > Unsupported Tests  :  1718 (rc2:  1719)
> > > Unresolved Tests   :     8 (rc2:     8)
> 
> Does someone knows what unresolved means?
> 
It usually means that the test runner hit an unexpected error,
e.g. crashed.

-- 
Best regards,
Michał Górny

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 618 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190707/7da59a33/attachment.sig>

On 6 Jul 2019, at 04:36, Christian Gagneraud <chgans at gmail.com>
wrote:
> 
> On Thu, 4 Jul 2019 at 22:16, Yvan Roux via cfe-dev
> <cfe-dev at lists.llvm.org> wrote:
>>> Expected Passes    : 53266 (rc2: 53259)
>>> Expected Failures  :   213 (rc2:   213)
>>> Unsupported Tests  :  1718 (rc2:  1719)
>>> Unresolved Tests   :     8 (rc2:     8)
> 
> Does someone knows what unresolved means?
Yes, that's when you have to kill the script that runs the individual
test, for example because the test hangs.

In my case, I have some lldb tests that sometimes sit and hang in a STOP
state (these are apparently tests for the stop/continue logic).  In that
case, I have to kill off the tested program and its parent (most of the
time a forked lit.py), leading to "Unresolved" status for that
particular test.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190707/b0e3bfa1/attachment.sig>