Hi Florian,
On 2019-03-27 23:59, Florian Weimer wrote:
> retitle 924891 glibc: misc/tst-pkey fails due to cleared PKRU register after
> signal in amd64 32-bit compat mode
> thanks
>
> * Lucas Nussbaum:
>
> > On 27/03/19 at 08:48 +0100, Florian Weimer wrote:
> >> > If that's useful, I can
On 27/03/19 at 23:59 +0100, Florian Weimer wrote:
> retitle 924891 glibc: misc/tst-pkey fails due to cleared PKRU register after
> signal in amd64 32-bit compat mode
> thanks
>
> * Lucas Nussbaum:
>
> > On 27/03/19 at 08:48 +0100, Florian Weimer wrote:
> >> > If that's useful, I can easily
Processing commands for cont...@bugs.debian.org:
> retitle 924891 glibc: misc/tst-pkey fails due to cleared PKRU register after
> signal in amd64 32-bit compat mode
Bug #924891 [src:glibc] glibc: FTBFS: tst-pkey fails for 32-bit processes on
Xeon SP
Changed Bug title to 'glibc: misc/tst-pkey
retitle 924891 glibc: misc/tst-pkey fails due to cleared PKRU register after
signal in amd64 32-bit compat mode
thanks
* Lucas Nussbaum:
> On 27/03/19 at 08:48 +0100, Florian Weimer wrote:
>> > If that's useful, I can easily provide access to an AWS VM to debug this
>> > issue.
>>
>> Oh, that
On 27/03/19 at 22:00 +0100, Lucas Nussbaum wrote:
> On 27/03/19 at 08:48 +0100, Florian Weimer wrote:
> > > If that's useful, I can easily provide access to an AWS VM to debug this
> > > issue.
> >
> > Oh, that would be quite helpful indeed.
>
> Can you send your SSH key? (I thought there was a
On 27/03/19 at 08:48 +0100, Florian Weimer wrote:
> > If that's useful, I can easily provide access to an AWS VM to debug this
> > issue.
>
> Oh, that would be quite helpful indeed.
Can you send your SSH key? (I thought there was a way to get the SSH key
for a DD, but I cannot find it anymore)
* Lucas Nussbaum:
> On 26/03/19 at 23:10 +0100, Aurelien Jarno wrote:
>> On 2019-03-22 17:30, Florian Weimer wrote:
>> > > About the archive rebuild: The rebuild was done on EC2 VM instances from
>> > > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
>> > > failed build
On 26/03/19 at 23:10 +0100, Aurelien Jarno wrote:
> On 2019-03-22 17:30, Florian Weimer wrote:
> > > About the archive rebuild: The rebuild was done on EC2 VM instances from
> > > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> > > failed build was retried once to
On 2019-03-22 17:30, Florian Weimer wrote:
> > About the archive rebuild: The rebuild was done on EC2 VM instances from
> > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> > failed build was retried once to eliminate random failures.
>
> I believe the actual test
On 22/03/19 at 17:30 +0100, Florian Weimer wrote:
> > About the archive rebuild: The rebuild was done on EC2 VM instances from
> > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> > failed build was retried once to eliminate random failures.
>
> I believe the actual test
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
I believe the actual test failure is tst-pkey.
Presumably, this rebuild was
11 matches
Mail list logo
