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

Bug#992654: glibc breaks ruby-rugged autopkgtest: RemoteNetworkTest#test_remote_check_connection_push_credentials



Control: reassign -1 ruby-rugged 1.1.0+ds-4
Control: retitle -1 ruby-rugged autopkgtest regressed in Augustus 2021
Control: tag -1 - unreproducible

On 22-08-2021 00:32, Aurelien Jarno wrote:
>> With a recent upload of glibc the autopkgtest of ruby-rugged fails in
>> testing when that autopkgtest is run with the binary packages of glibc
>> from unstable. It passes when run with only packages from testing. In
>> tabular form:
>>
>>                        pass            fail
>> glibc                  from testing    2.31-16
>> ruby-rugged            from testing    1.1.0+ds-4
>> versioned deps [0]     from testing    from unstable
>> all others             from testing    from testing
> 
> Unfortunately I have not been able to reproduce this behaviour.
> 
> In my testing, the autopktest failure happens already happen in pure
> testing (i.e. glibc 2.31-13), and it also appears with testing + glibc
> 2.31-16. I therefore don't believe glibc has anything to do with this
> failure.

The migration-reference/0 result on arm64 agrees with you, hence
reassigning to ruby-rugged alone.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: