buildbot step detail useful?

Chris AtLee

unread,

Dec 9, 2011, 7:05:02 AM12/9/11

to tools...@lists.mozilla.org

Does anybody use the per-step messages that we're currently generating? I imagine we could cut down the # of messages by at least 10x if we didn't send messages when steps started and stopped.

Chris AtLee

unread,

Dec 9, 2011, 2:33:11 PM12/9/11

to tools...@lists.mozilla.org

silence is consent. I'm going to turn off pulse messages for buildbot steps.

https://bugzilla.mozilla.org/show_bug.cgi?id=709229

_______________________________________________
tools-pulse mailing list
tools...@lists.mozilla.org
https://lists.mozilla.org/listinfo/tools-pulse

Axel Hecht

unread,

Dec 9, 2011, 3:26:43 PM12/9/11

to

Silence over a few hours hardly is.

I don't consider pulse to be in a state where people do production work
with it, tbh. Which makes it much harder to evaluate if data is useful
or not.

Axel

Al Billings

unread,

Dec 9, 2011, 4:38:09 PM12/9/11

to Axel Hecht, tools...@lists.mozilla.org

QA has been using it for our test runs but whenever it dies, it means we
have to reset 20+ machines right now so it isn't convenient for us if it
isn't reliable.

Al

Jonathan Griffin

unread,

Dec 9, 2011, 7:29:41 PM12/9/11

to Chris AtLee, tools...@lists.mozilla.org

OrangeFactor actually uses these messages, and turning them off will break it. Back when OF started using pulse, there ONLY seemed to be step message from buildbot; are there other messages OF now could use instead?

Jonathan

Chris AtLee

unread,

Dec 9, 2011, 11:00:32 PM12/9/11

to Jonathan Griffin, tools...@lists.mozilla.org

Hm, I don't think that was ever the case. We've always generated build start/stop events as well as step start/stop events.

To be clear, the per-step data will still be included in the build.X.Y.finished messages, like below, we just won't be sending individual events when the steps begin and end. Were you using the individual build.X.Y.step.N.started/finished events?

{
"payload": {
"build": {
"slave": "talos-r4-snow-075",
"builderName": "Rev4 MacOSX Snow Leopard 10.6 mozilla-aurora opt test mochitest-other",
"text": [
"build",
"successful",
"slave",
"lost"
],
"number": 52,
"currentStep": null,
"results": 0,
"blame": [
"sendchange-unittest"
],
"reason": "scheduler",
"eta": null,
"steps": [
{
"statistics": {},
"name": "get_buildername",
"isFinished": true,
"text": [
"get_buildername"
],
"results": [
0,
[]
],
"isStarted": true,
"times": [
1323488109.7448881,
1323488109.7456779
],
"eta": null,
"urls": {},
"step_number": 0,
"expectations": []
},
{
"statistics": {},
"name": "tinderboxprint_buildername",
"isFinished": true,
"text": [
"tinderboxprint_buildername"
],
"results": [
0,
[]
],
"isStarted": true,
"times": [
1323488109.7461729,
1323488109.746835
],
"eta": null,
"urls": {},
"step_number": 1,
"expectations": []
},

Jonathan Griffin

unread,

Dec 10, 2011, 6:20:12 PM12/10/11

to Chris AtLee, tools...@lists.mozilla.org

Hey Chris,

I had been using the step events; I hadn't realized there were build stop/start events. I'll update OF to use those as soon as pulse is back up.

Chris AtLee

unread,

Dec 12, 2011, 9:21:36 AM12/12/11

to Jonathan Griffin, tools...@lists.mozilla.org

Great!

Sorry for the short notice on this. We can look at turning them back on
once pulse is more stable. In the meanwhile, I think this will
drastically reduce the load on pulse.

Jonathan Griffin

unread,

Dec 22, 2011, 1:02:37 PM12/22/11

to Chris AtLee, tools...@lists.mozilla.org

FYI, the step messages are still being published for android builds.

Jonathan