SourcePackageRecipeBuild:+index LocationError build

There are appear to be three builds that are building, but do not have build queue records. I think this should be an impossibility. Other pages do not assume that the buildqueue_record exists, but sourcepackagerecipebuild-index.pt does for this case. Fixing the template to avoid the case is trivial, but I suspect something is else is wrong. These three source package recipe builds are not BUILDING, the status is wrong.

-- source package recipe builds that are currently building, but are
-- not in the build queue...shouldn't this be impossible.
SELECT sprb.id, sprb.recipe, sprb.package_build, pb.archive, bfj.*
FROM
    SourcePackageRecipeBuild sprb
    JOIN PackageBuild pb ON sprb.package_build = pb.id
    JOIN buildfarmjob bfj ON pb.build_farm_job = bfj.id
    LEFT JOIN SourcePackageRecipeBuildJob sprbj
        ON sprbj.sourcepackage_recipe_build = sprb.id
    LEFT JOIN BuildQueue bq ON sprbj.job = bq.job
WHERE
    bfj.status = 6
    AND bq.id IS NULL
;

   id | recipe | package_build | archive | id | processor | virtualized | date_created | date_started | date_finished | date_first_dispatched | builder | status | log | job_type | failure_count
--------+--------+---------------+---------+---------+-----------+-------------+----------------------------+----------------------------+----------------------------+----------------------------+---------+--------+-----------+----------+---------------
 313796 | 1381 | 4168429 | 24522 | 4195986 | | t | 2012-09-25 21:30:17.362718 | 2012-09-26 01:18:46.619776 | 2012-09-26 01:22:49.685661 | 2012-09-26 01:18:46.619776 | 28 | 6 | 117342577 | 3 | 0
 306575 | 2426 | 4092077 | 28986 | 4118914 | | t | 2012-09-13 21:45:15.396141 | 2012-09-14 01:39:14.201798 | 2012-09-14 01:42:31.287629 | 2012-09-14 01:39:14.201798 | 48 | 6 | 115866517 | 3 | 0
 339948 | 3168 | 4299322 | 25596 | 4329103 | | t | 2012-11-06 17:45:13.837404 | 2012-11-06 19:20:51.690196 | 2012-11-06 19:23:38.150159 | 2012-11-06 19:20:51.690196 | 36 | 6 | 122195218 | 3 | 0

The "~rbose-vcs-imports/xboard/master recipe build" 's job has the wrong status. (the item in the previous list from 2012-11-06) There were networking issue on that day is it appears that the job finished, but the communication to update the status failed.

We don't know how the first two items in the list got in the bad state. We can fix the status of all three source package recipe builds.

Three SourcePackageRecipeBuild builds claim to be building, but they are not.
They do not have a builder, and we can see that they finished. The absense
of a SourcePackageRelease indicates all three builds failed. The times
of the failure relate to networking/firewall issues.

The log id can be used to hack the log url:
1 is Failed by deps https://launchpadlibrarian.net/117342577/buildlog.txt.gz
2 is Failed by bzr https://launchpadlibrarian.net/115866517/buildlog.txt.gz
3 is Failed by bzr https://launchpadlibrarian.net/122195218/buildlog.txt.gz

-- source package recipe builds that are currently building, but are
-- not in the build queue...shouldn't this be impossible.
SELECT
    sprb.id AS sprb, sprb.package_build, pb.archive,
    bfj.date_started, bfj.date_finished, bfj.status, bfj.log,
    spr.version, spr.upload_archive
FROM
    SourcePackageRecipeBuild sprb
    JOIN PackageBuild pb ON sprb.package_build = pb.id
    JOIN buildfarmjob bfj ON pb.build_farm_job = bfj.id
    LEFT JOIN SourcePackageRecipeBuildJob sprbj
        ON sprbj.sourcepackage_recipe_build = sprb.id
    LEFT JOIN BuildQueue bq ON sprbj.job = bq.job
    LEFT JOIN SourcePackageRelease spr
        ON spr.sourcepackage_recipe_build = sprb.id
WHERE
    bfj.status = 6
    AND bq.id IS NULL
;

  sprb | package_build | archive | date_started | date_finished | status | log | version | upload_archive
--------+---------------+---------+----------------------------+----------------------------+--------+-----------+---------+----------------
 313796 | 4168429 | 24522 | 2012-09-26 01:18:46.619776 | 2012-09-26 01:22:49.685661 | 6 | 117342577 | |
 306575 | 4092077 | 28986 | 2012-09-14 01:39:14.201798 | 2012-09-14 01:42:31.287629 | 6 | 115866517 | |
 339948 | 4299322 | 25596 | 2012-11-06 19:20:51.690196 | 2012-11-06 19:23:38.150159 | 6 | 122195218 | |
(3 rows)

I think this SQL will fix the 3 broken builds: https://pastebin.canonical.com/80263/