Comment 1 for bug 2068633

https://autopkgtest.ubuntu.com/packages/t/tgt/oracular/armhf shows that the only tests that have been run for tgt/armhf in oracular all have trigger migration-reference/0. This is because packages that had previously been uploaded during the *noble* cycle had triggered the tests, which failed starting 2024-04-18, the same day the tgt armhf binaries were removed.

I think it's unlikely that there is a bug here in britney triggering tests for architectures it's not supposed to. I think what likely happened here is:
- britney triggered tests while the tgt binaries were still present
- the tgt binaries were removed while the above tests were in the queue
- the tests ran and failed with the specific behavior of failing to find the package

So this isn't a britney bug per se, just a race.

Subsequently, there are knock-on britney behaviors which I think are bugs:
- having collected the failing test result, britney apparently never notices that it's no longer relevant because of the architecture binaries having disappeared
- britney was excessively retriggering migration-reference/0 tests for this failed test, because the results that came back were insufficient? https://autopkgtest.ubuntu.com/packages/t/tgt/noble/armhf (but this also seems not to have happened in oracular, where the baseline retest was triggered only once)