On Tue, 18 May 2021 at 05:38:29 +, Mike Gabriel wrote:
> I have Cc: Adrian Bunk as he had some good ideas in the past on such issues.
> Adrian, do you mind taking a look? Any hint how to track this issue down?
Adrian asked me on IRC and was concerned about whether
Hi Paul,
On Di 18 Mai 2021 20:49:55 CEST, Paul Gevers wrote:
Hi Mike,
On 18-05-2021 07:38, Mike Gabriel wrote:
Would it be a viable solution for now to not run autopkgtests on
ppcel64? I really don't have a clue why this issue comes up only on
ppcel64.
If you think this failure is not
Hi Mike,
On 18-05-2021 07:38, Mike Gabriel wrote:
> Would it be a viable solution for now to not run autopkgtests on
> ppcel64? I really don't have a clue why this issue comes up only on
> ppcel64.
If you think this failure is not representative for the package behavior
on ppc64el, it is.
Hi Paul,
On Mo 17 Mai 2021 20:56:52 CEST, Paul Gevers wrote:
Control: reopen -1
Hi Mike,
On 17-05-2021 12:57, Mike Gabriel wrote:
Can you do your autopkgtest magic with upcoming dbus-test-runner
16.10.0~bzr100+repack1-5~exp2 once more?
Sure thing. Sadly, if fails 6/20:
Control: reopen -1
Hi Mike,
On 17-05-2021 12:57, Mike Gabriel wrote:
> Can you do your autopkgtest magic with upcoming dbus-test-runner
> 16.10.0~bzr100+repack1-5~exp2 once more?
Sure thing. Sadly, if fails 6/20:
https://ci.debian.net/user/elb...@debian.org/jobs?package=dbus-test-runner
Paul
Processing control commands:
> reopen -1
Bug #986590 {Done: Mike Gabriel } [src:dbus-test-runner]
dbus-test-runner: flaky ppc64el autopkgtest: FAIL test-libdbustest-mock-test
(exit status: 1)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be
Hi Paul,
On Do 15 Apr 2021 13:50:31 CEST, Paul Gevers wrote:
Hi Mike,
On 15-04-2021 12:24, Mike Gabriel wrote:
Hi Paul,
Am Donnerstag, 15. April 2021 schrieb Paul Gevers:
Hi Mike,
On 14-04-2021 21:41, Mike Gabriel wrote:
Can you re-run those autopkgtests multiple times on ppc64el and
Hi Paul,
Am Donnerstag, 15. April 2021 schrieb Paul Gevers:
> Hi Mike,
>
> On 14-04-2021 21:41, Mike Gabriel wrote:
> > Can you re-run those autopkgtests multiple times on ppc64el and check if
> > the flakiness has now vanished with debhelper compat level bumped to
> > version 13? Thanks.
>
> I
Hi Mike,
On 15-04-2021 12:24, Mike Gabriel wrote:
> Hi Paul,
>
> Am Donnerstag, 15. April 2021 schrieb Paul Gevers:
>> Hi Mike,
>>
>> On 14-04-2021 21:41, Mike Gabriel wrote:
>>> Can you re-run those autopkgtests multiple times on ppc64el and check
if
>>> the flakiness has now vanished with
Hi Mike,
On 14-04-2021 21:41, Mike Gabriel wrote:
> Can you re-run those autopkgtests multiple times on ppc64el and check if
> the flakiness has now vanished with debhelper compat level bumped to
> version 13? Thanks.
I scheduled the job 21 times. It doesn't look good:
HI Paul
On Do 08 Apr 2021 09:15:17 CEST, Paul Gevers wrote:
Hi,
On 08-04-2021 08:40, Mike Gabriel wrote:
FAIL: ./test-libdbustest-mock
FAIL test-libdbustest-mock-test (exit status: 1)
This is a known issue for DBus unit tests in CI / buildd
infrastructures. (I don't remember the full
Hi Paul,
On Mi 07 Apr 2021 21:20:55 CEST, Paul Gevers wrote:
Source: dbus-test-runner
Version: 16.10.0~bzr100+repack1-4.1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org, t...@canonical.com
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
Hi,
On 08-04-2021 08:40, Mike Gabriel wrote:
>> FAIL: ./test-libdbustest-mock
>> FAIL test-libdbustest-mock-test (exit status: 1)
>
> This is a known issue for DBus unit tests in CI / buildd
> infrastructures. (I don't remember the full details / the bug number,
> but it is a problem caused by
Source: dbus-test-runner
Version: 16.10.0~bzr100+repack1-4.1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org, t...@canonical.com
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
Your package has an autopkgtest, great. However, I looked into
the
14 matches
Mail list logo
