[opensuse-buildservice] new repository / scheduler states
Hi, You see new states in the web interface now for entire repostories. A more detailed documentation can be found here: http://lizards.opensuse.org/2010/01/11/obs-reports-scheduling-state-now/ Unfortunatly, I missed a corner case which let the schedulers die on build.opensuse.org. They are currently restarting, but you know that this takes a while :/ The positive aspect is that you see now with the new code that the state is about to be reprocessed when you for example upload new sources. You see this in the webinterface, the state is mentioned to be "outdated". So you know that it will happen and do not to speculate if there is maybe a bug ;) have fun adrian -- 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
On 01/11/2010 02:47 PM, Adrian Schröter wrote:
Hi,
You see new states in the web interface now for entire repostories. A more detailed documentation can be found here:
http://lizards.opensuse.org/2010/01/11/obs-reports-scheduling-state-now/
Unfortunatly, I missed a corner case which let the schedulers die on build.opensuse.org. They are currently restarting, but you know that this takes a while :/
The positive aspect is that you see now with the new code that the state is about to be reprocessed when you for example upload new sources. You see this in the webinterface, the state is mentioned to be "outdated". So you know that it will happen and do not to speculate if there is maybe a bug ;)
have fun adrian
Thanks very much for letting us know whats happening, I was wondering what "succeeded (rescheduling)" was. Regards Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Montag, 11. Januar 2010 14:03:08 schrieb Dave Plater:
On 01/11/2010 02:47 PM, Adrian Schröter wrote:
Hi,
You see new states in the web interface now for entire repostories. A more detailed documentation can be found here:
http://lizards.opensuse.org/2010/01/11/obs-reports-scheduling-state-now/
Unfortunatly, I missed a corner case which let the schedulers die on build.opensuse.org. They are currently restarting, but you know that this takes a while :/
The positive aspect is that you see now with the new code that the state is about to be reprocessed when you for example upload new sources. You see this in the webinterface, the state is mentioned to be "outdated". So you know that it will happen and do not to speculate if there is maybe a bug ;)
have fun adrian
Thanks very much for letting us know whats happening, I was wondering what "succeeded (rescheduling)" was.
Hm, I will rename the "rescheduling" to "outdated" I think to have the same wording as on project page. Or has anyway a better word for reflecting the "dirty" status ? bye adrian -- 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
On 01/11/2010 03:41 PM, Adrian Schröter wrote:
Am Montag, 11. Januar 2010 14:03:08 schrieb Dave Plater:
On 01/11/2010 02:47 PM, Adrian Schröter wrote:
Hi,
You see new states in the web interface now for entire repostories. A more detailed documentation can be found here:
http://lizards.opensuse.org/2010/01/11/obs-reports-scheduling-state-now/
Unfortunatly, I missed a corner case which let the schedulers die on build.opensuse.org. They are currently restarting, but you know that this takes a while :/
The positive aspect is that you see now with the new code that the state is about to be reprocessed when you for example upload new sources. You see this in the webinterface, the state is mentioned to be "outdated". So you know that it will happen and do not to speculate if there is maybe a bug ;)
have fun adrian
Thanks very much for letting us know whats happening, I was wondering what "succeeded (rescheduling)" was.
Hm, I will rename the "rescheduling" to "outdated" I think to have the same wording as on project page.
Or has anyway a better word for reflecting the "dirty" status ?
bye adrian
I think "outdated" or even "dirty" explains the situation better. Regards Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 01/11/2010 04:06 PM, Dave Plater wrote:
On 01/11/2010 03:41 PM, Adrian Schröter wrote:
Am Montag, 11. Januar 2010 14:03:08 schrieb Dave Plater:
On 01/11/2010 02:47 PM, Adrian Schröter wrote:
Hi,
You see new states in the web interface now for entire repostories. A more detailed documentation can be found here:
http://lizards.opensuse.org/2010/01/11/obs-reports-scheduling-state-now/
Unfortunatly, I missed a corner case which let the schedulers die on build.opensuse.org. They are currently restarting, but you know that this takes a while :/
The positive aspect is that you see now with the new code that the state is about to be reprocessed when you for example upload new sources. You see this in the webinterface, the state is mentioned to be "outdated". So you know that it will happen and do not to speculate if there is maybe a bug ;)
have fun adrian
Thanks very much for letting us know whats happening, I was wondering what "succeeded (rescheduling)" was.
Hm, I will rename the "rescheduling" to "outdated" I think to have the same wording as on project page.
Or has anyway a better word for reflecting the "dirty" status ?
bye adrian
I think "outdated" or even "dirty" explains the situation better. Regards Dave P
Ok I now understand the meaning of "(rescheduling)" it should be "(Please Wait)" Regards Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 01/11/2010 03:41 PM, Adrian Schröter wrote:
Am Montag, 11. Januar 2010 14:03:08 schrieb Dave Plater:
On 01/11/2010 02:47 PM, Adrian Schröter wrote:
Hi,
You see new states in the web interface now for entire repostories. A more detailed documentation can be found here:
http://lizards.opensuse.org/2010/01/11/obs-reports-scheduling-state-now/
Unfortunatly, I missed a corner case which let the schedulers die on build.opensuse.org. They are currently restarting, but you know that this takes a while :/
The positive aspect is that you see now with the new code that the state is about to be reprocessed when you for example upload new sources. You see this in the webinterface, the state is mentioned to be "outdated". So you know that it will happen and do not to speculate if there is maybe a bug ;)
have fun adrian
Thanks very much for letting us know whats happening, I was wondering what "succeeded (rescheduling)" was.
Hm, I will rename the "rescheduling" to "outdated" I think to have the same wording as on project page.
Or has anyway a better word for reflecting the "dirty" status ?
bye adrian
Is "(rescheduling)" supposed to be permanently visible or is it supposed to indicate something. It seems to be permanently displayed on home:plater ghostscript-library regardless of what is happening. home:plater lilypond has most of the builds disabled and have displayed "disabled (rescheduling)" for a while now. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Adrian Schröter
-
Dave Plater