625354 - Test jobs should have changeset information since the beginning

Status: RESOLVED DUPLICATE of bug 564178

(Release Engineering :: General, defect)

Description

[Armen [:armenzg]]

Yesterday few hundred test jobs went red but they did not show on tbpl because the changeset is unknown until we unpack and query the info from the binary files.

I don't know what is the right way (add info to sendchange or schedulerDB) but it would have allowed people to tell us earlier that something was going wrong.

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

Not sure I follow. We include the revision in the sendchange, and that's available in JSON for running/pending jobs. TBPL is using that data. 

Are you saying that it assigns finished builds differently ? Still scraping tinderbox so that we have TinderboxPrint the revision as the first step). Or the builds-*.js.gz doesn't contain the revision if we fail early ? (because it's a property set in a later step).

Comment 2

[Armen [:armenzg]]

After we download the build we run the step "get build info" which prints this:
> buildid: 20110113045435
> TinderboxPrint:<a href=http://hg.mozilla.org/mozilla-central/rev/70d10ef482f3 title="Built from revision 70d10ef482f3">rev:70d10ef482f3</a>

If we have the revision before we download the build we could TinderboxPrint as early as we can.

TBPL was unable to show red test jobs as we never reached the "get build info" step.

That is why only philor saw it at tinderbox.m.o

Comment 3

[Chris AtLee [:catlee]]

I think this is about printing out the changeset at the beginning of the run...which sounds a lot like bug 564178.