On Fri, May 18, 2018 at 08:40:56PM +0200, Adam Borowski wrote:
> If no random problem happens, the build still fails with:
> 
> .----
> ##################################################
>  Monkeysphere basic tests completed successfully!
> ##################################################
> ### removing temp dir...
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_test: make -j2 -Oline test returned exit code 2
> debian/rules:6: recipe for target 'build' failed
> make: *** [build] Error 25
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
> `----
> 
> To exclude a peculiarity of my test setup (btrfs, new non-Debian kernel,
> etc), official buildds of second-class archs that tried monkeysphere
> recently concur.
> 
> Build logs of two types (failed and passed testsuite) attached.

For thre record, the above failed testsuite log fails on:

2018/05/18 14:25:50 socat[27609] E connect(5, AF=1 
"/<<PKGBUILDDIR>>/tests/tmp/ms.cco/ssh-socket", 74): Connection refused
ssh_exchange_identification: Connection closed by remote host

./tests/basic: line 81: kill: (27487) - No such process
##### ssh connection test FAILED. returned: 255, expected: 0
FAILED!
### removing temp dir...

That is strange in itself, but the "passed" one is much stranger, as
mentioned.

On Mon, Jun 18, 2018 at 07:56:10PM +0200, Adam Borowski wrote:
[...] 
> So does reproducible:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/monkeysphere.html
> (fails on all 4 tested: amd64 i386 armhf arm64)

That, however, seems to be a different problem, at least now. The amd64
failed with:

ms: importing key from file 
'/build/1st/monkeysphere-0.41/tests/tmp/ms.9XY/ssh_host_rsa_key'...
RSA.xs:198: OpenSSL error: no start line at 
/build/1st/monkeysphere-0.41/tests/../src/pem2openpgp line 1104, <STDIN> line 1.
gpg: no valid OpenPGP data found.
FAILED!

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/monkeysphere_0.41-1.rbuild.log.gz

I wonder if that shouldn't be treated separately: I suspect this is
related to the recent changes in OpenSSH's key storage format.

So I'd propose we keep this bug for "kilobyte's weird heisenbug FTBFS"
and open a separate issue for the RSA key parser.. :/

A.

Attachment: signature.asc
Description: PGP signature

Reply via email to