* Dimstar / Dominique Leuenberger [2014-11-12 10:47]:

On Wed, 2014-11-12 at 10:43 +0100, Guido Berhoerster wrote:

...

* Dimstar / Dominique Leuenberger [2014-11-11 22:34]:

...

As apparently some maintainers are not aware of their packages failing in openSUSE:Factory (openSUSE Tumbleweed), I implemented a quick script today that finds all the current failures and sends a notification to the maintainer(s) (as defined in the metadata, same info as osc maintainer gives) in the hope that the maintainers will realize this.

The notification is sent out after the package failed for 7 days. If there is already a submit request pending to Factory (which hopefully fixes the issue), the notification is suppressed (the staging process can sometimes take longer, and I think it would be annoying to be reminded in this case).

The message looks like the one below.

Feel free to let me know your thoughts about this; if you think it's useful or not. The aim, of course, is to get Tumbleweed in the best possible shape for our users.

I think it's useful but could you add some additional headers so that it's possible to distinguish these notifications from personal mails and to filter them more easily? In particular - Precedence: bulk - X-Mailer: something unique Thanks,

Hi Guido,

Thanks for the hint. I'll add this in the next run.

I hope this won't result though in people just filtering it out to /dev/null: then I can as well ust skip the mails :)

Actually in all seriousness, I think it's to the contrary, if I wouldn't filter the tons of bulk mail I get from lists, notification systems etc. into seperate mailboxes I'd simply overlook the more important stuff. Above headers allow easy filtering into the same mailbox where notifications from OBS, Hermes, and Coolo's reminder mails go which ensures I notice them. And the mails are only useful for those who are not aware of build failures, those who didn't care before probably won't care even after you send them mail. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, 2014-11-12 at 10:52 +0100, Jan Engelhardt wrote:

On Tuesday 2014-11-11 22:33, Dimstar / Dominique Leuenberger wrote:

...

As apparently some maintainers are not aware of their packages failing in openSUSE:Factory (openSUSE Tumbleweed), I implemented a quick script today that finds all the current failures and sends a notification to the maintainer(s)

But was there not already some mechanism in OBS that would do this on its own? Why the sudden need for an external script?

Yes, OBS does have notifications for package failures; but as they are 'for each failure' people tend to disable them (as they can be many and intermittent). The parser I wrote only takes into account packages failing for longer periods, taking 'random' occurrences away. The need is simple: there are packages failing for a long time (current top ranked: 77 days, but submitted, 2nd 66 days, even failing in the devel prj); if they stay like this, I will simply file delete requests; which in turn will have people complain that it's gone and we all know how those discussions end. So the idea is to: - After 1 week: Send a mail to the maintainers - After 1 more week: Send a reminder to the maintainers - After 1 more week: Send a mail to -factory asking for people to actively step up if they care for the package - After 1 more week: file a delete request Of course there CAN be valid reasons why something is failing, and this would be taken into account. Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wednesday 2014-11-12 11:12, Andreas Schwab wrote:

Dimstar / Dominique Leuenberger writes:

...

Yes, OBS does have notifications for package failures; but as they are 'for each failure' people tend to disable them (as they can be many and intermittent).

It won't work for Factory anyway, since there is no bugowner defined.

Then perhaps something should be defined. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 12.11.2014 11:12, Andreas Schwab wrote:

Dimstar / Dominique Leuenberger writes:

...

Yes, OBS does have notifications for package failures; but as they are 'for each failure' people tend to disable them (as they can be many and intermittent).

It won't work for Factory anyway, since there is no bugowner defined.

The "source_maintainer" role in OBS' notification system is about maintainers (of devel package). It should work also for Factory - but I never tried it actually as it will cause too much mail for me. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 12.11.2014 14:33, Andreas Schwab wrote:

Stephan Kulow writes:

...

The "source_maintainer" role in OBS' notification system is about maintainers (of devel package).

Where is that documented?

In the code Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 12.11.2014 14:36, Andreas Schwab wrote:

Stephan Kulow writes:

...

The "source_maintainer" role in OBS' notification system is about maintainers (of devel package).

There is no source_maintainer role for notification of build failures.

That might be the problem Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hi, On Wed, Nov 12, 2014 at 11:02:32AM +0100, Dimstar / Dominique Leuenberger wrote:

On Wed, 2014-11-12 at 10:52 +0100, Jan Engelhardt wrote:

...

On Tuesday 2014-11-11 22:33, Dimstar / Dominique Leuenberger wrote:

...

As apparently some maintainers are not aware of their packages failing in openSUSE:Factory (openSUSE Tumbleweed), I implemented a quick script today that finds all the current failures and sends a notification to the maintainer(s)

But was there not already some mechanism in OBS that would do this on its own? Why the sudden need for an external script?

Yes, OBS does have notifications for package failures; but as they are 'for each failure' people tend to disable them (as they can be many and intermittent). The parser I wrote only takes into account packages failing for longer periods, taking 'random' occurrences away.

Perhaps to improve the existing notifications by adding ...

The need is simple: there are packages failing for a long time (current top ranked: 77 days, but submitted, 2nd 66 days, even failing in the devel prj); if they stay like this, I will simply file delete requests; which in turn will have people complain that it's gone and we all know how those discussions end.

So the idea is to: - After 1 week: Send a mail to the maintainers - After 1 more week: Send a reminder to the maintainers - After 1 more week: Send a mail to -factory asking for people to actively step up if they care for the package - After 1 more week: file a delete request

... these options? Or is that for some reason impossible? Cheers, Dejan

Of course there CAN be valid reasons why something is failing, and this would be taken into account.

Cheers, Dominique

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org