openssl is still building (running tests) after ~6 hours. All of the gnome-panel build tasks have completed, but the main task is still open, tracker x86_64 job seems stuck installing the buildroot long after others have completed. etc...
On Wed, 2007-07-25 at 12:07 -0600, Orion Poplawski wrote:
openssl is still building (running tests) after ~6 hours. All of the gnome-panel build tasks have completed, but the main task is still open, tracker x86_64 job seems stuck installing the buildroot long after others have completed. etc...
The tests in openssl build are very slowly going ahead. So not stuck, but there is definitely something strange on the builders - the tests definitely shouldn't take so much time to finish.
On Wed, 2007-07-25 at 20:11 +0200, Tomas Mraz wrote:
On Wed, 2007-07-25 at 12:07 -0600, Orion Poplawski wrote:
openssl is still building (running tests) after ~6 hours. All of the gnome-panel build tasks have completed, but the main task is still open, tracker x86_64 job seems stuck installing the buildroot long after others have completed. etc...
The tests in openssl build are very slowly going ahead. So not stuck, but there is definitely something strange on the builders - the tests definitely shouldn't take so much time to finish.
Do the tests access the network or do DNS lookups? Besides being a no-no, I doubt that the chroot is set up with a proper resolv.conf etc.
Jeff
On Wed, 2007-07-25 at 13:13 -0500, Jeffrey C. Ollie wrote:
On Wed, 2007-07-25 at 20:11 +0200, Tomas Mraz wrote:
On Wed, 2007-07-25 at 12:07 -0600, Orion Poplawski wrote:
openssl is still building (running tests) after ~6 hours. All of the gnome-panel build tasks have completed, but the main task is still open, tracker x86_64 job seems stuck installing the buildroot long after others have completed. etc...
The tests in openssl build are very slowly going ahead. So not stuck, but there is definitely something strange on the builders - the tests definitely shouldn't take so much time to finish.
Do the tests access the network or do DNS lookups? Besides being a no-no, I doubt that the chroot is set up with a proper resolv.conf etc.
They do network communication and perhaps they even are trying to do some dns lookups if /etc/hosts is not set up properly to resolve the machine's hostname. But they should communicate only on the machine itself. Being a no-no means that we shouldn't be running them? They are very useful for for example finding bugs in compiler.
On Wed, 25 Jul 2007 20:30:21 +0200 Tomas Mraz tmraz@redhat.com wrote:
They do network communication and perhaps they even are trying to do some dns lookups if /etc/hosts is not set up properly to resolve the machine's hostname. But they should communicate only on the machine itself. Being a no-no means that we shouldn't be running them? They are very useful for for example finding bugs in compiler.
/etc/hosts has an entry for localhost, but it seems your test is trying to hit what is in /etc/resolv.conf which is a bogus IP. Perhaps your test is getting a hostname of the builder and trying to look that up?
Jesse Keating napsal(a):
On Wed, 25 Jul 2007 20:30:21 +0200 Tomas Mraz tmraz@redhat.com wrote:
They do network communication and perhaps they even are trying to do some dns lookups if /etc/hosts is not set up properly to resolve the machine's hostname. But they should communicate only on the machine itself. Being a no-no means that we shouldn't be running them? They are very useful for for example finding bugs in compiler.
/etc/hosts has an entry for localhost, but it seems your test is trying to hit what is in /etc/resolv.conf which is a bogus IP. Perhaps your test is getting a hostname of the builder and trying to look that up?
If we are talking about DNS problems (and when I add yesterday "cvs renumbering" problem or what it was) I think it would be good have DNS server in build system and builders will ask to them instead using /etc/hosts file.
Adam
On Wed, 25 Jul 2007 20:42:52 +0200 Adam Tkac atkac@redhat.com wrote:
If we are talking about DNS problems (and when I add yesterday "cvs renumbering" problem or what it was) I think it would be good have DNS server in build system and builders will ask to them instead using /etc/hosts file.
For the builders we have that taken care of. For the chroots we don't want them being able to resolve names or access the network.
On Wed, 2007-07-25 at 14:38 -0400, Jesse Keating wrote:
On Wed, 25 Jul 2007 20:30:21 +0200 Tomas Mraz tmraz@redhat.com wrote:
They do network communication and perhaps they even are trying to do some dns lookups if /etc/hosts is not set up properly to resolve the machine's hostname. But they should communicate only on the machine itself. Being a no-no means that we shouldn't be running them? They are very useful for for example finding bugs in compiler.
/etc/hosts has an entry for localhost, but it seems your test is trying to hit what is in /etc/resolv.conf which is a bogus IP. Perhaps your test is getting a hostname of the builder and trying to look that up?
Yes, it doesn't connect over localhost but over the machine hostname. Either in the buildroots the hostname should be set to localhost or the /etc/hosts in the buildroot should have an entry for the machine's hostname as 127.0.0.1.
Somebody in the thread at some point said:
On Wed, 2007-07-25 at 12:07 -0600, Orion Poplawski wrote:
openssl is still building (running tests) after ~6 hours. All of the gnome-panel build tasks have completed, but the main task is still open, tracker x86_64 job seems stuck installing the buildroot long after others have completed. etc...
The tests in openssl build are very slowly going ahead. So not stuck, but there is definitely something strange on the builders - the tests definitely shouldn't take so much time to finish.
crypto stuff can easily stall depending on entropy on /dev/random, maybe it is that.
-Andy
On Wed, 2007-07-25 at 19:30 +0100, Andy Green wrote:
Somebody in the thread at some point said:
On Wed, 2007-07-25 at 12:07 -0600, Orion Poplawski wrote:
openssl is still building (running tests) after ~6 hours. All of the gnome-panel build tasks have completed, but the main task is still open, tracker x86_64 job seems stuck installing the buildroot long after others have completed. etc...
The tests in openssl build are very slowly going ahead. So not stuck, but there is definitely something strange on the builders - the tests definitely shouldn't take so much time to finish.
crypto stuff can easily stall depending on entropy on /dev/random, maybe it is that.
Openssl prefers /dev/urandom over /dev/random if available.
Orion Poplawski napsal(a):
openssl is still building (running tests) after ~6 hours. All of the gnome-panel build tasks have completed, but the main task is still open, tracker x86_64 job seems stuck installing the buildroot long after others have completed. etc...
Builders are under heavy load due bug in gcc/binutils rebuilding
Adam
On 7/25/07, Adam Tkac atkac@redhat.com wrote:
Orion Poplawski napsal(a):
openssl is still building (running tests) after ~6 hours. All of the gnome-panel build tasks have completed, but the main task is still open, tracker x86_64 job seems stuck installing the buildroot long after others have completed. etc...
Builders are under heavy load due bug in gcc/binutils rebuilding
How much horsepower are they anyhow?