[zorg] r214540 - Fixed mergefunc builder configure; added lldb builder for FreeBSD.

Hi all,

Before you move them, can you explain what experimental means?

The Linux builder does have some flakey builds and I’m working on that right now.

I’m one test away from getting OSX green. I would like to see how it does.

We are doing a bringup on the android builder right now, it makes sense to move that somewhere else.

Also, it would be very much appreciated to include lldb-dev when discussing lldb issues.

Thanks,

Vince

Hi all,

Before you move them, can you explain what experimental means?

The significant thing to be, according to Galina, is that such a buildbot
won't send fail-mail to everyone on the blame list when it fails.

The Linux builder does have some flakey builds and I'm working on that
right now.

I'm one test away from getting OSX green. I would like to see how it does.

Seems fine - but I'd be happy to have it in experimental first, you can fix
it, wait to see a consistently good non-flaky behavior, then move it over.

Hi Vince,

Maybe “experimental” is not the best word to name the group. Anyway, the actual meaning is a group of builders which does not send e-mail notifications to the blame list on a failure after a green or interrupted build.
These builders are shown in the UI as usual, though, on the waterfall page they are at the right. The IRC notifications are sent on every builder status change.
The builders of this group builds on demand only.
I think this is not a desired behavior in this case. We still want these builders to build on regular commits to the dependent projects, I guess. This is an easy change. I’ll make it as well.

Originally, the purpose of this group is just like that - someone introduce a new builder, work out all possible issues and make it reliably green, before it gets to a pool of regular builders and gets noisy.

The major issue with an unreliable builder is people get annoyed and stop pay attention to the failures. It would take quite an effort to get the situation back to normal.

Thanks

Galina

Hi Vince,

Maybe "experimental" is not the best word to name the group. Anyway, the
actual meaning is a group of builders which does not send e-mail
notifications to the blame list on a failure after a green or interrupted
build.
These builders are shown in the UI as usual, though, on the waterfall page
they are at the right. The IRC notifications are sent on every builder
status change.
The builders of this group builds on demand only.
I think this is not a desired behavior in this case. We still want these
builders to build on regular commits to the dependent projects, I guess.
This is an easy change. I'll make it as well.

Thanks, that'd be great - could we disable IRC notification for these
buildbots as well?

Originally, the purpose of this group is just like that - someone
introduce a new builder, work out all possible issues and make it reliably
green, before it gets to a pool of regular builders and gets noisy.
The major issue with an unreliable builder is people get annoyed and stop
pay attention to the failures. It would take quite an effort to get the
situation back to normal.

Indeed - the greater risk is people start ignoring other, valid buildbot
email from reliable builders because it gets lost in the noise of the
unreliable ones. That's why I'd be happy to aggressively mark as
experimental (or any other approach) any buildbot that's producing
particularly unhelpful notifications (email or IRC) or otherwise clouding
the feedback these tools should be providing.

If someone is willing to put up with an unreliable builder and triage the
failures manually - they can always forward the real failures to the
mailing list, cc'ing whoever's appropriate, etc. But it shouldn't be every
developer's job to figure out whether any bot email is valid or not.

- David

Agreed - thanks for taking care of that.

Hi David,

I agree that it needs to be fixed. Thanks for communicating the issue.

I’ve submitted a change that XFAILs timeout tests. This should make lldb-x86_64-ubuntu-14.04-cmake solid (fingers crossed).

Will our rotations alias still get failure emails like it does now?

Vince

Hi David,

I agree that it needs to be fixed. Thanks for communicating the issue.

I've submitted a change that XFAILs timeout tests. This should make
lldb-x86_64-ubuntu-14.04-cmake solid (fingers crossed).

Will our rotations alias still get failure emails like it does now?

Galina should be able to answer this - I'm not sure on the exact setup, but
that seems like a reasonable/right configuration. The main/only thing I
care about is not notifying random contributors (or the IRC channel, which
is equivalent) on a bot that's not pretty reliable (granted, my GDB 7.5
buildbot has some flaky tests in it that come up once a week or so - and I
wouldn't mind being held to this bar myself, I've meant/tried to disable
those at various points but never quite pushed through)

- David

Will our rotations alias still get failure emails like it does now?

Galina should be able to answer this

What is the “rotations alias”?

could we disable IRC notification for these buildbots as well?

I will disable IRC notifications for experimental bots today, if everything will go well.

Thanks

Galina

>> Will our rotations alias still get failure emails like it does now?
...
> Galina should be able to answer this

What is the "rotations alias"?

From the buildbot perspective it is an additional e-mail address where it

sends a notification for each failed build (based on
an InformativeMailNotifier in buildbot/osuosl/master/config/status.py:125).
It is a special e-mail address what will forward the failure notification
to the right people inside the LLDB team at Google based on some settings
but it isn't effect the way the buildbot have to handle it.

Small note, you can control emails sent by builder.

For example, I did not include my experimental builders in the email notification.

By the same token, you could add a custom notifier for any experimental builder that you individually want to watch without going to a web site.

The remaining problem is that the experimental builder failures appear on lab.llvm.org:8011.

Rick

InformativeMailNotifier(
fromaddr = , sendToInterestedUsers= False, extraRecipients = [,], subject=“Build %(builder)s Failure”, mode = “failing”, b addLogs=False, num_lines = 15),

Thanks for clarifying this, Tamas.

Vince,

Yes, this notifier is still active and works as before.
So, your rotations alias still get failure emails.

Thanks

Galina