Brian Cain via llvm-dev
2016-Aug-20 00:10 UTC
[llvm-dev] [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 sles11.3 x86_64, msan's getrlimit test fails to build for lack of prlimit(). SLES11.3 has glibc 2.11.3. Is there a minimum required glibc? I think this test implementation previously used getrlimit(), which is present on glibc2.11.3. On Fri, Aug 19, 2016 at 11:22 AM, Diana Picus via Release-testers < release-testers at lists.llvm.org> wrote:> Hi, > > All good on AArch64 - we've uploaded the binaries. > > Regards, > Diana > > On 19 August 2016 at 04:51, Hans Wennborg via Release-testers > <release-testers at lists.llvm.org> wrote: > > 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 is only open for fixing critical problems > > (bad enough to warrant another test cycle) and release notes. > > > > Thanks, > > Hans > > _______________________________________________ > > Release-testers mailing list > > Release-testers at lists.llvm.org > > http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > _______________________________________________ > Release-testers mailing list > Release-testers at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers >-- -Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160819/3f58a153/attachment.html>
Hans Wennborg via llvm-dev
2016-Aug-20 00:16 UTC
[llvm-dev] [Release-testers] [3.9 Release] Release Candidate 2 has been tagged
+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 gmail.com> wrote:> 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 sles11.3 x86_64, msan's getrlimit test fails to build > for lack of prlimit(). SLES11.3 has glibc 2.11.3. Is there a minimum > required glibc? I think this test implementation previously used > getrlimit(), which is present on glibc2.11.3. > > > On Fri, Aug 19, 2016 at 11:22 AM, Diana Picus via Release-testers > <release-testers at lists.llvm.org> wrote: >> >> Hi, >> >> All good on AArch64 - we've uploaded the binaries. >> >> Regards, >> Diana >> >> On 19 August 2016 at 04:51, Hans Wennborg via Release-testers >> <release-testers at lists.llvm.org> wrote: >> > 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 is only open for fixing critical problems >> > (bad enough to warrant another test cycle) and release notes. >> > >> > Thanks, >> > Hans >> > _______________________________________________ >> > Release-testers mailing list >> > Release-testers at lists.llvm.org >> > http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers >> _______________________________________________ >> Release-testers mailing list >> Release-testers at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > > > > > -- > -Brian
Evgenii Stepanov via llvm-dev
2016-Aug-20 00:40 UTC
[llvm-dev] [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 gmail.com> wrote: >> 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 sles11.3 x86_64, msan's getrlimit test fails to build >> for lack of prlimit(). SLES11.3 has glibc 2.11.3. Is there a minimum >> required glibc? I think this test implementation previously used >> getrlimit(), which is present on glibc2.11.3. >> >> >> On Fri, Aug 19, 2016 at 11:22 AM, Diana Picus via Release-testers >> <release-testers at lists.llvm.org> wrote: >>> >>> Hi, >>> >>> All good on AArch64 - we've uploaded the binaries. >>> >>> Regards, >>> Diana >>> >>> On 19 August 2016 at 04:51, Hans Wennborg via Release-testers >>> <release-testers at lists.llvm.org> wrote: >>> > 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 is only open for fixing critical problems >>> > (bad enough to warrant another test cycle) and release notes. >>> > >>> > Thanks, >>> > Hans >>> > _______________________________________________ >>> > Release-testers mailing list >>> > Release-testers at lists.llvm.org >>> > http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers >>> _______________________________________________ >>> Release-testers mailing list >>> Release-testers at lists.llvm.org >>> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers >> >> >> >> >> -- >> -Brian
Apparently Analagous Threads
- [Release-testers] [3.9 Release] Release Candidate 2 has been tagged
- [3.9 Release] Release Candidate 2 has been tagged
- [3.9 Release] Release Candidate 1 has been tagged
- [3.9 Release] Release Candidate 3 source and binaries available
- [Release-testers] [3.9 Release] Release Candidate 2 has been tagged