[opensuse-buildservice] workers fail with "Not an ARRAY reference at ./bs_worker line 671." after updating obs to 2.0.1
Hi, after I updated my OBS to 2.0.1, most of the builds fail with "Not an ARRAY reference at ./bs_worker line 671." without giving me a hint on which of the workers are failing. Even worse, not every build fails on a worker, so it's very hard to find out what to do... :-( It seems to be related to the disk cache. -- With best regards, Carsten Hoeger
On Mon, Jun 28, 2010 at 10:19:41AM +0200, Carsten Hoeger wrote:
Hi,
after I updated my OBS to 2.0.1, most of the builds fail with "Not???an???ARRAY???reference???at???./bs_worker???line???671." without giving me a hint on which of the workers are failing.
Even worse, not every build fails on a worker, so it's very hard to find out what to do... :-(
It seems to be related to the disk cache.
So how does the content look like, i.e. please do bs_admin --dump-relsync /<cachedir>/content Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Jun 28, Michael Schröder wrote:
after I updated my OBS to 2.0.1, most of the builds fail with "Not???an???ARRAY???reference???at???./bs_worker???line???671." without giving me a hint on which of the workers are failing.
Even worse, not every build fails on a worker, so it's very hard to find out what to do... :-(
It seems to be related to the disk cache.
So how does the content look like, i.e. please do
bs_admin --dump-relsync /<cachedir>/content
http://choeger.de/~choeger/dump.out.bz2 I did that on one of the many workers. Don't know, if that one is affected by that problem. -- With best regards, Carsten Hoeger
On Mon, Jun 28, Michael Schröder wrote:
after I updated my OBS to 2.0.1, most of the builds fail with "Not???an???ARRAY???reference???at???./bs_worker???line???671." without giving me a hint on which of the workers are failing.
Even worse, not every build fails on a worker, so it's very hard to find out what to do... :-(
It seems to be related to the disk cache.
So how does the content look like, i.e. please do
bs_admin --dump-relsync /<cachedir>/content
This is the content file from one of the "broken" workers. I found out which workers - sometimes - issue that error in adding that code to bs_worker: sub manage_cache { [...] $content ||= []; if( ref(@$content) ne "ARRAY" ) { die `uname -n`; } my %content = map {$_->[0] => $_->[1]} @$content; http://choeger.de/~choeger/content.bz2 -- With best regards, Carsten Hoeger
On Mon, Jun 28, 2010 at 11:28:16AM +0200, Carsten Hoeger wrote:
This is the content file from one of the "broken" workers. I found out which workers - sometimes - issue that error in adding that code to bs_worker:
sub manage_cache {
[...]
$content ||= []; if( ref(@$content) ne "ARRAY" ) {
I don't even know what 'ref' does if you give it an array as argument... Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Monday 2010-06-28 11:33, Michael Schroeder wrote:
On Mon, Jun 28, 2010 at 11:28:16AM +0200, Carsten Hoeger wrote:
This is the content file from one of the "broken" workers. I found out which workers - sometimes - issue that error in adding that code to bs_worker:
sub manage_cache {
[...]
$content ||= []; if( ref(@$content) ne "ARRAY" ) {
I don't even know what 'ref' does if you give it an array as argument...
Outputs the empty string. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Jun 28, Michael Schröder wrote:
This is the content file from one of the "broken" workers. I found out which workers - sometimes - issue that error in adding that code to bs_worker:
sub manage_cache {
[...]
$content ||= []; if( ref(@$content) ne "ARRAY" ) {
I don't even know what 'ref' does if you give it an array as argument...
Yes, that's nonsense which happened while op was under pressure... -- With best regards, Carsten Hoeger
participants (3)
-
Carsten Hoeger
-
Jan Engelhardt
-
Michael Schroeder