Re: FreeBSD_HEAD_amd64_gcc - Build #1144 - Failure

On Mon, Apr 04, 2016 at 04:41:47AM +0800, Li-Wen Hsu wrote:
> On Mon, Apr 4, 2016 at 1:59 AM, Dimitry Andric <dim_at_freebsd.org> wrote:
> > On 03 Apr 2016, at 19:19, Andriy Gapon <avg_at_FreeBSD.org> wrote:
> >> On 03/04/2016 12:39, jenkins-admin_at_FreeBSD.org wrote:
> >>> FreeBSD_HEAD_amd64_gcc - Build #1144 - Failure:
> >>>
> >>> Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1144/
> >>> Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1144/changes
> >>> Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1144/console
> >>>
> >>
> >> I wasn't able to understand what was the failure here...
> >
> > The step to install the amd64-xtoolchain-gcc package failed, apparently because it decided to auto-upgrade pkg first, without actually installing the package that was asked for:
> >
> > + sudo pkg install -y devel/amd64-xtoolchain-gcc
> > Updating FreeBSD repository catalogue...
> > Fetching meta.txz: . done
> > Fetching packagesite.txz: .......... done
> > Processing entries: .......... done
> > FreeBSD repository update completed. 25093 packages processed.
> > New version of pkg detected; it needs to be installed first.
> > The following 1 package(s) will be affected (of 0 checked):
> >
> > Installed packages to be UPGRADED:
> >         pkg: 1.6.4_1 -> 1.7.1
> >
> > The process will require 84 KiB more space.
> > 2 MiB to be downloaded.
> > Fetching pkg-1.7.1.txz: .......... done
> > Checking integrity... done (0 conflicting)
> > [1/1] Upgrading pkg from 1.6.4_1 to 1.7.1...
> > [1/1] Extracting pkg-1.7.1: .......... done
> > Updating FreeBSD repository catalogue...
> > Repo "FreeBSD" upgrade schema 2012 to 2013: Add vital field
> > FreeBSD repository is up-to-date.
> > All repositories are up-to-date.
> > Build step 'Execute shell' marked build as failure
> >
> > I'd consider this a bug in pkg?  Is it suppose to return a failure code in this case?
> 
> I've checked this a little more, I found the return code of
> "installing a installed package" has been changed.
> 
> For pkg 1.6.4_1, it returns 0, but 1.7.1 returns 70, thus jenkins
> consider the build script execution failure.
> 
> 
It shoudl not return 70 if it returns 70 then there is a bug I can fix, I need
to know more about what is failing to be able to fix

Best regards,
Bapt