You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Nathan Hartman <ha...@gmail.com> on 2020/02/27 17:17:41 UTC
Re: buildbot failure in on svn-backport-conflicts-1.13.x
On Thu, Feb 27, 2020 at 12:01 PM <bu...@apache.org> wrote:
> The Buildbot has detected a new failure on builder
> svn-backport-conflicts-1.13.x while building . Full details are available
> at:
>
> https://ci.apache.org/builders/svn-backport-conflicts-1.13.x/builds/3916
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: bb_qnode6_ubuntu
>
> Build Reason: The Nightly scheduler named
> 'subversion-1.13.x-backport-conflicts' triggered this build
> Build Source Stamp: [branch subversion/branches/1.13.x] HEAD
> Blamelist:
>
> BUILD FAILED: failed Conflicts
Another timeout.
Re: buildbot failure in on svn-backport-conflicts-1.13.x
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Nathan Hartman wrote on Thu, 27 Feb 2020 17:52 +00:00:
> On Thu, Feb 27, 2020 at 12:26 PM Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> > > > Build Reason: The Nightly scheduler named 'subversion-1.13.x-backport-conflicts' triggered this build
> > > > Build Source Stamp: [branch subversion/branches/1.13.x] HEAD
> > > > Blamelist:
> > > >
> > > > BUILD FAILED: failed Conflicts
> > >
> > > Another timeout.
> >
> > If Infra can't fix the root cause, we might be able to work around this
> > by changing the build configuration. Currently it runs hourly; we could
> > change it to run only after commits to the relevant branches.
> >
> > I assume we had a good reason for coding that job to run hourly, back
> > when we first added it, but we can revisit that decision.
>
> This wouldn't fix the timeout problem, but it may save on resources to
> run a test hourly only if a commit has been made since the last test
> run. This way, tests will run soon after commits. The potential
> downside is that any breakage of the test host might not be detected
> for a long time. So, maybe we'd want, at minimum, 1 test run every 24
> hours, whether commits were made or not?
+1
> Regarding the timeout issue, I'll ask Infra (very nicely) to look at it...
Thanks!
Cheers,
Daniel
Re: buildbot failure in on svn-backport-conflicts-1.13.x
Posted by Nathan Hartman <ha...@gmail.com>.
On Thu, Feb 27, 2020 at 12:26 PM Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> > > Build Reason: The Nightly scheduler named 'subversion-1.13.x-backport-conflicts' triggered this build
> > > Build Source Stamp: [branch subversion/branches/1.13.x] HEAD
> > > Blamelist:
> > >
> > > BUILD FAILED: failed Conflicts
> >
> > Another timeout.
>
> If Infra can't fix the root cause, we might be able to work around this
> by changing the build configuration. Currently it runs hourly; we could
> change it to run only after commits to the relevant branches.
>
> I assume we had a good reason for coding that job to run hourly, back
> when we first added it, but we can revisit that decision.
This wouldn't fix the timeout problem, but it may save on resources to
run a test hourly only if a commit has been made since the last test
run. This way, tests will run soon after commits. The potential
downside is that any breakage of the test host might not be detected
for a long time. So, maybe we'd want, at minimum, 1 test run every 24
hours, whether commits were made or not?
Regarding the timeout issue, I'll ask Infra (very nicely) to look at it...
Nathan
Re: buildbot failure in on svn-backport-conflicts-1.13.x
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Nathan Hartman wrote on Thu, 27 Feb 2020 17:17 +00:00:
> On Thu, Feb 27, 2020 at 12:01 PM <bu...@apache.org> wrote:
> > The Buildbot has detected a new failure on builder svn-backport-conflicts-1.13.x while building . Full details are available at:
> > https://ci.apache.org/builders/svn-backport-conflicts-1.13.x/builds/3916
> >
> > Buildbot URL: https://ci.apache.org/
> >
> > Buildslave for this Build: bb_qnode6_ubuntu
> >
> > Build Reason: The Nightly scheduler named 'subversion-1.13.x-backport-conflicts' triggered this build
> > Build Source Stamp: [branch subversion/branches/1.13.x] HEAD
> > Blamelist:
> >
> > BUILD FAILED: failed Conflicts
>
> Another timeout.
If Infra can't fix the root cause, we might be able to work around this
by changing the build configuration. Currently it runs hourly; we could
change it to run only after commits to the relevant branches.
I assume we had a good reason for coding that job to run hourly, back
when we first added it, but we can revisit that decision.
Cheers,
Daniel