Hi Andreas, Hi Paul,
Paul Gevers, on 2020-12-10 13:50:59 +0100:
> On 10-12-2020 13:10, Andreas Tille wrote:
> > My guess is that kmc was developed under and designed for amd64 and it
> > runs there. That's explicitly the case for the latest upstream version
> > which will not support any arm*
Hi
On 10-12-2020 13:10, Andreas Tille wrote:
> On Thu, Dec 10, 2020 at 11:58:23AM +0100, Paul Gevers wrote:
>>> In the kmc case I'm seriously wondering whether we should restrict
>>> the architectures to those that are relevant in practice. It seems
>>> to be in line with upstream and I'm
On Thu, Dec 10, 2020 at 11:58:23AM +0100, Paul Gevers wrote:
> > In the kmc case I'm seriously wondering whether we should restrict
> > the architectures to those that are relevant in practice. It seems
> > to be in line with upstream and I'm tempted to follow Étienne's
> > suggestion to upgrade
Hi
Oops, missed a part of the message.
On 10-12-2020 11:00, Andreas Tille wrote:
>> It seems that this didn't work on our armhf worker:
>> https://ci.debian.net/packages/k/kmc/testing/armhf/
>>
>> The amd64 run didn't happen on the big box.
>
> In the kmc case I'm seriously wondering whether we
Hi Andreas,
On 10-12-2020 11:00, Andreas Tille wrote:
> just a general question: The general overview page like
>
>https://ci.debian.net/packages/k/kmc/
>
> does not seem to be updated while the specific architecture
> pages like
You can see at the bottom of the page when it was last
Hi Paul,
just a general question: The general overview page like
https://ci.debian.net/packages/k/kmc/
does not seem to be updated while the specific architecture
pages like
https://ci.debian.net/packages/k/kmc/testing/armhf/
shows the issue. I remember I was asking in connection with
Control: reopen -1
Control: retitle -1 kmc: autopgktest times out on multimulticore hosts
Hi
On 06-12-2020 22:06, Étienne Mollier wrote:
> Paul Gevers, on 2020-12-06 20:54:43 +0100:
>> It recently started to time out on amd64 too, but not always [1]. And
>> when we added armhf, that timed out
Control: tag -1 + confirmed
Control: tag -1 - unreproducible
Hi Paul,
Paul Gevers, on 2020-12-06 20:54:43 +0100:
> It recently started to time out on amd64 too, but not always [1]. And
> when we added armhf, that timed out too. The failures on amd64 that I
> checked were all on ci-worker13,
Control: severity -1 serious
Hi Étielle,
On 06-12-2020 19:31, Étienne Mollier wrote:
> I tried to trigger the kmc bug #954270 from an autopkgtest run
> within a qemu-user arm64 machine (host amd64). Unfortunately, I
> failed to reproduce any freeze; the run executes in a matter of
> a minute or
Control: tag -1 + unreproducible
Hi there,
I tried to trigger the kmc bug #954270 from an autopkgtest run
within a qemu-user arm64 machine (host amd64). Unfortunately, I
failed to reproduce any freeze; the run executes in a matter of
a minute or two. I don't see any changes that would visibly
10 matches
Mail list logo
