[opensuse-buildservice] Kiwi-inside-obs - bug-squashing the loop
Hi! We improved kiwi now to be able to build also images for arm (and other architectures) on an x86 host. Only remaining is the rebuild-loop when kiwi is used inside obs. Let's hunt that little bug now ;). Summary: The scenario is like this: project "imaging:Admin", package "foo", repository "image". Simple kiwi-config (only bootstrap section!), output is ext2-image. Filename ends in "*0.0.1" (version in the kiwi.xml). So far: build succeeds, things get uploaded here (also show up in /srv/obs/build/<foo>), BUT not in /srv/obs/repos and the job is directly rescheduled and thus builds in a loop. here's the scheduler-log: event finished:imaging::image::obs-imaging-8d2731b6e7128e3694ffb623f20177a6 0 left) - imaging/image: obs-imaging built: 3 files looking at med prio imaging/image (0/0/1/0/17) - imaging/image expanding dependencies sorting 1 packages - obs-imaging (kiwi) +autoconf +automake [...] +openvpn +perl-base +python +python-xml +rpm +rpm-python +smart +terminfo-base +xenomai +zlib meta change, start build Use of uninitialized value in substitution (s///) at BSFileDB.pm line 86. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 1. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 1. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 1. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 2. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 2. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 2. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 3. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 3. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 3. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 4. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 4. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 4. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 5. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 5. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 5. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 6. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 6. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 6. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 7. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 7. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 7. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 8. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 8. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 8. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 9. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 9. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 9. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 10. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 10. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 10. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 11. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 11. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 11. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 12. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 12. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 12. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 13. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 13. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 13. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 14. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 14. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 14. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 15. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 15. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 15. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 16. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 16. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 16. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 17. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 17. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 17. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 18. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 18. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 18. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 19. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 19. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 19. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 20. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 20. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 20. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 21. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 21. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 21. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 22. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 22. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 22. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 23. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 23. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 23. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 24. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 24. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 24. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 25. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 25. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 25. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 26. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 26. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 26. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 27. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 27. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 27. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 28. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 28. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 28. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 29. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 29. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 29. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 30. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 30. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 30. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 31. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 31. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 31. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 32. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 32. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 32. scheduled: 1 building: 1, notready: 1 took 0 seconds to check the packages looking at low prio imaging/image (0/0/0/0/17) - imaging/image expanding dependencies sorting 1 packages scheduled: 1 building: 1, notready: 1 took 0 seconds to check the packages waiting for an event... Looks like BSFileDB doesn't find variables in this case. My worker sends these files: $VAR1 = [ { 'filename' => '/tmp//root_1/.build.packages/KIWI/limbo-auto-config.i686-0.0.1', 'name' => 'limbo-auto-config.i686-0.0.1' }, { 'filename' => '/tmp//root_1/.build.meta', 'name' => 'meta' }, { 'filename' => '/tmp//root_1/.build.log', 'name' => 'logfile' } ]; We need to find a way to accept kiwi's output filenames (other than .iso). I looked at bs_sched, but I'm (a bit) lost finding the right spot. best regards, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, Oct 30, 2008 at 08:02:35PM +0100, Jan-Simon Möller wrote:
We improved kiwi now to be able to build also images for arm (and other architectures) on an x86 host. Only remaining is the rebuild-loop when kiwi is used inside obs.
Let's hunt that little bug now ;).
Actually I'm just fixing this. Should work with the next SVN checkin. M. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Michael Schroeder wrote:
On Thu, Oct 30, 2008 at 08:02:35PM +0100, Jan-Simon Möller wrote:
We improved kiwi now to be able to build also images for arm (and other architectures) on an x86 host. Only remaining is the rebuild-loop when kiwi is used inside obs.
Let's hunt that little bug now ;).
Actually I'm just fixing this. Should work with the next SVN checkin.
M.
I might be the "rebuild loop" bug of Download on Demand, Marcus fixed yesterday. I put new packages for cross-build inside openSUSE:Tools:Devel with the fix. You may give it a try.. Martin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Freitag 31 Oktober 2008 11:05:56 schrieb Michael Schroeder:
Let's hunt that little bug now ;).
Actually I'm just fixing this. Should work with the next SVN checkin.
Thats great news! I just came across an issue again, which is pretty annoying for imaging, if you use more than one source-repo. The image-repo needs to be derived from a repo knowing all packages, or there will be an "expansion error". Thats clear, because not all packages are part of all repos. But it wouldn't be better to let the imaging inspec the .kiwi and calculate the availability according to the used obs///-links ? The image-repo could be an "empty" repo then. IMHO this would be more flexible, or ? Best regards, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, Oct 31, 2008 at 04:09:20PM +0100, Jan-Simon Möller wrote:
Am Freitag 31 Oktober 2008 11:05:56 schrieb Michael Schroeder:
Let's hunt that little bug now ;).
Actually I'm just fixing this. Should work with the next SVN checkin.
Thats great news!
Ok, I checked in a new version of the scheduler, but the kiwi-image part isn't well tested. There are probably still some bugs lurking around (in bs_worker maybe). 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
Am Freitag 31 Oktober 2008 17:52:32 schrieb Michael Schroeder:
Ok, I checked in a new version of the scheduler, but the kiwi-image part isn't well tested. There are probably still some bugs lurking around (in bs_worker maybe).
Atm. I'm stuck here with: expansion error: nothing provides kiwi And no "Ignore:" or packages providing kiwi do help. Best regards, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
A scheduler restart got me a step further: got job, run build... Building 'imaging' for project '' repository 'lire/base_toolchain' arch 'i586' using helper linux32 fetching sources...remote error: 404 projid is empty Best regards, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Freitag 31 Oktober 2008 17:52:32 schrieb Michael Schroeder:
Ok, I checked in a new version of the scheduler, but the kiwi-image part isn't well tested. There are probably still some bugs lurking around (in bs_worker maybe).
Just a small remark/question: Its ~ line 450 in bs_worker. A dump of $buildinfo->{'path'} looks here like: { 'repository' => 'lire/base_toolchain/', 'project' => '', 'server' => 'http://192.168.10.246:6262' }, { 'repository' => 'lire_own/standard/', 'project' => '', 'server' => 'http://192.168.10.246:6262' }, { 'repository' => 'base_toolchain/standard/', 'project' => '', 'server' => 'http://192.168.10.246:6262' } ]; The repo/project isn't split correctly (probably bs_sched 1441?) and shouldn't we iterate over 'path' ? Atm its only $buildinfo->{'path'}->[0] ;) . Big thanks for the checkin, Michael! Best regards, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
[back from 1 day vacation, sorry for the delay] On Mon, Nov 03, 2008 at 06:13:21PM +0100, Jan-Simon Möller wrote:
Its ~ line 450 in bs_worker. A dump of $buildinfo->{'path'} looks here like: { 'repository' => 'lire/base_toolchain/', 'project' => '', 'server' => 'http://192.168.10.246:6262' }, { 'repository' => 'lire_own/standard/', 'project' => '', 'server' => 'http://192.168.10.246:6262' }, { 'repository' => 'base_toolchain/standard/', 'project' => '', 'server' => 'http://192.168.10.246:6262' } ];
The repo/project isn't split correctly (probably bs_sched 1441?) and shouldn't we iterate over 'path' ?
Sounds like the kiwi parser in bs_srcsrv doesn't set the path info correctly. I'll have a look... M. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Nov 04, 2008 at 10:14:25AM +0100, Michael Schroeder wrote:
Sounds like the kiwi parser in bs_srcsrv doesn't set the path info correctly. I'll have a look...
Does your kiwi config contain obs:/// instead of obs:// ? M. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Nov 04, 2008 at 10:16:59AM +0100, Michael Schroeder wrote:
On Tue, Nov 04, 2008 at 10:14:25AM +0100, Michael Schroeder wrote:
Sounds like the kiwi parser in bs_srcsrv doesn't set the path info correctly. I'll have a look...
Does your kiwi config contain obs:/// instead of obs:// ?
That brings me to the question: is obs:/// more correct that obs://? M. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag 04 November 2008 10:28:34 schrieb Michael Schroeder:
That brings me to the question: is obs:/// more correct that obs://?
I extract the 2 parts also from an url, so i had also a "/" at the end. with only obs://part1/part2 (and no "/" at the end) it works. The job fails, because the worker doesn't know the output file extension. Will reply with a patch. But kiwi has more output filetypes. best regards, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Here are 2 patches for the filetypes kiwi uses - as schafi told me ... But that seems to be not the only problem ... " Nov-04 11:08:26 <1> : KIWI exited successfully done build succeeded $VAR1 = []; build did not create anything to send back! build failed, send back logfile... sent, all done... " $VAR1 is the @files to send. I tried to handle this - look at worker_kiwifiletypes_extended.diff . Then the build sends files back but still rebuilds in a loop. Probably it fails somewhere else ... best regards, Jan-Simon
participants (3)
-
Jan-Simon Möller -
Martin Mohring -
Michael Schroeder