From owner-freebsd-current@freebsd.org Tue Nov 17 20:03:05 2015 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 75EFBA3192F for ; Tue, 17 Nov 2015 20:03:05 +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 603C31BF0; Tue, 17 Nov 2015 20:03:03 +0000 (UTC) (envelope-from lwhsu@FreeBSD.cs.nctu.edu.tw) Received: by FreeBSD.cs.nctu.edu.tw (Postfix, from userid 1058) id 8E6EC220F; Wed, 18 Nov 2015 04:00:55 +0800 (CST) Date: Wed, 18 Nov 2015 04:00:55 +0800 From: Li-Wen Hsu To: Baptiste Daroussin Cc: jenkins-admin@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: FreeBSD_HEAD-tests - Build #1704 - Still Unstable Message-ID: <20151117200055.GA55478@FreeBSD.cs.nctu.edu.tw> References: <1510276266.43.1447770841201.JavaMail.jenkins@jenkins-9.freebsd.org> <512656898.45.1447781806402.JavaMail.jenkins@jenkins-9.freebsd.org> <20151117193427.GA76612@ivaldir.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline In-Reply-To: <20151117193427.GA76612@ivaldir.etoilebsd.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Tue, 17 Nov 2015 20:03:05 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 17, 2015 at 20:34:29 +0100, Baptiste Daroussin wrote: > On Tue, Nov 17, 2015 at 05:36:45PM +0000, jenkins-admin@FreeBSD.org wrote: > > FreeBSD_HEAD-tests - Build #1704 - Still Unstable: > >=20 > > Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1= 704/ > > Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/170= 4/changes > > Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1704= /console > >=20 > > Change summaries: > >=20 > > No changes > >=20 > >=20 > > The failed test cases: > >=20 > > 1 tests failed. > > FAILED: test-report.xml. > >=20 > > Error Message: > >=20 > Can someone fix that? or at least show which test is giving unicode in the > output? Just did a quick look into this: https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1704/testReport/test-rep= ort/xml/_init_/ """ org.dom4j.DocumentException: Error on line 52159 of document file:///builds= /FreeBSD_HEAD-tests/test-report.xml : An invalid XML character (Unicode: 0x= 1) was found in the element content of the document. Nested exception: An i= nvalid XML character (Unicode: 0x1) was found in the element content of the= document. """ And this is the case output contains invalid XML character: """ Test case metadata ------------------ allowed_architectures is empty allowed_platforms is empty description =3D crypt(3) salt consistency checks has_cleanup =3D false required_configs is empty required_disk_space =3D 0 required_files is empty required_memory =3D 0 required_programs is empty required_user is empty timeout =3D 300 Original stderr --------------- *** Expected check failure: Old-style/bad inputs fail on FreeBSD: /builds/F= reeBSD_HEAD/contrib/netbsd-tests/lib/libcrypt/t_crypt.c:140: Test 22 ^A^BUZ= oIyj/Hy/c !=3D ^A^Bwyd0KZo65Jo *** Expected check failure: Old-style/bad inputs fail on FreeBSD: /builds/F= reeBSD_HEAD/contrib/netbsd-tests/lib/libcrypt/t_crypt.c:140: Test 23 a_Av8a= wQ0AsR6 !=3D a_C10Dk/ExaG. *** Expected check failure: Old-style/bad inputs fail on FreeBSD: /builds/F= reeBSD_HEAD/contrib/netbsd-tests/lib/libcrypt/t_crypt.c:140: Test 24 ~=E2= =96=92UZoIyj/Hy/c !=3D ~=E2=96=92.5OTsRVjwLo """ There is an issue and a PR for kyua for this: https://github.com/jmmv/kyua/issues/136 https://github.com/jmmv/kyua/pull/148 Escape these characters is a way, or we might make our test cases always produce printable characters in outputs, however that might be impossible (who knows when test fails would happen?). Or, don't know if there is a method to embedded these bytes into a valid XML. Li-Wen --=20 Li-Wen Hsu http://lwhsu.org --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQJ8BAEBCgBmBQJWS4d2XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMDdENTNGNjUyMTUzMzVCNzA5NDNGODQ2 NzI3RTc3Qzg4NjJCNjU2AAoJEGcn53yIYrZWOmQP/igRzks4RgM7fVsEDztBdlub EBrLHUsNqmpv/vCs2CyJGB9vYwofXM2Hrqe2r4AU3/yoNtvbWQ3zueruu0ukUvIf Mz9WurzADxLAV05hl5I1xHl0tkKz7nHWKwymk0nMXP8tmh8bASD+H/9VtBmKhWjg aTnigHBGsbED09uKdtgerbhXygxijq4b3UBlxAJWEEFoMJCSlGv3LRS04qojcIBn k3PmSjJQgFqXBmUHHNumdG+QJ0Gn5FP/f874fdXWRhhQLGc4d22qdZ6bQa28k/CS pEiSxZrKKKAZGOaGLCksltmjma1fofu8USAUOs/vzcchueBiEn8Y9r9OWE0dabhp 0hSguQ8Ne0rkiikWiU03I3XuyHNuAdSRq+UQZLcilQa4hu11cN0k3mN1AWlzmQQ+ 6SHWgTJ6T7I4Xy7fBrpYaE6OutbkFUQbdzXGnBF+0i1Ez21cyzPihgc22PNEc3zW Uq3ks0bw7bSdydblZD2tmyhLjmwnusSoSAu4HXX/xsNfDPGmUAhsd/v98IQXHv1w A9kxX+RMAeZ1aaZ9RE10Q51wQDnm26q7/Q3gHe9xO5Ozj68kd76b2JN8hBQmDLr0 hzOQuPTW/8koNX001SE6tlS6BtQ7QqRdk27/O/NSOUr9SMhHz8E/ijaiELl0EVf1 CLHuoTU5NHOLxXDI1lw3 =WPYx -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/--