This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[RFC] Automatic nightly builds?


On Tue, Jul 16, 2013 at 06:07:35PM -0400, Carlos O'Donell wrote:
> Community,
> 
> How are the machine builds going?
> 
Given that now it may take while until we find problem with some of less
used architectures we could speed this process by doing nightly builds.

How many of you could add a cron job that test given machine on nightly
basis?

You could report results by sending email every time there is difference
in failures.
A sample bash script to list failures is below.

Alternatively you can use an procmail hook to check mails beggining with
[PATCH] to run testsuite with that patch and use script below to find
difference with patch applied and without it.

Comments?


git pull
mkdir test
cd test
../glibc/configure --prefix=/usr # TODO configure failure
make # TODO build failures
make -k check 
for I in `find | grep .out$`; do
  if [ -z "`diff $I ../oldtest/$I 2>&1`" ]
    true
  else
    echo $I
  fi
done
rm -rf oldtest
mv test oldtest


> Please update "Current Status" so we can make the release.
> http://sourceware.org/glibc/wiki/Release/2.18#Current_Status
> 
> Marcus, How is AArch64?
> 
> H.J, How is x32?
> 
> Thomas, Roland, How is GNU/Hurd?
> 
> Andreas, How is s390?
> 
> David, How are SPARC and SPARC64?
> 
> Mike, How is IA64?
> 
> Carlos, How is hppa?
> 
> Kaz, Thomas, How is SH?
> 
> Chris, How is Tile?
> 
> Andreas, How is m68k?
> 
> Cheers,
> Carlos.

-- 

manager in the cable duct


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]