[Release-testers] [4.0.0 Release] Release Candidate 3 has been tagged

[Eric Fiselier via Release-testers]

On Fri, Mar 3, 2017 at 9:05 AM, Renato Golin <renato.golin at linaro.org>
wrote:

> On 2 March 2017 at 19:47, Hans Wennborg via Release-testers
> <release-testers at lists.llvm.org> wrote:
> > Hello testers,
> >
> > 4.0.0-rc3 was just tagged from the branch at r296762.
>
> ARM looks good, bd3c31f080a016409179fa8cb69da4e2fa14c951
> clang+llvm-4.0.0-rc3-armv7a-linux-gnueabihf.tar.xz
>
> AArch64 has a libc++ error we did not see on RC2:
>
> libc++ :: std/thread/thread.condition/thread.condition.condvarany/wait
> _for.pass.cpp
>
> wait_for.pass.cpp.exe:
> /home/renato.golin/devel/llvm/release/rc3/llvm.src/projects/
> libcxx/test/std/thread/thread.condition/thread.condition.con
> dvarany/wait_for.pass.cpp:58:
> void f(): Assertion `t1 - t0 - milliseconds(250) < milliseconds(50)'
> failed.
>
> Copying Eric and Marshall to see if they know of any back-ported
> commit that could cause this or if that's just the test's own
> instability (which seems to be the case).
>

Nothing relevant to this test has changed since the initial 4.0 branch. I
think it's safe to assume
the test is flakey, (Although I've never seen this specific test timeout
before)



>
> Anyway, binaries uploaded: 9356d607c68fbf8de56c03bde70c2964a794d26e
> clang+llvm-4.0.0-rc3-aarch64-linux-gnu.tar.xz
>
>
> > This is a release candidate in the real sense: if no major issues show
> > up with this one, it is the version that will be released.
>
> There is one rename that will land on trunk that needs to be announced
> on 4.0's release notes (https://reviews.llvm.org/D30510), but this
> won't need a new re-spin, just an update on the release notes before
> the final tag.
>
> cheers,
> --renato
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/release-testers/attachments/20170304/b8babab9/attachment.html>