[llvm-dev] [Release-testers] [11.0.0 Release] Release Candidate 5 is here

Wed Sep 30 16:29:39 PDT 2020

What I usually do is

grep -n 'Expectedly Failed' testing.11.0.0-rc5.log

This will give two lines (shown here as examples).

99700:  Expectedly Failed:   241
211999:  Expectedly Failed:   248

Get the text around the second line.

sed -n 211980,212005p testing.11.0.0-rc5.log

It sounds like you are saying there are two errors and that may appear 
in the totals counts in an Unexpected Failures line after the Expectedly 
Failed line.

The detail of the errors will commonly be immediately above the totals 
counts area and can be seen by reducing the start line number enough in 
the above sed command. You can then copy the errors to the llvm-dev list 
or create a blocking bug tied to https://llvm.org/pr46725 as noted below.

Neil Nelson

On 9/30/20 4:54 PM, Shoaib Meenai via llvm-dev wrote:
>
> https://www.dropbox.com/s/ovb47c2rpmr2c17/clang%2Bllvm-11.0.0-rc5-x86_64-apple-darwin.tar.xz?dl=1
>
> 2d4163b1fb5c5d1514883f7ce02286dc63befad70b02ad9c368a0b861bf5dfb5 
> clang+llvm-11.0.0-rc5-x86_64-apple-darwin.tar.xz
>
> Two libunwind tests failed for me. I haven’t dug into why; has this 
> been seen before?
>
>   libunwind :: libunwind_01.pass.cpp
>
>   libunwind :: signal_frame.pass.cpp
>
> *From: *Tobias Hieta <tobias at plexapp.com>
> *Date: *Wednesday, September 30, 2020 at 11:42 AM
> *To: *Shoaib Meenai <smeenai at fb.com>
> *Cc: *Hans Wennborg <hans at chromium.org>, llvm-dev 
> <llvm-dev at lists.llvm.org>, Release-testers 
> <release-testers at lists.llvm.org>, cfe-dev <cfe-dev at lists.llvm.org>
> *Subject: *Re: [llvm-dev] [Release-testers] [11.0.0 Release] Release 
> Candidate 5 is here
>
> Shoabi,
>
> Thanks that would be great - llvm comes with a script that builds and 
> runs the tests in llvm/utils/release/test-release.sh
>
> I usually create a release directory and then invoke it like this
>
> ../llvm/utils/release/test-release.sh -release 11.0.0 -rc 5 -triple 
> x86_64-apple-darwin -use-ninja -j <jobs>
>
> That takes two hours or so then I inspect the log file for testing errors:
>
> grep "FAIL:" logs/testing-rc5.txt (I think don't remember exactly the 
> name of the file).
>
> make sha256 sum: shasum -a 256 clang+llvm-....tar.xz
>
> And then upload to the sftp server, but in this case - feel free to 
> put it on gdrive or something like that and I can upload it to the 
> sftp server for Hans to add to the release.
>
> Thanks for helping out!
>
> -- Tobias
>
> On Wed, Sep 30, 2020, 20:30 Shoaib Meenai <smeenai at fb.com 
> <mailto:smeenai at fb.com>> wrote:
>
>     I’m happy to run them, although I’d appreciate a pointer to the
>     appropriate documentation.
>
>     *From: *llvm-dev <llvm-dev-bounces at lists.llvm.org
>     <mailto:llvm-dev-bounces at lists.llvm.org>> on behalf of Tobias
>     Hieta via llvm-dev <llvm-dev at lists.llvm.org
>     <mailto:llvm-dev at lists.llvm.org>>
>     *Reply-To: *Tobias Hieta <tobias at plexapp.com
>     <mailto:tobias at plexapp.com>>
>     *Date: *Wednesday, September 30, 2020 at 11:15 AM
>     *To: *Hans Wennborg <hans at chromium.org <mailto:hans at chromium.org>>
>     *Cc: *llvm-dev <llvm-dev at lists.llvm.org
>     <mailto:llvm-dev at lists.llvm.org>>, Release-testers
>     <release-testers at lists.llvm.org
>     <mailto:release-testers at lists.llvm.org>>, cfe-dev
>     <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>>
>     *Subject: *Re: [llvm-dev] [Release-testers] [11.0.0 Release]
>     Release Candidate 5 is here
>
>     Just a heads up - I won't be able to do any macOS builds for a bit
>     - my mac pro has died and needs to be replaced. I hope to get a
>     replacement next week, but meanwhile I won't be able to do any
>     testing or binary uploads.
>
>     Let me know if anyone else with a mac have some CPU cycles to
>     spare for this release.
>
>     On Wed, Sep 30, 2020, 20:07 Hans Wennborg via Release-testers
>     <release-testers at lists.llvm.org
>     <mailto:release-testers at lists.llvm.org>> wrote:
>
>         Hello again,
>
>         We had to pick up another bug fix, so here is another release
>         candidate: llvmorg-11.0.0-rc5 tag was just created.
>
>         Source code and docs are available at
>         https://prereleases.llvm.org/11.0.0/#rc5
>         <https://urldefense.proofpoint.com/v2/url?u=https-3A__prereleases.llvm.org_11.0.0_-23rc5&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=o3kDXzdBUE3ljQXKeTWOMw&m=3zO32sQ9J9Z9mUnLnq680ymJQIXb2lfSJmWhpITb_Bc&s=eSHtDFZDrkM3cwwi5gh5J2_jKrdJXbHV38g2H13_eB4&e=>
>         and
>         https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc5
>
>         Pre-built binaries will be added as they become ready.
>
>         Please file reports for any bugs you find as blockers of
>         https://llvm.org/pr46725
>         <https://urldefense.proofpoint.com/v2/url?u=https-3A__llvm.org_pr46725&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=o3kDXzdBUE3ljQXKeTWOMw&m=3zO32sQ9J9Z9mUnLnq680ymJQIXb2lfSJmWhpITb_Bc&s=HaARfs5F1mITNzZgOymyhtSfceC_cfGSk4Tj_sMsm7g&e=>
>
>         Release testers, if you still have cycles (perhaps you didn't even
>         have time to start rc4 yet), please run the test script, share
>         your
>         results, and upload binaries.
>
>         As mentioned above, this rc is very similar to the previous
>         one. There
>         are no open blockers, so it could be the last release candidate.
>
>         Thanks,
>         Hans
>         _______________________________________________
>         Release-testers mailing list
>         Release-testers at lists.llvm.org
>         <mailto:Release-testers at lists.llvm.org>
>         https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>         <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.llvm.org_cgi-2Dbin_mailman_listinfo_release-2Dtesters&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=o3kDXzdBUE3ljQXKeTWOMw&m=3zO32sQ9J9Z9mUnLnq680ymJQIXb2lfSJmWhpITb_Bc&s=gG3ZTP7fh_31TMQ9rmin300CiIdKb9eyC3cSGSJze-M&e=>
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200930/d9409872/attachment-0001.html>