From owner-freebsd-current@freebsd.org Mon Apr 4 10:39:02 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D178B02A33 for ; Mon, 4 Apr 2016 10:39:02 +0000 (UTC) (envelope-from lwhsu@FreeBSD.cs.nctu.edu.tw) Received: from FreeBSD.cs.nctu.edu.tw (freebsd2.cs.nctu.edu.tw [140.113.17.206]) by mx1.freebsd.org (Postfix) with ESMTP id 281B71157; Mon, 4 Apr 2016 10:39:01 +0000 (UTC) (envelope-from lwhsu@FreeBSD.cs.nctu.edu.tw) Received: by FreeBSD.cs.nctu.edu.tw (Postfix, from userid 1058) id 20D262E5B; Mon, 4 Apr 2016 18:39:00 +0800 (CST) Date: Mon, 4 Apr 2016 18:39:00 +0800 From: Li-Wen Hsu To: Baptiste Daroussin Cc: Dimitry Andric , Andriy Gapon , freebsd-current@freebsd.org Subject: Re: FreeBSD_HEAD_amd64_gcc - Build #1144 - Failure Message-ID: <20160404103859.GA27648@FreeBSD.cs.nctu.edu.tw> References: <2034599654.182.1459676383628.JavaMail.jenkins@jenkins-9.freebsd.org> <57015089.4010700@FreeBSD.org> <19A774FF-773C-4F29-8DF1-E72BBED81DA9@FreeBSD.org> <20160403225014.GH5214@ivaldir.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qDbXVdCdHGoSgWSk" Content-Disposition: inline In-Reply-To: <20160403225014.GH5214@ivaldir.etoilebsd.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 10:39:02 -0000 --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. > >=20 > > For pkg 1.6.4_1, it returns 0, but 1.7.1 returns 70, thus jenkins > > consider the build script execution failure. > >=20 > >=20 > 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 --=20 Li-Wen Hsu https://lwhsu.org --qDbXVdCdHGoSgWSk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQJ8BAEBCgBmBQJXAkRCXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMDdENTNGNjUyMTUzMzVCNzA5NDNGODQ2 NzI3RTc3Qzg4NjJCNjU2AAoJEGcn53yIYrZWk/EP/AjfamxifqeCB+dnVkRSh1La sBVYHP2rFvoBofPsLOw4WsrxfvCV44xf151Fmr7vzVl/B1rn9viidmStARSbZ9M7 cUaNvIZn9C295t0kTtVGQJ9hBKDzifcbzQ7jF4WZ8lnqwkFmxOov/BefBXFci2Ui bXzrFv3KGY+24e+ywbw8hmDSfnVIhv40r7VPp6pQ6Bii5JhnwzDQPZ2ewqfpiWGJ g5GSXyFhI9TBmeUWFtZRyyqkOuuUmGFsoR1LT+f4yulwGSqrwalsiQtnhDPTHYac MmszOdi6sjpvURNt3xfyf8Ifzl9Rf0uoG94GOxP89QpS4RD3O8UXCUpRpdMbPw86 Xkpghq7tY+G2Y4I40bB+Wsg6sc0bOXSVl1FuF0A5NssvnW5fmPXPn0gH5HQmU8C+ 7Si/Bn9oXsEwgi65pETay5sZU5037XyMlFfVGzTTkNe6O/FY7Mo9j4YtHTVwphR4 42Zta9BW2GDZxp5oglX5nJzq7IlUyVhSPr+MHaZpp4y/Og/8eJ+fU5DEnJUgn7FU Q9bVE9z8NZ8ZuX03LSo7yZHJ6ifyl2H648/nJztI/l4TVc/fszswWFo2wWLquvXw kvf1kNrUu1J+6BuaQOOkgqH+Qc5Qwms0I2p8Laus3KuEntT4c2SvxG2O6HbNJ5J8 DVaw0WmU8qwf60uH7bNy =LlpN -----END PGP SIGNATURE----- --qDbXVdCdHGoSgWSk--