698964 - update_from_files doesn't find new builders until 2nd reconfig

Status: RESOLVED INCOMPLETE

(Release Engineering :: General, defect, P3)

Description

[Mike Taylor [:bear]]

For bug 697470 I changed the chunking of jsreftest from 2 to 3 and also made crashtest have 2 chunks.  The initial reconfig, and a subsequent one later in the day, did not cause the .../builder file to be created for jsreftest-3

Nick said this in bug 697470's comment:

>Going by the log for the job that inserts the finished jobs into the statusdb >(test-master01:~cltbld/update.log) there have been no crashtest-[1,2] or >jsreftest-3 inserted at all. Hence nothing in builds-4hr.js.gz.

Comment 1

[Chris AtLee [:catlee]]

The problem here is that buildbot doesn't create builder files on disk for new builders until the 2nd reconfig. update_from_files (which inserts items into the database) requires these builder files to work, and so jobs for the new builders don't end up in the database, and therefore don't show up on tbpl.

Comment 2

[Chris Cooper [:coop] (he/him)]

So the workaround for now is a double reconfig, at least on the master(s) where you need the new builder to show up?

Comment 3

[Chris AtLee [:catlee]]

(In reply to Chris Cooper [:coop] from comment #2)
> So the workaround for now is a double reconfig, at least on the master(s)
> where you need the new builder to show up?

correct. the problem is that buildduty often isn't aware that new builders are expected.

Comment 4

[Mike Taylor [:bear]]

resolving as INCOMPLETE because these bugs are most likely not even being worked on or known about anymore

Comment 5

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

At some point update_from_files.py got deprecated in favour of catlee's queue based system for log uploading, status db update and pulsing.