An issue had been found lately on swatbot, where the last reported builds show incoherent data: builds started in 2021 on the old autobuilder (typhoon) and with an end date in 2025. After some investigations, it appeared the issue is builds are stored in swatbot using the buildbot buildid as an identifier, but this buildid is only unique across a single buildbot controller. As a consequence, if a build running on buildbot has the same buildid as an older build already stored in swatbot, the old data in swatbot will be partly replaced, leading to a corrupt build description. Swatbot has been put offline as a preventive action, to avoid further corruption of the builds data. Now we must think about how swatbot can be fixed, so data of new builds are no longer merged with old builds. Two possibilities arise so far: - Adding a new field to swatbot build and buildcollection tables, allowing to store an identifier of the buildbot controller instance the builds come from. This will require to update all existing entries with the correct buildbot instance. - Removing all entries coming from typhoon and only keep entries from valkyrie. We will probably still need to implement the additional field with controller identifier, to be safe if we ever introduce another buildbot controller, but this can be done with less urgency. Once swatbot is fixed, missing builds will have to be imported: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14316
I've moved swatbot to a new VM and updated to the newest django 4.2 LTS release. I added 2,000,000,000,000 to all typhoon builds which avoid the collision problem for a few million years. It would be cleaner to modify the software to track cluster names but this works for now.If we ever add another cluster though we will get collisions in approximately 12,000 builds. I've re-enabled swatbot submissions on valkyrie. We are ready to insert the missing data from between 2025-07-10 07:07:48 and now.
Mathieu has restored the rest of the missing data.