Wednesday, 26 February 2014

Re: Analysis of current ppc64el test failures

On 26/02/2014, Martin Pitt <[email protected]> wrote:
>
> I categorized the current failures for packages which don't fail on x86.

Thanks for doing this!

> Tests run, but some failures
> ----------------------------
...
> bzr

Two issues:

File ".../bzrlib/tests/__init__.py", line 2862, in makeAndChdirToTestDir
os.mkdir(self.test_base_dir)
OSError: [Errno 36] File name too long:
'/tmp/adt-downtmp/...<reallylongfilename>...'

Does the container have a 256 char limit on paths or something? What
does a script along the lines of the following return:

import tempfile
import os

fd = os.open(tempfile.gettempdir(), 0)
try:
maxlen = os.fpathconf(fd, "PC_PATH_MAX")
finally:
os.close(fd)
print "Max path length", maxlen

The second issue seems to be a lack of default certs inside the
container, does /etc/ssl/certs/ca-certificates.crt exist? Would be
need to add some package as a test dep to insure it does?

> Tests that fail due to packages not (yet) existing for ppc64el
> --------------------------------------------------------------
...
> juju-core

I don't understand the output here, the latest log seems to fail on
the initial setup before getting to juju:

Errors were encountered while processing:
/var/cache/apt/archives/python3.3-minimal_3.3.5~rc1-1_ppc64el.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
adt-run: unexpected error: testbed setup commands failed with status 100

However I guess if mongodb isn't working, juju-core is stuck for now anyway.

Martin

--
ubuntu-devel mailing list
[email protected]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel