[opensuse-buildservice] rebuild not triggered?
Hi, https://build.opensuse.org/package/live_build_log?arch=i586&package=acx&proj... shows a failed build log from Wed Feb 25 11:14:52 UTC 2009 and the package has status failed in repository home:michal-m:kill-symsets/test. I fixed the bug in the kernel-source package in home:michal-m:kill-symsets:changes (the home:michal-m:kill-symsets/test repository is configured to use packages from here), both kernel-source and kernel-syms rebuilt successfully yesterday evening: https://build.opensuse.org/package/live_build_log?arch=i586&package=kernel-s... but the acx package (and any other kmp in the project) was not rebuilt since then. It's not even in the "scheduled" state. https://build.opensuse.org/monitor shows that Factory is rebuilding, but does this mean that the scheduler needs more than 16 hours to notice changes? Or did it miss the kernel-syms rebuilt due to my project configuration (kernel-syms and kernel-source are also in the home:michal-m:kill-symsets project, but disabled for the test repository)? Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Michal, you speak here about changed binary packages in one repo, triggering a build in another repo. These kind of changes are currently handled as "low priority" and can indeed take very long to get detected with our current load. Source changes get handled with highest prio, finished builds with medium prio. There are times that the service has even hard times to keep up with the source changes (Imagine, it needs to run a dependeny solving based on full installation with requires and build requires. This is harder than run a package solver in an installed system. And that needs to be done for each event ...). I want to have the current scheduler load on the web in future. And also a "dirty" flag for repos, so that the frontend can tell you that the server knows that this repo needs to be evaluated. As a workaround, you can trigger a rebuild for any of these packages, it will create a high prio event to evaluate this repo. bye adrian Am Donnerstag, 26. Februar 2009 10:53:04 schrieb Michal Marek:
Hi,
https://build.opensuse.org/package/live_build_log?arch=i586&package=acx&pro ject=home%3Amichal-m%3Akill-symsets&repository=test
shows a failed build log from Wed Feb 25 11:14:52 UTC 2009 and the package has status failed in repository home:michal-m:kill-symsets/test. I fixed the bug in the kernel-source package in home:michal-m:kill-symsets:changes (the home:michal-m:kill-symsets/test repository is configured to use packages from here), both kernel-source and kernel-syms rebuilt successfully yesterday evening:
https://build.opensuse.org/package/live_build_log?arch=i586&package=kernel- syms&project=home%3Amichal-m%3Akill-symsets%3Achanges&repository=openSUSE_11 .1
but the acx package (and any other kmp in the project) was not rebuilt since then. It's not even in the "scheduled" state. https://build.opensuse.org/monitor shows that Factory is rebuilding, but does this mean that the scheduler needs more than 16 hours to notice changes? Or did it miss the kernel-syms rebuilt due to my project configuration (kernel-syms and kernel-source are also in the home:michal-m:kill-symsets project, but disabled for the test repository)?
Michal
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian Schröter napsal(a):
you speak here about changed binary packages in one repo, triggering a build in another repo.
These kind of changes are currently handled as "low priority" and can indeed take very long to get detected with our current load.
Thanks, that makes sense to me.
As a workaround, you can trigger a rebuild for any of these packages, it will create a high prio event to evaluate this repo.
OK, maybe I will. The build is currently "low priority" for me as well :), I was just curious if I hit a build service bug. Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Adrian Schröter
-
Michal Marek