FreeBSD_HEAD_amd64_gcc - Build #1144 - Failure
Li-Wen Hsu
lwhsu at FreeBSD.org
Mon Apr 4 10:39:02 UTC 2016
On Mon, Apr 04, 2016 at 00:50:14 +0200, Baptiste Daroussin wrote:
> On Mon, Apr 04, 2016 at 04:41:47AM +0800, Li-Wen Hsu wrote:
> > 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
What else information do you need? My experiment is as following:
On a machine uses quarterly branch, where pkg is 1.6.4_1, install a
installed package. I choose rsync here, then echo $?, it returns 0.
And I switch to latest branch, also use `pkg install -y rsync`, but this
time $? is 70.
Jenkins "Execute shell" build step checks return value of each command
in the shell script, if it is non-zero, it aborts the build and
considers if failure.
Regards,
Li-Wen
--
Li-Wen Hsu <lwhsu at FreeBSD.org>
https://lwhsu.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 949 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20160404/7bdecf4e/attachment.sig>
More information about the freebsd-current
mailing list