FreeBSD_HEAD_amd64_gcc - Build #1144 - Failure

[Baptiste Daroussin]

On Mon, Apr 04, 2016 at 08:38:03PM +0800, Li-Wen Hsu wrote:
> On Mon, Apr 04, 2016 at 14:32:35 +0200, Baptiste Daroussin wrote:
> > On Mon, Apr 04, 2016 at 08:25:39PM +0800, Li-Wen Hsu wrote:
> > > On Mon, Apr 04, 2016 at 12:53:16 +0200, Baptiste Daroussin wrote:
> > > > On Mon, Apr 04, 2016 at 06:39:00PM +0800, Li-Wen Hsu wrote:
> > > > > 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.
> > > > 
> > > > Return 70 means an error occured. if I look at the log I can see that
> > > > powerpc64-gcc is not installed for sure, hence the error 70
> > > > 
> > > > What is strange it that no "error message is shown"
> > > 
> > > Very strange, no further error message is shown, even -d provided.
> > > 
> > > root at jenkins10a:~ # pkg -d install -y devel/amd64-xtoolchain-gcc
> > > DBG(1)[44393]> pkg initialized
> > > Updating FreeBSD repository catalogue...
> > > DBG(1)[44393]> PkgRepo: verifying update for FreeBSD
> > > DBG(1)[44393]> Pkgrepo, begin update of '/var/db/pkg/repo-FreeBSD.sqlite'
> > > DBG(1)[44393]> Fetch: fetching from: http://pkgmir.pkg.freebsd.org/FreeBSD:10:amd64/latest/meta.txz with opts "i"
> > > DBG(1)[44393]> Fetch: fetching from: http://pkgmir.pkg.freebsd.org/FreeBSD:10:amd64/latest/packagesite.txz with opts "i"
> > > FreeBSD repository is up-to-date.
> > > All repositories are up-to-date.
> > > DBG(1)[44393]> want to get an advisory lock on a database
> > > DBG(1)[44393]> release an advisory lock on a database
> > > root at jenkins10a:~ # echo $?
> > > 70
> > > 
> > > Is there anything I can help on debugging this?
> > > 
> > pkg info amd64-xtoolchain-gcc please
> 
> root at jenkins10a:~ # pkg -d info amd64-xtoolchain-gcc
> DBG(1)[44644]> pkg initialized
> amd64-xtoolchain-gcc-0.1
> Name           : amd64-xtoolchain-gcc
> Version        : 0.1
> Installed on   : Tue Mar  3 07:32:25 2015 UTC
> Origin         : devel/amd64-xtoolchain-gcc
> Architecture   : freebsd:10:x86:64
> Prefix         : /usr/local
> Categories     : devel
> Licenses       :
> Maintainer     : bapt at FreeBSD.org
> WWW            : UNKNOWN
> Comment        : Pre seeded toolchain to cross build FreeBSD base
> Annotations    :
>         repo_type      : binary
>         repository     : FreeBSD
> Flat size      : 225B
> Description    :
> Pre seeded cross toolchain definition to cross build FreeBSD base
> 

Ok I see the issue, I will fix it thanks.

Bapt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20160404/c2b6dd9d/attachment.sig>