Re: [lldb-dev] [Release-testers] [cfe-dev] LLVM 8.0.1-rc3

2019-07-07 Thread Michał Górny via lldb-dev 
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
>  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



signature.asc
Description: This is a digitally signed message part
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] [Release-testers] LLVM 8.0.1-rc3

2019-07-07 Thread Dimitry Andric via lldb-dev 
On 6 Jul 2019, at 04:36, Christian Gagneraud  wrote:
> 
> On Thu, 4 Jul 2019 at 22:16, Yvan Roux via cfe-dev
>  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



signature.asc
Description: Message signed with OpenPGP
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev