On 1/17/19 1:24 PM, Paul Gevers wrote: > Hi Olivier, > > On 17-01-2019 12:12, Olivier Sallou wrote: >> I tested in buster with updated libbarclay-java (2.1.0-3 pushed today to >> allow migration to testing) and could rebuild picard-tools from source >> (with tests) with no issue. >> >> >> I tried again with libbarclay-java 2.1.0-2 and faced no issue either. > The autopkgtest also fails in unstable. If you are only testing builds, > and not actually running autopkgtest, than it may be that you have a > build dependency that you miss during the tests, because you didn't add > it to the test dependencies.
I fixed picard-tools (git only) to fix the classpath in jar manifest and bin PicardCommandLine. running autopkgtest with test removes the ClassNotFound error, however it results in failure of 2 tests. I tested against a local build of the package though local build (which runs tests) works fine..... (both are run on the same machine)! autopkgtest does not keep the tempory directory used, so I cannot look at test report (testng) to find failing tests. The autopkgtest report is too verbose and I cannot find failing tests in this log file. I don't understand why some tests fail with autopkgtest and not with gbp buildpackage on the same server. > > Paul > > > _______________________________________________ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging -- Olivier Sallou Univ Rennes, Inria, CNRS, IRISA Irisa, Campus de Beaulieu F-35042 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
signature.asc
Description: OpenPGP digital signature
