[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Fwd: New bali-phy version

OK, I figured this out, now that I can debug the pbuilder fails. Thanks!

On 05/05/2018 08:13 PM, Andreas Tille wrote:
On Sat, May 05, 2018 at 04:41:59PM +0200, Andreas Tille wrote:
  FileNotFoundError: [Errno 2] No such file or directory: '/build/bali-phy-3.1+dfsg/tests/run-tests.py': '/build/bali-phy-3.1+dfsg/tests/run-tests.py'
No idea why this error message was printed.  What was really missing was
/usr/bin/python.  I've added this in my latest commit to the
Build-Depends.  Missing Build-Depends are usually causing issued between
a build on the local machine compared to pbuilder.
Yeah, that was a misleading error message from meson.  It was actually failing to find python to run the script.  I removed the Build-Depends on python 2, and added a quilt patch to change the interpreter to /usr/bin/python3.  I might change this upstream, if this also work on homebrew, although on homebrew it is not necessary since /usr/bin/python recently changed to point to python3

   So while this is
solved now I get a set of other errors:

28/28 bali-phy testsuite                      FAIL    63.29 s

OK:        27
FAIL:       1
SKIP:       0

The output from the failed tests:

28/28 bali-phy testsuite                      FAIL    63.29 s

--- command ---
/build/bali-phy-3.1.1+dfsg/tests/run-tests.py /build/bali-phy-3.1.1+dfsg/obj-x86_64-linux-gnu/src/bali-phy --package-path=/build/bali-phy-3.1.1+dfsg/obj-x86_64-linux-gnu/src/builtins:/build/bali-phy-3.1.1+dfsg
--- Listing only the last 100 lines from a long log. ---
Running test: parse/partitions/link/5  ... FAIL! ['error']
Running test: parse/partitions/link/7  ... FAIL! ['error']
Running test: parse/partitions/link/1  ... ok
Running test: parse/partitions/link/4  ... FAIL! ['error']
Running test: prob_prog/if-then-else/1  ... ok
Running test: IO/errors/Codons/2  ... FAIL! ['error']
Running test: IO/errors/Codons/stop/2  ... FAIL! ['error']
Running test: IO/errors/Codons/stop/1  ... FAIL! ['error']
Running test: IO/errors/Codons/AUTGC  ... FAIL! ['error']
Running test: IO/errors/Codons/3  ... FAIL! ['error']
Running test: IO/errors/Codons/1  ... FAIL! ['error']
Running test: IO/errors/Triplets/2  ... FAIL! ['error']
Running test: IO/errors/Triplets/AUTGC  ... FAIL! ['error']
Running test: IO/errors/Triplets/1  ... FAIL! ['error']
Running test: IO/errors/DNA-RNA/2  ... FAIL! ['error']
Running test: IO/errors/DNA-RNA/3  ... FAIL! ['error']
Running test: IO/errors/DNA-RNA/1  ... FAIL! ['error']
FAIL! (41 unexpected failures, 2 expected failures, 91 tests total)

Full log written to /build/bali-phy-3.1.1+dfsg/obj-x86_64-linux-gnu/meson-logs/testlog.txt
FAILED: meson-test
/usr/bin/python3 -u /usr/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.

If the build works on your local machine I'd recommend to seek for

    1. Further missing Build-Depends
    2. Attempts to access remote resources (which is not possible
       in pbuilder)
The extra error indirectly resulted from the fact that pbuilder runs the tests with HOME=/nonexistant.  This caused an extra error message.  I changed the test script to stop requiring that the error messages are EXACTLY x, but that instead the error messages contain all lines in x.

As a result, I can now build the package with gbp buildpackage @ pbuilder.  The repo on salsa should be up-to-date now.
Moreover I'd recommend to switch to Python3.
The test script works in both python2 and python3.  So the question is just whether /usr/bin/python3 is a usable name on other OSs where /usr/bin/python just works.  I suspect it is.

macosports wants /usr/bin/env python, since they don't want to run the python from /usr/bin, but that sounds like a security risk to me...

Hope this helps
Very much!


Reply to: