On Wed, 3 Jul 2019 at 13:08, Dimitry Andric via Release-testers
<[hidden email]> wrote:
> On 28 Jun 2019, at 00:56, Tom Stellard via Release-testers <[hidden email]> 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:
On 6 Jul 2019, at 04:36, Christian Gagneraud <[hidden email]> wrote:
> On Thu, 4 Jul 2019 at 22:16, Yvan Roux via cfe-dev
> <[hidden email]> 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