686238 - builds-4hr json for mozilla-inbound shows a Win64 talos run, but no build

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Phil Ringnalda (:philor)]

If you look at https://tbpl.mozilla.org/?tree=Mozilla-Inbound&usebuildbot=1&rev=870d1be89bcd you'll see a Win64 talos chrome run (apparently shutting off tests on non-mozilla-central missed chrome), but you won't see the build. I looked at builds-4hr.js.gz a couple of hours afterward, and didn't see any sign of it there, so I think tbpl isn't showing it because nothing other than Tinderbox (https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=870d1be89bcd&noignore=1 does show it) ever heard that it happened at all.

Comment 1

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

In
  https://build.mozilla.org/buildapi/self-serve/mozilla-inbound/rev/870d1be89bcd
I see a
 WINNT 6.1 x86-64 mozilla-inbound build
to go with  the
 Rev3 WINNT 6.1 x64 mozilla-inbound talos chrome
That's derived from buildbot's schedulerdb, while builds-4hrs.js.gz comes from the statusdb. Investigating ...

Comment 2

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

Strangely, there are no jobs for the builder 'mozilla-inbound-win64' in the statusdb, when there are for other branches (eg  m-c, build-system, try). And there are 56 jobs completed for 'WINNT 6.1 x86-64 mozilla-inbound build' on buildbot-master12 alone.

The script importing the jobs to the db is
 http://hg.mozilla.org/build/buildbotcustom/file/default/bin/update_from_files.py
Nothing obvious in there that I can see.

Comment 3

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

So buildbot-master12 has 880 builder directories, and only 865 of them contain a builder file (which the importer wants to read). The 15 missing the file are:
  accessibility-win64
  accessibility-win64-nightly
  devtools-win64
  devtools-win64-nightly
  jaegermonkey-win64
  jaegermonkey-win64-nightly
  mozilla-aurora-win64
  mozilla-aurora-win64-nightly
  mozilla-beta-win64
  mozilla-inbound-win64
  mozilla-inbound-win64-nightly
  tracemonkey-win64
  tracemonkey-win64-nightly
  ux-win64
  ux-win64-nightly
Smells like a reconfig that went wrong.

catlee/bhearsum - graceful restart on the master, and then touch the \d+ files in each of those dirs so they get imported ?

Comment 4

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

catlee pointed out (in IRL, OMG) that the builder files aren't created for new builders when you first add them, but on the next reconfig. So I've done that for buildbot-master12 and used touch on the NN files so that they get imported. I'll check if the other three 3 build masters need the same treatment.

Comment 5

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

buildbot07, 08, and 13 all had the correct number of builders so I didn't take any action on them.