June 2015 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Buildinfo timeout issue on api.o.o
by Marcus Hüwe 23 Jun '15

23 Jun '15

Hi, when posting a "larger" file to the _buildinfo route on api.o.o I get a strange timeout error: marcus@linux:~> dd if=/dev/zero of=./foo bs=1 count=250K 256000+0 records in 256000+0 records out 256000 bytes (256 kB) copied, 0.444089 s, 576 kB/s marcus@linux:~> curl -u Marcus_H -H "Content-Type: application/octet-stream" \ -X POST -T foo \ https://api.opensuse.org/build/openSUSE:Tools/FOO/BAR/_repository/_buildinfo Enter host password for user 'Marcus_H': <status code="timeout_error"> <summary>Timeout::Error</summary> </status> marcus@linux:~> A "smaller" file works as expected: marcus@linux:~> dd if=/dev/zero of=./foo bs=1 count=50K 51200+0 records in 51200+0 records out 51200 bytes (51 kB) copied, 0.0936674 s, 547 kB/s marcus@linux:~> curl -u Marcus_H -H "Content-Type: application/octet-stream" \ -X POST -T foo \ https://api.opensuse.org/build/openSUSE:Tools/FOO/BAR/_repository/_buildinfo Enter host password for user 'Marcus_H': <status code="not_found"> <summary><status code="404"> <summary>project 'openSUSE:Tools' has no repository 'FOO'</summary> <details>404 project 'openSUSE:Tools' has no repository 'FOO'</details> </status> </summary> </status> marcus@linux:~> I suspect there occurs an error when the api tries to contact the srcserver, but the Timeout::Error hides the actual exception (see Suse::Backend.put_or_post in lib/opensuse/backend.rb). Currently, I'm not able to reproduce this with a local instance (using git master). Any ideas? Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] wipebinary options ignored
by Olaf Hering 20 Jun '15

20 Jun '15

After the switch to gcc5 most packages succeeded in packman. But a few got into failure state. Either due to the new compiler, or due to packman being unable to reach OBS. So I tried to retrigger just the few failures, and wipe also stale packages. But the result is that appearently everything was wiped, such as fdupes which certainly succeeded. Is my command line wrong? I dont have access to the server side, so no idea what acutally happend there. "osc help wipebinaries" suggests that the command should wipe packages which are in a certain state, instead of implying --all. for p in Essentials Extra Multimedia Games do for r in openSUSE_Tumbleweed Factory do for a in x86_64 i586 do echo $p $r $a pbs wipebinaries \ --unresolvable \ --broken \ --build-failed \ --build-disabled \ -r $r -a $a $p done done done Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Build service broken?
by Mathias Homann 19 Jun '15

19 Jun '15

Hi, I just noticed, the dispatcher is down on back_main, and there is hardly any building going on... What's up? Cheers MH -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 6

[opensuse-buildservice] osc buildinfo vs. actual build job
by Andreas Schwab 18 Jun '15

18 Jun '15

Why does osc buildinfo give a different result than what the actual build job uses? Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] front end "search" down for anyone else... it's been days...
by Bahi, David 18 Jun '15

18 Jun '15

https://build.opensuse.org/search 500: Internal Server Error

2 1

[opensuse-buildservice] Popular branches, moving them to "official" repos
by Stanislav Baiduzhyi 17 Jun '15

17 Jun '15

I wonder if anyone tried to run some analytics about the most popular branches on OBS. I'm running into following situation pretty often: 1. Search for opera 29 or mc with enabled fish. 2. Install from the most reponsible source (the latest up-to-date version and properly modified description). 3. Wait for 1-2 month, when you'll have new machine or HDD or VM to install openSUSE again. 4. Check the repo from point 2 - often repo or package does not exist any more. Goto step 1. So if there was some kind of analytics over the branches, maybe the most popular of them could be moved to official repositories, not ones hosted under 'home:/'. That probably will free some OBS resources as well, and eliminate the need of "if you want something done - do it yourself". -- Regards, Stas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 8

[opensuse-buildservice] %gcc_version
by Andreas Schwab 17 Jun '15

17 Jun '15

%gcc_version in oS:Factory should be defined to 5, not 50. Also, the following line should be added: Prefer: libffi4-gcc%{gcc_version} libffi-devel-gcc%{gcc_version}. Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Strange OBS notification
by Martin Koegler 17 Jun '15

17 Jun '15

OBS has sent a build failure mail, but the build logs looks sucessful and the web-ui shows no error: ----- Forwarded message from OBS Notification <obs-email(a)opensuse.org> ----- Date: Tue, 16 Jun 2015 20:41:20 +0200 From: OBS Notification <obs-email(a)opensuse.org> Subject: Build failure of home:e9925248:grandorgue/grandorgue in openSUSE_Factory_ARM/armv7l Visit https://build.opensuse.org/package/live_build_log/home:e9925248:grandorgue/… Package home:e9925248:grandorgue/grandorgue failed to build in openSUSE_Factory_ARM/armv7l Check out the package for editing: osc checkout home:e9925248:grandorgue grandorgue Last lines of build log: [ 3975s] comparing filelist [ 3975s] comparing file checksum [ 3975s] creating rename script [ 3975s] RPM meta information is identical [ 3975s] comparing /.build.oldpackages/rpmlint.log and /home/abuild/rpmbuild/OTHER/rpmlint.log [ 3975s] ... saving statistics [ 3975s] ... saving built packages [ 3975s] RPMS/armv7hl/grandorgue-debuginfo-0.3.1.1921-114.2.armv7hl.rpm [ 3975s] RPMS/armv7hl/grandorgue-0.3.1.1921-114.2.armv7hl.rpm [ 3975s] RPMS/noarch/grandorgue-demo-0.3.1.1921-114.2.noarch.rpm [ 3975s] SRPMS/grandorgue-0.3.1.1921-114.2.src.rpm [ 3975s] OTHER/_statistics [ 3975s] OTHER/rpmlint.log [ 3975s] OTHER/grandorgue-appdata.xml [ 3975s] [ 3975s] armbuild19 finished "build grandorgue.spec" at Tue Jun 16 15:38:15 UTC 2015. [ 3975s] [ 3975s] ### WATCHDOG MARKER START ### [ 3978s] [ 3957.261062] SysRq : Power Off [ 3978s] [ 3957.262922] reboot: Power down [ 3979s] ### WATCHDOG MARKER END ### [ 3979s] build: extracting built packages... [ 3980s] RPMS/armv7hl/grandorgue-debuginfo-0.3.1.1921-114.2.armv7hl.rpm [ 3980s] RPMS/armv7hl/grandorgue-0.3.1.1921-114.2.armv7hl.rpm [ 3980s] RPMS/noarch/grandorgue-demo-0.3.1.1921-114.2.noarch.rpm [ 3980s] SRPMS/grandorgue-0.3.1.1921-114.2.src.rpm [ 3980s] OTHER/_statistics [ 3980s] OTHER/rpmlint.log [ 3980s] OTHER/grandorgue-appdata.xml ----- End forwarded message ----- Regards, Martin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Question about a bit of logic in bs_publish
by Andrew Davidoff 12 Jun '15

12 Jun '15

Hi, >From bs_publish: my $starttime = time(); if ($publish_lasttime{$prp} && $publish_duration{$prp} > 300 && $publish_lasttime{$prp} + 5 * $publish_duration{$prp} > $starttime) { print "$prp: not yet\n"; $publish_retry{$event} = $starttime + 60 * 5; next; } If I am reading this correctly, it means that If the last publish for this project/repo ($prp) took over 5 minutes, and 5 times that duration from the end of the last publish is in the future, wait 5 minutes before doing the pending publish. If I'm not just reading this incorrectly, what was the reasoning behind this? Thanks. Andy -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Ask for the "editors" project maintainers
by Kyrill Detinov 11 Jun '15

11 Jun '15

Hello. Is anybody around? https://build.opensuse.org/project/requests/editors -- WBR Kyrill

1 1