Mailinglist Archive: opensuse-buildservice (96 mails)

< Previous Next >
Re: [opensuse-buildservice] RFC: provide reason why job may hang in state scheduled
On 10/24/2016 05:51 PM, Greg Freemyer wrote:
On Mon, Oct 24, 2016 at 11:35 AM, Brüns, Stefan
<Stefan.Bruens@xxxxxxxxxxxxxx> wrote:
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)"
It is quite long IMHO. Imagine how this looks when you do an "osc r -v" on
your terminal. On the other side, it is self explaining :)

"No worker compliant with constraints. Mismatches: [hardware, sandbox]"

Hopefully it is a rare situation. Verbosity is not a bad thing in
rare error messages IMHO.

I think it is not very common. But if it happens the message should give the
user
a clue what went wrong.


But I find Stefan's verbiage both succinct and clear.


Yes. I like it too.

Greg

--
Greg Freemyer
Hillary says Trump is the only Republican she can beat, why should we
vote for him?
Evan McMullin is surging in the west of the Rockies
Deny Hillary, vote Evan McMullin for President


I will implement the following. Already checked in the version with "possible
workers", but
Stefan is right. Compliant sounds better. Will change it tomorrow morning.

For jobs that cannot be built on any worker:
"no compliant workers (constraints mismatch hint: hardware sandbox)"

And for jobs that could be built later:
"waiting for x compliant workers (y down)"

I will go with this at first.

Thanks for your thoughts,
Marco
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >