Glad to be of help! On Tue, Mar 21, 2017 at 11:33 AM, Elliot Saba <[email protected]> wrote:
> Thanks Bill, you nailed it. I changed my configuration > <https://github.com/staticfloat/julia-buildbot/commit/7d9db75321d234a40ca4446960fcd02d59c8fe2b> > to no longer collapse these changes, and now it's working great. > -E > > On Wed, Mar 8, 2017 at 3:29 PM, Bill Deegan <[email protected]> > wrote: > >> Did you look at: >> https://docs.buildbot.net/current/manual/cfg-builders.html# >> collapsing-build-requests >> >> >> On Wed, Mar 8, 2017 at 6:24 PM, Elliot Saba <[email protected]> >> wrote: >> >>> Bump. Does anyone have any idea why this would be happening? If you >>> need more information to diagnose this problem, I would be happy to provide >>> it. >>> -E >>> >>> On Sun, Feb 26, 2017 at 3:40 PM, Elliot Saba <[email protected]> >>> wrote: >>> >>>> Hello again, >>>> >>>> I have two schedulers defined to package my binaries. The first, is an >>>> AnyBranchScheduler >>>> <https://github.com/staticfloat/julia-buildbot/blob/8c7859d3136c10f3236e4e11cbd408d773123029/master/package.py#L319-L328> >>>> that >>>> has a treeStableTimer defined. The second, defined right below, is a >>>> ForceScheduler >>>> <https://github.com/staticfloat/julia-buildbot/blob/8c7859d3136c10f3236e4e11cbd408d773123029/master/package.py#L339-L356> >>>> . >>>> >>>> I am working on creating some tooling that allows us to force-schedule >>>> builds easily from the GitHub interface, and I discovered that if I >>>> force-schedule two builds, the first flips to results code 3, e.g. it is >>>> SKIPPED >>>> <http://docs.buildbot.net/latest/developer/results.html#buildbot.process.results.SKIPPED> >>>> . >>>> >>>> This is the exact behavior that I would expect if the ForceScheduler >>>> had a treeStableTimer applied to it, however, it does not, it's the >>>> AnyBranchScheduler that has one. >>>> >>>> It seems to me like the AnyBranchScheduler's `treeStableTimer` is >>>> messing with the builds from my ForceScheduler. I may be conflating two >>>> entirely unrelated things, but if so, I'd appreciate any help in tracking >>>> this down. I definitely want a tree stable timer on the >>>> AnyBranchScheduler, because otherwise merge commits can easily rack up days >>>> worth of CI time, as each build takes about an hour to complete, however I >>>> can't lose force scheduled builds willy-nilly. >>>> >>>> Thanks, >>>> -E >>>> >>> >>> >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> https://lists.buildbot.net/mailman/listinfo/users >>> >> >> >
_______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
