search for: sles11.3

Displaying 20 results from an estimated 49 matches for "sles11.3".

2016 Aug 20
2
[Release-testers] [3.9 Release] Release Candidate 2 has been tagged
When I tested rc1 I found that some of the test suite wouldn't build on SLES11.3 as a consequence of changes to the tests. At least some of the msan tests have been changed leverage features of glibc newer than is available on this platform. I asked about a minimum-required glibc but didn't hear back. Is the minimum required glibc for 3.9 different from 3.8? When I tried rc1 on
2016 Aug 20
2
[Release-testers] [3.9 Release] Release Candidate 2 has been tagged
It's a test for the new interceptor for prlimit. It could be disabled with __GLIBC_PREREQ for 2.13+. On Fri, Aug 19, 2016 at 5:16 PM, Hans Wennborg <hans at chromium.org> wrote: > +Evgenii for msan. > > I suspect the community simply doesn't keep track of what glibc > version is required :-/ > > On Fri, Aug 19, 2016 at 5:10 PM, Brian Cain <brian.cain at
2016 Jan 07
3
[3.7.1 Release] -final has been tagged.
Hmm, the clang+llvm-3.7.1-x86_64-sles11.3-linux-gnu.tar.xz tarball I uploaded doesn't seem to have made it on to this releases dir. I'm still a bit new to the process, is there a step that I skipped? On Wed, Jan 6, 2016 at 4:13 AM, Sedat Dilek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Mon, Jan 4, 2016 at 9:59 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote:
2016 Dec 04
2
[Release-testers] 3.9.1-rc2 is ready for testing
Here's the failing tests for rc2 on SLES11.3 (glibc 2.11, libstdc++4.7). I've done some amount of triaging what some critical elements of the failures are. Unabridged log is attached. Failing Tests (94): LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestAsyncIntInt LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestAsyncVoidBool LLVM-Unit ::
2016 Mar 03
8
[3.8 Release] 'final' has been tagged
Dear testers, My list of blockers is empty, and there were no new problems discovered with rc3, so I have gone ahead and tagged 3.8.0-final [1]. Please build the final binaries and upload to the sftp. For others following along: yes, this means 3.8.0 is complete, but it takes a couple of days to get the source and binary tarballs built. I will send the release announcement when everything's
2019 Mar 18
4
[8.0.0 Release] The final tag is in
Dear testers, The final version of 8.0.0 was just tagged from the release_80 branch at r356364. It's identical to rc5 except for a few documentation changes. Apologies for being behind schedule. It took longer than planned this time. Please build the final binaries and upload to the sftp. For those following along: this means 8.0.0 is done, but it will take a few days to get all the
2018 May 03
3
5.0.2-final has been tagged
Hi, 5.0.2-final has been tagged. Testers may begin uploading binaries. Thanks, Tom
2018 May 04
0
[Release-testers] 5.0.2-final has been tagged
Uploaded SLES11 and ubuntu 14.04. I can work on ubuntu 16.04 next. Is there any demand for ubuntu 17.10 releases? 4a0cb3e0ee573fb94e6c4f6be6c06eb661960471 clang+llvm-5.0.2-x86_64-linux-sles11.3.tar.xz 90430f7f0058100265352b1b2a2cd57e55558f92 clang+llvm-5.0.2-x86_64-linux-gnu-ubuntu-14.04.tar.xz On Thu, May 3, 2018 at 10:57 AM, Tom Stellard via Release-testers < release-testers at
2017 Dec 01
0
[Release-testers] 5.0.1-rc2 has been tagged
On Wed, Nov 29, 2017 at 6:19 PM, Tom Stellard via Release-testers < release-testers at lists.llvm.org> wrote: > Hi, > > I've tagged the 5.0.1-rc2 release, go ahead and start testing and report > your results. > > > SLES11 uploaded. 1312db7bdfd05c82dd52983f8c5df1a6819df79f clang+llvm-5.0.1-rc2-linux-x86_64-sles11.3.tar.xz -------------- next part -------------- An
2018 Feb 24
0
[Release-testers] [6.0.0 Release] Release Candidate 3 tagged
SLES11 binaries for rc3 uploaded. 55b63de8adc12c67eb11abcf1a5f7132cca59b4e clang+llvm-6.0.0-rc3-x86_64-linux-sles11.3.tar.xz On Fri, Feb 23, 2018 at 9:14 AM, Hans Wennborg via Release-testers < release-testers at lists.llvm.org> wrote: > Dear testers, > > 6.0.0-rc3 was just tagged, after r325901 on the branch. > > There are still a few open blockers, but I'm not sure
2018 Dec 24
2
[Release-testers] 7.0.1-final has been tagged
Ubuntu and SLES tarballs uploaded. I haven't had a chance to make a SLES12 build yet, but I will try in the coming days. f7553a0d66092ca0bbe1eab2af405523a18bafba clang+llvm-7.0.1-x86_64-linux-gnu-ubuntu-18.04.tar.xz 41db01a3b216df4fc22fae9c44e248889f9a01ed clang+llvm-7.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz caf149635742622a3a5b220146ff34f9202b8670
2016 Aug 19
8
[3.9 Release] Release Candidate 2 has been tagged
Dear testers, 3.9.0-rc2 was just tagged from the 3.9 branch at r279183. This is a release candidate in the very real sense that if nothing new comes up, this is be what the final release looks like. There are currently no open release blockers, and no patches in my merge-queue. Please build, test, and upload binaries to the sftp. Let me know how everything goes. >From this point, the branch
2019 Jan 09
2
[Release-testers] [cfe-dev] 7.0.1-final has been tagged
On 01/08/2019 11:36 AM, Ian Tessier via Release-testers wrote: > Can the ubuntu tarballs be published to the download site? They're not available yet. > These are up on the download site now. -Tom > On Mon, Dec 24, 2018 at 7:38 AM Brian Cain via cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote: > > Ubuntu and SLES tarballs
2015 Dec 10
9
[3.7.1 Release] -final has been tagged.
Hi, I've tagged the final version of 3.7.1. There is no difference from 3.7.1-rc2, so testers just need to build the packages no testing is required. -Tom
2018 Mar 04
0
[Release-testers] [6.0.0 Release] The final tag is in
Uploaded ubuntu, SLES11, SLES12 binaries. 4907dbd37f4e5265a2f1252d9d7b5e5b0a9c0ec1 clang+llvm-6.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz 360b26fcd9eafe5ca9c4baa89c38339bc587c094 clang+llvm-6.0.0-x86_64-linux-sles11.3.tar.xz ce525cf949ef86409bc3f4f492035225989eecfd clang+llvm-6.0.0-x86_64-linux-sles12.2.tar.xz On Fri, Mar 2, 2018 at 6:17 AM, Hans Wennborg via Release-testers < release-testers
2017 Aug 11
2
[Release-testers] [5.0.0 Release] Release Candidate 2 tagged
I'm not aware of a bug filed for this, so please file one. I don't know much about the workings of test-suite myself, though. On Fri, Aug 11, 2017 at 2:54 PM, Brian Cain <brian.cain at gmail.com> wrote: > Much or all of "Bitcode/simd_ops/simd_ops_*.test" (254 failures) seem to be > failing for me with SIGILL. I'm guessing that my host CPU doesn't support
2017 Dec 07
7
5.0.1-rc3 has been tagged
Hi, I've just tagged 5.0.1-rc3, please test and report the results. Hopefully, this will be the last RC and the final release will be next week. -Tom
2019 Feb 27
5
[8.0.0 Release] rc3 has been tagged
Dear testers, 8.0.0-rc3 was just tagged from the release_80 branch at r355015. We're running a little behind schedule now, but I think we're also close to be able to call this done. Please take a close look at this release candidate. Unless anything bad comes up, this is probably very similar to what the final release will look like. Testers, please run the test script, share your
2019 Mar 12
6
[8.0.0 Release] rc5 has been tagged
Dear testers, 8.0.0-rc5 was just tagged from the release_80 branch at r355909. This is identical to rc4 with the addition of r355743. Hopefully it is the final release candidate, so please give it a good testing. As usual, please run the test script, share your results, and upload binaries. I'll publish source tarballs and docs as soon as possible, and binaries as they become available.
2016 Dec 02
9
3.9.1-rc2 is ready for testing
Hi, I just tagged 3.9.1-rc2, so testing can begin. There was a bug found in -rc1 before I could send out a release announcement, so I decided to merge the fix and tag -rc2 to save some testing cycles. We can always use more testers, so if you are interested in helping, let me know. Thanks, Tom