[Buildbot-devel] Odd behavior in web after changing list of targets

[Diane Maple]

Hello,

Does the order in which builders are created and added of target matter?

I don't recall seeing this issue before.  I have implemented a somewhat automated system such that the buildbot master configurations load a YAML file per master which defines the targets, etc and I have a common master.cfg script which processes the YAML file.

I have been using this system with 0.8.8 for a few weeks now.
When a new change is made to the YAML version of the configuration and checked into source control a buildbot master checks out the configs, validates the yaml, validates the configuration against the master it is for and then uses the "buildbot restart --clean" to enable using the configuration.

The configuration was changed today, the order of the targets changed and some were added.
After the restart the master appears to have a large gap in the build history for the targets which existed from before the change.
As in when I view the page for a given target it should have the last 4 or so builds listed.  None are listed.

Was there a change from 0.8.7p1 to 0.8.8 with regards to how the data is stored in the database?

Also, the web view keeps seeming like it is out of sync with reality of builds.
The web may show no active builds and yet the twistd.log file shows a build is going.
Also, the grid view doesn't always appear to render properly vs the waterfall view.

Forcing the web browser to reload does not appear to solve the problem.

Are there any reported problems or things being worked on which could be the cause of these odd issues?

Thank you.