I'd recommend you start by opening an INFRA jira against Jenkins. The INFRA
folks are usually pretty quick to address.

Patrick

On Mon, Jul 25, 2016 at 10:26 AM, Flavio Junqueira <[email protected]> wrote:

> I've only logged on to the jenkins console, I've never tried to access the
> machine itself.
>
> -Flavio
>
> > On 25 Jul 2016, at 17:57, Michael Han <[email protected]> wrote:
> >
> > Actually the issue might not be transient, just noticed that although
> > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/ succeeds,
> the
> > log still said permission denied on invoking test-patch.sh. Not sure why
> > this build is green given other pre-commit build failed with same cause
> > (for example
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/).
> >
> > Does anyone have access to the build bot so we can investigate and fix
> > this, or Apache Infra team can take care of this?
> >
> > On Mon, Jul 25, 2016 at 9:49 AM, Michael Han <[email protected]> wrote:
> >
> >> The issue might be transient, as this pre-commit build works this
> morning:
> >> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3284/
> >>
> >> As a side note there are a couple of other failures while triage the
> build
> >> today, looks like these are infrastructure issues:
> >>
> >> https://builds.apache.org/job/ZooKeeper-trunk-solaris/1240/
> >> BUILD FAILED
> >> /zonestorage/hudson_solaris/home/hudson/hudson-slave/
> >> workspace/ZooKeeper-trunk-solaris/trunk/build.xml:324: Execute failed:
> >> java.io.IOException: Cannot run program "sh": error=12, Not enough space
> >>
> >> https://builds.apache.org/job/ZooKeeper-trunk/3005/
> >> mv: cannot stat 'build/*.tar.gz': No such file or directory
> >> mv: cannot stat 'build/*.jar': No such file or directory
> >> mv: cannot stat 'build/test/findbugs': No such file or directory
> >> mv: cannot stat 'build/docs/api': No such file or directory
> >>
> >> On Mon, Jul 25, 2016 at 7:55 AM, Rakesh Radhakrishnan <
> [email protected]>
> >> wrote:
> >>
> >>> Anybody has done changes to the build machine or test infrastructure?
> Is
> >>> this something simple issue, which can be resolved by giving
> permission to
> >>> those directories?
> >>>
> >>> +Rakesh
> >>>
> >>> On Sun, Jul 24, 2016 at 9:02 PM, Flavio Junqueira <[email protected]>
> wrote:
> >>>
> >>>> The console output says this:
> >>>>
> >>>> [exec]
> >>>>
> >>>
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
> >>>> line 558: /home/jenkins/tools/jiracli/latest/jira: Permission denied
> >>>>     [exec]
> >>>>
> >>>
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/src/java/test/bin/test-patch.sh:
> >>>> line 559: /home/jenkins/tools/jiracli/latest/jira: Permission denied
> >>>>
> >>>> I'm not sure whether this is transient or anyone has changed the
> config.
> >>>>
> >>>> -Flavio
> >>>>
> >>>>> On 24 Jul 2016, at 16:12, Rakesh Radhakrishnan <[email protected]>
> >>>> wrote:
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> It looks like "Precommit build" is triggered but failed to add
> >>> comments
> >>>> to
> >>>>> Jira. Appreciate your help. Thanks!
> >>>>>
> >>>>> References:-
> >>>>> ZOOKEEPER-2479 ->
> >>>>> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3283/
> >>>>> ZOOKEEPER-2172 ->
> >>>>> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3282/
> >>>>>
> >>>>>
> ======================================================================
> >>>>>
> >>>>>    [exec]     Adding comment to Jira.
> >>>>>    [exec]
> >>>> ======================================================================
> >>>>>    [exec]
> >>>> ======================================================================
> >>>>>    [exec]
> >>>>>    [exec]
> >>>>>    [exec]
> >>>>>    [exec]
> >>>>>    [exec]
> >>>> ======================================================================
> >>>>>    [exec]
> >>>> ======================================================================
> >>>>>    [exec]     Finished build.
> >>>>>    [exec]
> >>>> ======================================================================
> >>>>>
> >>>>>
> >>>>> Thanks,
> >>>>> Rakesh
> >>>>
> >>>>
> >>>
> >>
> >>
> >>
> >> --
> >> Cheers
> >> Michael.
> >>
> >
> >
> >
> > --
> > Cheers
> > Michael.
>
>

Reply via email to