openSUSE Build Service July 2015

buildservice@lists.opensuse.org

17 participants
16 discussions

[opensuse-buildservice] enabling networking for workers

by Darin Perusich

Hello All, I'm running a private instance and I'd like to enable networking on my workers so they can build some java apps, via maven, which need to download pom's/war's from the net. I ask google but he wasn't much help so I'm hoping someone here can help;-) How can I go about doing this? -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 years, 6 months

[opensuse-buildservice] broken mirror tux.rainside.sk

by Olaf Hering

Not sure what the correct list is to report mirror issues, but http://tux.rainside.sk/opensuse/ is empty. laf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 years, 5 months

[opensuse-buildservice] SLE_12: build host kernel problems

by Ruediger Meier

Hi, I get kernel oopses very often for SLE_12 builds on x86_64 and ppc64le. Is this a known problem? Here one example for SLE_12 x86_64: [ 205.213153] BUG: unable to handle kernel paging request at ffffffffa01fae60 [ 205.214124] IP: [<ffffffffa01fae60>] 0xffffffffa01fae60 [ 205.214914] PGD 1a0d067 PUD 1a0e063 PMD 1f99fd067 PTE 0 [ 205.215738] Oops: 0010 [#1] SMP [ 205.216239] Modules linked in: sd_mod raid1 raid0 md_mod cramfs ext4 crc16 mbcache jbd2 sr_mod cdrom ata_generic virtio_blk ata_piix ahci libahci libata scsi_mod virtio_pci virtio_ring virtio binfmt_misc loop autofs4 [last unloaded: scsi_debug] [ 205.217089] Supported: Yes [ 205.217089] CPU: 2 PID: 24652 Comm: systemd-udevd Not tainted 3.12.28-4-default #1 [ 205.217089] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.7.5.1-0-g8936dbb-20150318_003745-cloud117 04/01/2014 [ 205.217089] task: ffff8800bad38040 ti: ffff8800bad32000 task.ti: ffff8800bad32000 [ 205.217089] RIP: 0010:[<ffffffffa01fae60>] [<ffffffffa01fae60>] 0xffffffffa01fae60 [ 205.224409] RSP: 0018:ffff8800bad33d50 EFLAGS: 00010286 [ 205.225280] RAX: ffffffffa01fae60 RBX: ffff8801f9b39028 RCX: 0000000000000286 [ 205.226668] RDX: ffff8801f9b39260 RSI: 0000000000000286 RDI: ffff8801f9b39018 [ 205.227561] RBP: ffff8801f9b39018 R08: ffff8800bad32000 R09: 0000000000000000 [ 205.227561] R10: ffffffff81f7b558 R11: 0000000000000000 R12: ffff8801a8f56180 [ 205.227561] R13: ffff8801f9439bd8 R14: 000000000000005d R15: 0000000000000000 [ 205.227561] FS: 00007f434c12c880(0000) GS:ffff880204f00000(0000) knlGS:0000000000000000 [ 205.227561] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 205.227561] CR2: ffffffffa01fae60 CR3: 00000000bad72000 CR4: 00000000000407e0 [ 205.232887] Stack: [ 205.232887] ffffffff81393a7d ffff8801f9b39028 ffffffff81ae4d40 ffff8801f8c63a80 [ 205.232887] ffffffff8129a352 ffff8800bb46c800 ffff8801f9b39018 ffff8801a8f56300 [ 205.232887] ffffffffa003be21 ffff8800bb46c9a0 ffff8800bb46c990 ffff8801a8f56300 [ 205.232887] Call Trace: [ 205.232887] Inexact backtrace: [ 205.232887] [ 205.232887] [<ffffffff81393a7d>] ? device_release+0x2d/0xa0 [ 205.232887] [<ffffffff8129a352>] ? kobject_cleanup+0x72/0x1a0 [ 205.232887] [<ffffffffa003be21>] ? scsi_host_dev_release+0xc1/0xe0 [scsi_mod] [ 205.232887] [<ffffffff81393a7d>] ? device_release+0x2d/0xa0 [ 205.232887] [<ffffffff8129a352>] ? kobject_cleanup+0x72/0x1a0 [ 205.232887] [<ffffffff81393a7d>] ? device_release+0x2d/0xa0 [ 205.232887] [<ffffffff8129a352>] ? kobject_cleanup+0x72/0x1a0 [ 205.232887] [<ffffffff8106db07>] ? execute_in_process_context+0x67/0x70 [ 205.232887] [<ffffffff81393a7d>] ? device_release+0x2d/0xa0 [ 205.232887] [<ffffffff8129a352>] ? kobject_cleanup+0x72/0x1a0 [ 205.232887] [<ffffffffa021077b>] ? scsi_disk_put+0x2b/0x40 [sd_mod] [ 205.232887] [<ffffffff811d55bd>] ? __blkdev_put+0x15d/0x1a0 [ 205.232887] [<ffffffff811d6011>] ? blkdev_close+0x21/0x30 [ 205.248034] [<ffffffff811a0382>] ? __fput+0xc2/0x240 [ 205.248034] [<ffffffff81073947>] ? task_work_run+0x97/0xd0 [ 205.248034] [<ffffffff81002929>] ? do_notify_resume+0x69/0xa0 [ 205.248034] [<ffffffff81519603>] ? int_signal+0x12/0x17 [ 205.248034] Code: Bad RIP value. [ 205.248034] RIP [<ffffffffa01fae60>] 0xffffffffa01fae60 [ 205.248034] RSP <ffff8800bad33d50> [ 205.248034] CR2: ffffffffa01fae60 [ 205.248034] ---[ end trace ec1ae60827e0b798 ]--- [ 205.254616] systemd-udevd[1223]: worker [24652] terminated by signal 9 (Killed) [ 205.255711] systemd-udevd[1223]: worker [24652] failed while handling '/devices/pseudo_0/adapter0/host10/target10:0:0/10:0:0:0/block/sda/sda1' [ 205.454695] scsi_debug: host protection [ 205.455316] scsi11 : scsi_debug, version 1.82 [20100324], dev_size_mb=50, opts=0x0 [ 205.456558] scsi 11:0:0:0: Direct-Access Linux scsi_debug 0004 PQ: 0 ANSI: 5 [ 205.460037] sd 11:0:0:0: [sda] 102400 512-byte logical blocks: (52.4 MB/50.0 MiB) [ 205.464032] sd 11:0:0:0: [sda] Write Protect is off [ 205.464732] sd 11:0:0:0: [sda] Mode Sense: 73 00 10 08 [ 205.472036] sd 11:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA qemu: terminating on signal 15 from pid 25397 Killed Job ### WATCHDOG MARKER END ### No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) or the build host has a kernel or hardware problem... -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 years, 3 months

[opensuse-buildservice] Ghost package

by trcs＠gmx.com

Hi. There is a ghost package in my OBS home project. I'm using the web interface, not the command line one. If you go to https://build.opensuse.org/project/show/home:jcsl:LXDE you can see the real 10 packages in the Packages box on left side, but if you look in the Build Results box, on the right side, you see 11 next to the "succeeded" text. If you then click the succeeded link you find the pcmanfm-1.2.0-beta1 package, and if you click on its link you get a Package "pcmanfm-1.2.0-beta1" not found in project "home:jcsl:LXDE", as expected. It even appears in the scheduled and building states when something I'm building triggers its build (I don't know how can this be). Any hints? Greetings. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 years, 6 months

[opensuse-buildservice] Tools repo trouble

by Bruno Friedmann

On openSUSE 13.1 with repo tools [1] There's a problem with nothing provide python-packaging can't install obs-service-set_version-0.5.0-44.1-noarch A missing link or aggregate for 13.1 ? [1] repositories/openSUSE:/Tools/openSUSE_13.1 An idea how to fix it? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 years, 11 months

[opensuse-buildservice] Broken Debian/Ubuntu builds

by Sven Hesse

Hej hej! Sometime between July 19 and today, July 23, the building of deb packages for Debian and Ubuntu broke in the public instance of OBS, at least for the generated / munged Debian control files. Here's a log of a new, broken build: <https://build.opensuse.org/build/home:DrMcCoy:xoreos/Debian_8.0/x86_64/xore…> and a log of an old, working build: <https://build.opensuse.org/build/home:DrMcCoy:xoreos/Debian_8.0/i586/xoreos…> The broken build worked previously, but after hitting "Trigger rebuild", it fails. Nothing was changed in that package. The relevant error message is this: | dpkg-genchanges -v~0 >../xoreos_0.0.1_amd64.changes | parsechangelog/debian: warning: 'since' option specifies non-existing version | parsechangelog/debian: warning: use newest entry that is earlier than the one specified | parsechangelog/debian: error: parsechangelog/debian: error: ~0 is not a valid version | | dpkg-genchanges: error: changelog parser /usr/lib/dpkg/parsechangelog/debian gave error exit status 255 | dpkg-buildpackage: error: dpkg-genchanges gave error exit status 255 while previously, the dpkg-genchanges call was this: | dpkg-genchanges >../xoreos_0.0.1_i386.changes I.e. something now sets -v ($since in dpkg-buildpackage) to "~0". I can't see in the logs where that's coming from, so I guess that's the OBS scripts doing that? Or am I missing or forgetting something in the source files, that now somehow shows? Thanks, Sven -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 years, 11 months

[opensuse-buildservice] Failing Debian Builds

by James Geboski

Debian builds are failing due to a missing DEBVERSION environment variable, which was introduced by openSUSE/obs-build#175 [1]. This patch should have included some sort of backwards compatibility via a conditional check for DEBVERSION being nonempty. I would gladly submit a patch for this if I had some sort of easy way to test the patch, which I do not. Also, how does one go about setting the DEBVERSION variable for OBS? Is this even possible? Relevant log output: [ 40s] dpkg-deb: building package `bitlbee-facebook' in `../bitlbee-facebook_17~f55536c_i386.deb'. [ 40s] dpkg-genchanges -v~0 >../bitlbee-facebook_17~f55536c_i386.changes [ 40s] parsechangelog/debian: warning: 'since' option specifies non-existing version [ 40s] parsechangelog/debian: warning: use newest entry that is earlier than the one specified [ 40s] parsechangelog/debian: error: parsechangelog/debian: error: ~0 is not a valid version [ 40s] [ 40s] dpkg-genchanges: error: changelog parser /usr/lib/dpkg/parsechangelog/debian gave error exit status 255 [ 40s] dpkg-buildpackage: error: dpkg-genchanges gave error exit status 255 James [1] https://github.com/openSUSE/obs-build/pull/175 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 years, 11 months

[opensuse-buildservice] Workers building Staging:E are stuck

by Brüns, Stefan

Hi, all the workers building openSUSE:Factory:Staging:E are stuck with a segfault in systemd, e.g.: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Kind regards, Stefan Log excerpt: [ 11s] copying packages... [ 18s] reordering...cycle: libcrack2 -> cracklib [ 18s] breaking dependency libcrack2 -> cracklib [ 18s] done [ 18s] BFD: /var/cache/obs/worker/root_4/.mount/.build.kernel.xen: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss [ 19s] ### WATCHDOG MARKER START ### [ 19s] booting xen... [ 19s] xl create -c /var/tmp/build.xen.conf-iZjHG2Cab name="build_4" disk=[ "phy:/dev/dm-6,hda1,w", "phy:/dev/dm-7,hda2,w" ] extra="panic=1 quiet init=/.build/build rd.driver.pre=binfmt_misc elevator=noop console=ttyS0" [ 19s] Parsing config from /var/tmp/build.xen.conf-iZjHG2Cab [ 20s] [ 0.154583] PCI: Fatal: No config space access function found [ 20s] [ 0.161736] Unable to read sysrq code in control/sysrq [ 26s] [ 5.474026] i8042: No controller found [ 26s] [ 5.482103] mce: Unable to init device /dev/mcelog (rc: -5) [ 26s] [ 5.556674] systemd[1]: segfault at 8 ip 00007f3e5d6a4793 sp 00007ffe80f3b4f8 error 4 in libc-2.21.so[7f3e5d626000+199000] [ 26s] [ 5.559622] systemd[1]: Caught <SEGV>, dumped core as pid 69. [ 26s] [ 5.559773] systemd[1]: Freezing execution. [ 325s] ### WATCHDOG TRIGGERED, KILLING VM ### -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 years, 11 months

[opensuse-buildservice] What to do about builds running amok?

by Stefan Bruens

Hi, I just stumbled over a build starting again and again due to a kernel panic: https://build.opensuse.org/package/live_build_log/home:steffens:SmartClient… How to deal with this? Kind regards, Stefan Log excerpt: .... [ 27s] [[32m OK [0m] Started Reload Configuration from the Real Root. [ 27s] [[32m OK [0m] Reached target Initrd File Systems. [ 27s] [[32m OK [0m] Reached target Initrd Default Target. [ 28s] /.build/build-vm: line 235: syntax error near unexpected token `"$ARG"' [ 28s] /.build/build-vm: line 235: ` VM_NETOPT+=("$ARG")' [ 28s] /.build/build: line 671: vm_detect_2nd_stage: command not found [ 28s] no recipe files found in /. exit... [ 28s] [ 9.284601] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 28s] [ 9.284601] [ 28s] [ 9.285719] CPU: 0 PID: 1 Comm: build Not tainted 3.16.7-7-default #1 [ 28s] [ 9.286415] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.7.5.1-0-g8936dbb-20150318_003745-cloud117 04/01/2014 [ 28s] [ 9.287646] ffff88003c293ed8 ffffffff815ca6b2 ffffffff8180dad0 ffffffff815c5276 [ 28s] [ 9.288073] 0000000000000010 ffff88003c293ee8 ffff88003c293e88 ffffffff81135d12 [ 28s] [ 9.288073] 0000000000000100 ffff88003c28c4e8 0000000000000015 0000000000000001 [ 28s] [ 9.288073] Call Trace: [ 28s] [ 9.288073] [<ffffffff810050e6>] dump_trace+0x86/0x330 [ 28s] [ 9.288073] [<ffffffff81005424>] show_stack_log_lvl+0x94/0x170 [ 28s] [ 9.288073] [<ffffffff81006a81>] show_stack+0x21/0x50 [ 28s] [ 9.288073] [<ffffffff815ca6b2>] dump_stack+0x41/0x51 [ 28s] [ 9.288073] [<ffffffff815c5276>] panic+0xc8/0x1fc [ 28s] [ 9.288073] [<ffffffff8105e7ff>] do_exit+0xa4f/0xa50 [ 28s] [ 9.288073] [<ffffffff8105e879>] do_group_exit+0x39/0xa0 [ 28s] [ 9.288073] [<ffffffff8105e8f0>] SyS_exit_group+0x10/0x10 [ 28s] [ 9.288073] [<ffffffff815d3949>] ia32_do_call+0x13/0x13 [ 28s] [ 9.288073] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff) t created as /etc/bindresvport.blacklist.rpmnew -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 years, 11 months

[opensuse-buildservice] Resetting CI_CNT

by Olaf Hering

By accident I did a commit with 'Release: <largenumber>' in a rpm spec file. The prjconf has 'Release: <CI_CNT>.string.<B_CNT>', but that does most likely not matter. What happens now is that CI_CNT is now based on <largenumber> instead of the single digit checkin count of the pkg. How does one reset CI_CNT? Doing a new checkin with "Release: 1' does not help. Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 years, 11 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service July 2015