search for: builbots

...ominator. What you seem to want is just the opposite, so short story > is that it's bad planning to build to such a new version of glibc. > You're not going to get around this, it just won't work. > > > Peter Copy that. I do realize the sane thing to do is to have the builbots -- smoketest environments -- match the production environment, which currently is spec'd at CentOS 5.x. Unfortunately, I don't have direct control over some of this. <sigh> -- -------------------------------------------- MzK "God helps those who help themselves."...

On 08/25/2016 10:44 AM, Gordon Messmer wrote: > On 08/25/2016 09:49 AM, Kay Schenk wrote: >> I do realize the sane thing to do is to have the builbots -- >> smoketest environments -- match the production environment > > > I think the sane thing to do would be to use buildbots that support LSB: > > http://www.ludism.org/~rwhe/LSB/tutorial/tut.html Great resource! Thanks... -- --------------------------------------------...

I'm trying to understand why the buildbot sanitizer-ppc64-linux1 fails due to my latest patch. It was in llvm::GlobalValue while the reported failure is: strcspn-2.c.tmp: /home/buildbots/sanitizerslave1/sanitizer-ppc64-1/build/llvm/projects/compiler-rt/test/asan/TestCases/strcspn-2.c:17: int main(int, char **): Assertion `r == sizeof(s1) - 1' failed. where strcspn-2.c (below) tests the

I am seeing a couple of new test failures with gcc 6.1.0 on aarch64 in Release mode. Debug mode works. They work with gcc 8.2.0 in Release mode. What compiler(s) do the Builbot builders use? Presumably if we use the same compiler(s) we should see the same testing result. I'm trying to isolate the problem and it would be good to run a sanity check to get a baseline. I looked through zorg

On 08/26/2015 09:46 AM, Philip Reames wrote: > On 08/26/2015 09:41 AM, David Blaikie via llvm-dev wrote: >> >> >> On Wed, Aug 26, 2015 at 9:41 AM, Renato Golin >> <renato.golin at linaro.org <mailto:renato.golin at linaro.org>> wrote: >> >> On 26 August 2015 at 17:39, David Blaikie <dblaikie at gmail.com >> <mailto:dblaikie at

On 08/25/2016 09:49 AM, Kay Schenk wrote: > I do realize the sane thing to do is to have the builbots -- > smoketest environments -- match the production environment I think the sane thing to do would be to use buildbots that support LSB: http://www.ludism.org/~rwhe/LSB/tutorial/tut.html

On 26/08/16 06:18, Kay Schenk wrote: >> On 08/25/2016 09:49 AM, Kay Schenk wrote: >>> I do realize the sane thing to do is to have the builbots -- >>> smoketest environments -- match the production environment >> >> >> I think the sane thing to do would be to use buildbots that support LSB: >> >> http://www.ludism.org/~rwhe/LSB/tutorial/tut.html > > Great resource! Thanks... mock is available...

On 08/25/2016 06:26 PM, Peter wrote: > On 26/08/16 06:18, Kay Schenk wrote: >>> On 08/25/2016 09:49 AM, Kay Schenk wrote: >>>> I do realize the sane thing to do is to have the builbots -- >>>> smoketest environments -- match the production environment >>> >>> >>> I think the sane thing to do would be to use buildbots that support LSB: >>> >>> http://www.ludism.org/~rwhe/LSB/tutorial/tut.html >> >> Great resource...

On Aug 24, 2016 5:05 PM, "Gordon Messmer" <gordon.messmer at gmail.com> wrote: > > On 08/24/2016 04:22 PM, Kay Schenk wrote: >> >> Due to a proposed changeover to build machines for a project I'm >> involved with, I need at least glib 2.19. > > > Do you know why? As in, what features or fixes are required? If not, I think John's question

...ged by breakages that occur over long periods of time. Here's an attempt to explain why I fly off the handle at these. Before we had buildbots, a random patch would break the system. It would sometimes take a whole day to determine which patch broke it. I came up with the idea of using builbots. We started using them internally at Apple (unfortunately, those machines are still unavailable to non-Apple employees). It quickly spread so that some were set up at Google. It was a huge win for us. However, it's only a huge win if people pay attention to the error reports. People di...