Bug#860554: autopkgtest: Running autopkgtest may fail due to long path

[Antonio Terceiro]

On Tue, Apr 18, 2017 at 03:50:15PM +0200, Balint Reczey wrote:
> Package: autopkgtest
> Version: 4.3
> 
> Dear Maintainers,
> 
> Running autopkgtest testsuite of libdbd-mysql-perl fails on s390x due
> to the long socket filename:
> 
> ( From https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1680577 )
> ...
> 2017-03-29T08:40:18.627231Z 0 [Warning] Failed to set up SSL because
> of the following SSL library error: SSL context is not usable without
> certificate and private key
> 2017-03-29T08:40:18.627257Z 0 [ERROR] The socket file path is too long
> (> 107): /data/adttmp/autopkgtest-virt-lxc.shared.y4ui3net/downtmp/build.R3s/libdbd-mysql-perl-4.041/t/testdb/mysql.sock
> 2017-03-29T08:40:18.627267Z 0 [ERROR] Aborting
> 
> 2017-03-29T08:40:18.627278Z 0 [Note] Binlog end
> 2017-03-29T08:40:18.627315Z 0 [Note] Shutting down plugin 'ngram'
> 2017-03-29T08:40:18.627328Z 0 [Note] Shutting down plugin 'partition'
> 2017-03-29T08:40:18.627337Z 0 [Note] Shutting down plugin 'BLACKHOLE'
> ...
> 
> A few characters could be cut in the package's test itself, but the
> same problem may affect many other packages and fixing the issue in
> autopkgtest seems bring more benefits.
> 
> The system configuration addst the beginning of the path, but it is
> not very long compared to the standard "/tmp":
> "/data/adttmp/"
> 
> The test itself generates the following path inside the source
> directory which is not a huge portion of the path either:
> "t/testdb/mysql.sock"
> 
> Autopkgtest generates the longest part:
> "autopkgtest-virt-lxc.shared.y4ui3net/downtmp/build.R3s/libdbd-mysql-perl-4.041"
> 
> I proposed a patch which cuts a few characters from the prefix by
> abbreviating "autopkgtest-virt-lxc.shared.", but the source directory
> for the package could also be just "src" instead of the full package
> name with version especially since this can be much longer than in the
> current case.
> 
> Before preparing an updated patch I wanted to ask for your opinion
> regarding the path to be taken ( :-) ).

I am not an autopkgtest maintainer, but I think we could maybe have the
source tree in a very short path right on top of /, like /src, or
/autopkgtest/src ... however I am not sure how that would impact the
current codebase.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/autopkgtest-devel/attachments/20170427/d277c408/attachment.sig>