October 2016 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] RFC: provide reason why job may hang in state scheduled
by Marco Strigl 24 Oct '16

24 Oct '16

Hi, I have implemented a feature that can show if a job hangs in state scheduled because there are no workers with the capabilities to build the job (constraints not fulfilled). We have two cases: 1. No worker at all can fulfill the constraints. Then the following detailed string is displayed: "no worker provides the capabilities to comply with the constraints (constraint missmatch hint: hardware) (constraint missmatch hint: sandbox)" 2. There is no idle worker, but a worker that is building, away or down can build this job later. At the moment the detailed string for case 2 that is displayed in osc r -v and on the mouse-over-event at build.o.o is not very significant. It just shows how many out of all workers (that are not in idle state) could build this job. See [1] # osc r -v Application:Geo sfcgal -r openSUSE_Factory_ARM openSUSE_Factory_ARM aarch64 scheduled: 159/627 building openSUSE_Factory_ARM armv7l scheduled Which means: 159 out of 627 workers in state building could build this job if they change to idle. You see. Not very self-explanatory. I would change the string in something like this: "no idle workers found for constraints: (3 in state building) (1 in state away)" But i am not sure and don't want to change the string every time we deploy. Any suggestions? Thanks and regards, Marco [1] http://paste.opensuse.org/35759685 -- Marco Strigl SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuremberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 5

[opensuse-buildservice] Request-URI Too Large
by Adam Mizerski 22 Oct '16

22 Oct '16

Hi, I've made a SR (https://build.opensuse.org/request/show/436781) and there is a new thing I've never seen before: "1 package maintainer (show who)". When I click on the "show who" link nothing happens and if I open it in a new tab it shows me error 414 "Request-URI Too Large". The url under the link is quite big: http://susepaste.org/b47747a8 -- Adam Mizerski

2 1

[opensuse-buildservice] strange build error
by scalpel4k 22 Oct '16

22 Oct '16

Hi guys, for 2 weeks now, I get strange build errors in some of my packages. For instance the one below from https://build.opensuse.org/package/show/ home:scalpel4k/kde-now First, it complains about some files not being packaged, although they are not installed in BUILDROOT. Second, I can't find any %if macro that could be malformed as stated; even my project config is clean. What am I doing wrong? thx Michi >>> BUILD OUTPUT >>> [ 161s] Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/ abuild/rpmbuild/BUILDROOT/kde- now-2016.08.01git~20161017T194355~3b41834-18.1.x86_64 [ 161s] error: Installed (but unpackaged) file(s) found: [ 161s] /home/abuild/rpmbuild/BUILD/kde- now-2016.08.01git~20161017T194355~3b41834/build/src/KDENowCoreTargets- relwithdebinfo.cmake [ 161s] /home/abuild/rpmbuild/BUILD/kde- now-2016.08.01git~20161017T194355~3b41834/build/src/KDENowCoreTargets.cmake [ 161s] [ 161s] [ 161s] RPM build errors: [ 161s] Macro %if has illegal name (%define) [ 161s] Macro %endif has empty body [ 161s] Macro %if has illegal name (%define) [ 161s] Macro %endif has empty body [ 161s] Installed (but unpackaged) file(s) found: [ 161s] /home/abuild/rpmbuild/BUILD/kde- now-2016.08.01git~20161017T194355~3b41834/build/src/KDENowCoreTargets- relwithdebinfo.cmake [ 161s] /home/abuild/rpmbuild/BUILD/kde- now-2016.08.01git~20161017T194355~3b41834/build/src/KDENowCoreTargets.cmake [ 161s] error: Macro %if has illegal name (%define) [ 161s] error: Macro %endif has empty body [ 161s] error: Macro %if has illegal name (%define) [ 161s] error: Macro %endif has empty body [ 161s] [ 161s] lamb07 failed "build kde-now.spec" at Sat Oct 22 08:22:17 UTC 2016. [ 161s] [ 161s] ### WATCHDOG MARKER START ### -- 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] RFC: provide reason why job may hang in state scheduled
by Marco Strigl 21 Oct '16

21 Oct '16

Hi, I have implemented a feature that can show if a job hangs in state scheduled because there are no workers with the capabilities to build the job (constraints not fulfilled). We have two cases: 1. No worker at all can fulfill the constraints. Then the following detailed string is displayed: "no worker provides the capabilities to comply with the constraints (constraint missmatch hint: hardware) (constraint missmatch hint: sandbox)" 2. There is no idle worker, but a worker that is building, away or down can build this job later. At the moment the detailed string for case 2 that is displayed in osc r -v and on the mouse-over-event at build.o.o is not very significant. It just shows how many out of all workers (that are not in idle state) could build this job. See [1] # osc r -v Application:Geo sfcgal -r openSUSE_Factory_ARM openSUSE_Factory_ARM aarch64 scheduled: 159/627 building openSUSE_Factory_ARM armv7l scheduled Which means: 159 out of 627 workers in state building could build this job if they change to idle. You see. Not very self-explanatory. I would change the string in something like this: "no idle workers found for constraints: (3 in state building) (1 in state away)" But i am not sure and don't want to change the string every time we deploy. Any suggestions? Thanks and regards, Marco [1] http://paste.opensuse.org/35759685 -- Marco Strigl SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuremberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- 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] Ubuntu 16.10
by Martin Koegler 21 Oct '16

21 Oct '16

The project config links two times to 16.04: <path project="Ubuntu:16.04" repository="standard"/> 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 3

[opensuse-buildservice] Ubuntu 16.10 and Debian:Next
by Adrian Schröter 19 Oct '16

19 Oct '16

Two new base distributions are available Ubuntu 16.10, this is also available on the simple target list. Debian:Next can be used by advanced developers to build against debian testing distribution. -- Adrian Schroeter email: adrian(a)suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] scheduled packages are not build
by Hans-Peter Jansen 19 Oct '16

19 Oct '16

for ages, while there are plenty idle workers at the moment?! E.g. the virtualbox packages here: https://build.opensuse.org/project/monitor/home:frispete:Kernel-current Due to the update to 4.8.2, BS built the kernel packages yesterday, but the virtualbox packages are kept in scheduling state since then. OTOH, 500 workers are idle now. Any idea, why it behaves like this? TIA, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 7

Re: [opensuse-buildservice] Ubuntu 16.10 and Debian:Next
by Adrian Schröter 19 Oct '16

19 Oct '16

On Mittwoch, 19. Oktober 2016, 18:14:26 CEST wrote Geunsik Lim: > Do you mean that open-build-service supports officially Ubuntu 16.04 and > Debian:Next? yes > On Oct 19, 2016 6:09 PM, "Adrian Schröter" <adrian(a)suse.de> wrote: > > > Two new base distributions are available > > > > Ubuntu 16.10, this is also available on the simple target list. > > > > Debian:Next can be used by advanced developers to build > > against debian testing distribution. > > > > -- > > > > Adrian Schroeter > > email: adrian(a)suse.de > > > > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB > > 21284 (AG Nürnberg) > > > > Maxfeldstraße 5 > > 90409 Nürnberg > > Germany > > > > > > -- > > To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org > > To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org > > > > -- Adrian Schroeter email: adrian(a)suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- 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] OBS:Server:2.7 aarch64 packages
by Matwey V. Kornilov 19 Oct '16

19 Oct '16

Hello, Is it possible to add openSUSE:Factory:ARM aarch64 repository to OBS:Server:2.7 project? I would like to have obs-worker 2.7 for aarch64. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 8

[opensuse-buildservice] Getting osc to use Plasma5's kwalletd5?
by Johannes Kastl 15 Oct '16

15 Oct '16

Dear all, when I log into my Tumbleweed machine with Plasma5, I get asked for my kwallet password (ssh-add wants to unlock my ssh key and uses the password in kwallet). After that kwallet should be unlocked, I guess. But osc still keeps asking me for my kwallet password (via a kwallet unlock popup), and after using osc I have a kwalletmanager icon in the systray. So I guess it is using a different kwallet, maybe the one from kde4? Any way to tell osc which one to use? So I do not have to enter my password multiple times. Any hints are highly appreciated... Johannes

3 4