glibc 2.28 machine testing.

glibc 2.28 machine testing.

[Carlos O'Donell]

Maintainers,

We are doing machine testing for glibc 2.28 to get results from all the
machine maintainers and put it on the wiki for the release:
https://sourceware.org/glibc/wiki/Release/2.28

Please test glibc master for your machine :-)

You may also want to cleanup your ULPS results.

Tulio,

Are you able to test the 32-bit power builds and make sure they are OK?

Richard,

Are you able to test the Alpha builds and make sure they are OK?

Dave,

Are you able to test hppa?

Mike,

Are you you able to test ia64?

David,

Are you able to test Microblaze?

Maciej,

Are you able to help with some of the mips testing?

DJ,

Are you able to test RISC-V? Or get Palmer or Darius?

Chung-Lin,

Are you able to test NIOS II?

Stefan,

Are you able to test 32-bit s390 and provide another set of test result for s390x?

David,

Are you able to test sparc?

Cheers,
Carlos.

Re: glibc 2.28 machine testing.

[Palmer Dabbelt]

On Thu, 26 Jul 2018 18:20:21 PDT (-0700), carlos@redhat.com wrote:
> Maintainers,
>
> We are doing machine testing for glibc 2.28 to get results from all the
> machine maintainers and put it on the wiki for the release:
> https://sourceware.org/glibc/wiki/Release/2.28
>
> Please test glibc master for your machine :-)
>
> You may also want to cleanup your ULPS results.
>
> DJ,
>
> Are you able to test RISC-V? Or get Palmer or Darius?

We've got a thread going, DJ and Darius are both running tests (as is Jim 
Wilson, our binutils/GCC maintainer here at SiFive, as he has the environment 
set up).

Our implementations are a bit on the slow side so it might take a bit to finish 
:).

Re: glibc 2.28 machine testing.

[Carlos O'Donell]

On 07/26/2018 09:20 PM, Carlos O'Donell wrote:
> Maintainers,
> 
> We are doing machine testing for glibc 2.28 to get results from all the
> machine maintainers and put it on the wiki for the release:
> https://sourceware.org/glibc/wiki/Release/2.28
> 
> Please test glibc master for your machine :-)
> 
> You may also want to cleanup your ULPS results.

[snip]

> David,
> 
> Are you able to test Microblaze?

David (corrected email), Nagaraju,

Are either of you able to test glibc master for microblaze?

Thank you!

Cheers,
Carlos.

Re: glibc 2.28 machine testing.

[Richard Henderson]

On 07/26/2018 06:20 PM, Carlos O'Donell wrote:
> Richard,
> 
> Are you able to test the Alpha builds and make sure they are OK?

Starting them now.


r~

Re: glibc 2.28 machine testing.

[Stefan Liebler]

> Stefan,
> 
> Are you able to test 32-bit s390 and provide another set of test result for s390x?

Yes, I will provide the test results for s390 and further ones for s390x.

Bye
Stefan

Re: glibc 2.28 machine testing.

[Maciej W. Rozycki]

Hi Carlos,

> Maciej,
> 
> Are you able to help with some of the mips testing?

 I'd love to, but I have no means.

 Firstly, I'm no longer at MIPS and obviously can't use the company 
infrastructure anymore.

 Secondly, my personal remote lab is currently offline and I cannot access 
it, as the ISP the lab has been wired to decided they need to change the 
infrastructure I've been using and cut me off.  They have been very 
reluctant to sort it out (it took them a month to give me an initial reply 
to the complaint I made, and then only to say that the complaint was 
missing some information) in what I believe is an attempt to force me to 
accept a change of the conditions of the agreement I have with them, after 
they have acquired the ISP I originally signed the agreement with.  
Needless to say the choice of ISPs is very limited there and I have no 
idea how long it will take to get the lab back online.

 Sorry. :(

  Maciej

RE: glibc 2.28 machine testing.

[Nagaraju Mekala]

> -----Original Message-----
> From: Carlos O'Donell [mailto:carlos@redhat.com]
> Sent: Friday, July 27, 2018 7:11 AM
> To: GNU C Library <libc-alpha@sourceware.org>; David Holsgrove
> <david@holsgrove.tech>; Nagaraju Mekala <nmekala@xilinx.com>
> Subject: Re: glibc 2.28 machine testing.
> 
> On 07/26/2018 09:20 PM, Carlos O'Donell wrote:
> > Maintainers,
> >
> > We are doing machine testing for glibc 2.28 to get results from all
> > the machine maintainers and put it on the wiki for the release:
> > https://sourceware.org/glibc/wiki/Release/2.28
> >
> > Please test glibc master for your machine :-)
> >
> > You may also want to cleanup your ULPS results.
> 
> [snip]
> 
> > David,
> >
> > Are you able to test Microblaze?
> 
> David (corrected email), Nagaraju,
> 
> Are either of you able to test glibc master for microblaze?
Starting them now.

Thanks,
Nagaraju 

Re: glibc 2.28 machine testing.

[Tulio Magno Quites Machado Filho]

Carlos O'Donell <carlos@redhat.com> writes:

> Tulio,
>
> Are you able to test the 32-bit power builds and make sure they are OK?

Yes.

-- 
Tulio Magno

Re: glibc 2.28 machine testing.

[John David Anglin]

On 2018-07-26 9:20 PM, Carlos O'Donell wrote:
> Dave,
>
> Are you able to test hppa?
Started.

Dave

-- 
John David Anglin  dave.anglin@bell.net

Re: glibc 2.28 machine testing.

[Adhemerval Zanella]

On 26/07/2018 22:20, Carlos O'Donell wrote:
> 
> Mike,
> 
> Are you you able to test ia64?
> 
I have updated the ia64 testing output.

Re: glibc 2.28 machine testing.

[Joseph Myers]

On Thu, 26 Jul 2018, Carlos O'Donell wrote:

> Maintainers,
> 
> We are doing machine testing for glibc 2.28 to get results from all the
> machine maintainers and put it on the wiki for the release:
> https://sourceware.org/glibc/wiki/Release/2.28
> 
> Please test glibc master for your machine :-)
> 
> You may also want to cleanup your ULPS results.

You didn't ask anyone to test m68k, sh or Hurd.  Are you planning to test 
those yourself? :-)

-- 
Joseph S. Myers
joseph@codesourcery.com

Re: glibc 2.28 machine testing.

[Samuel Thibault]

Joseph Myers, le ven. 27 juil. 2018 16:09:32 +0000, a ecrit:
> On Thu, 26 Jul 2018, Carlos O'Donell wrote:
> > We are doing machine testing for glibc 2.28 to get results from all the
> > machine maintainers and put it on the wiki for the release:
> > https://sourceware.org/glibc/wiki/Release/2.28
> > 
> > Please test glibc master for your machine :-)
> > 
> > You may also want to cleanup your ULPS results.
> 
> You didn't ask anyone to test m68k, sh or Hurd.  Are you planning to test 
> those yourself? :-)

I'm doing the Hurd part for the general tests. I'm not sure I'll have
the time to run ULPS. In principle the results are basically the same as
linux i386, the difference is mostly due to my usually running in a VM.

Samuel

Re: glibc 2.28 machine testing.

[Joseph Myers]

On Fri, 27 Jul 2018, Samuel Thibault wrote:

> I'm doing the Hurd part for the general tests. I'm not sure I'll have
> the time to run ULPS. In principle the results are basically the same as
> linux i386, the difference is mostly due to my usually running in a VM.

ulps files aren't OS-specific so you shouldn't have to do anything there.

-- 
Joseph S. Myers
joseph@codesourcery.com

Re: glibc 2.28 machine testing.

[Samuel Thibault]

Joseph Myers, le ven. 27 juil. 2018 16:28:06 +0000, a ecrit:
> On Fri, 27 Jul 2018, Samuel Thibault wrote:
> > I'm doing the Hurd part for the general tests. I'm not sure I'll have
> > the time to run ULPS. In principle the results are basically the same as
> > linux i386, the difference is mostly due to my usually running in a VM.
> 
> ulps files aren't OS-specific so you shouldn't have to do anything there.

Sure, I just happened to have issues just because of running in a VM
(IIRC running Linux in the same VM got the same ULPS issues)

Samuel

Re: glibc 2.28 machine testing.

[Carlos O'Donell]

On 07/27/2018 12:09 PM, Joseph Myers wrote:
> On Thu, 26 Jul 2018, Carlos O'Donell wrote:
> 
>> Maintainers,
>>
>> We are doing machine testing for glibc 2.28 to get results from all the
>> machine maintainers and put it on the wiki for the release:
>> https://sourceware.org/glibc/wiki/Release/2.28
>>
>> Please test glibc master for your machine :-)
>>
>> You may also want to cleanup your ULPS results.
> 
> You didn't ask anyone to test m68k, sh or Hurd.  Are you planning to test 
> those yourself? :-)

I *manage* the release ;-)

Andreas,

Would you be able to test m68k?

Samuel or Thomas,

Would you be able to test hurd please?

Cheers,
Carlos.