Ignoring binary build outcomes violates user expectations

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/06/2010 09:21 PM, Mackenzie Morgan wrote:
> Public bug reported:
>
> I just set up a daily recipe. The following pages claim success on lucid:
> https://code.edge.launchpad.net/~gally-dev/+recipe/daily
> https://code.edge.launchpad.net/~gally-dev/+recipe/daily/+build/219

These pages are reporting the success/failure of the source package build.

> However, this page says it failed:
> https://code.edge.launchpad.net/~gally-dev/+archive/daily/+build/1856564

This page is reporting the success/failure of the binary package build.

The meaning of "success" on the first two pages is simply narrower than
you were expecting.

One source package build can produce multiple binary package builds,
whose final outcomes may vary. So it would be impossible to combine the
result of the sourcepackagerecipe build with the result of the binary
package builds, and produce a single success/failure value.

We could consider displaying the binary build outcomes *in addition* to
the source build outcomes.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkw0fRcACgkQ0F+nu1YWqI1RCgCfdgGveyqSSxSWI2dBHNwTy45C
80UAn0aScF76aEKyBiKq6aEzu5iz8V3J
=VL7z
-----END PGP SIGNATURE-----

Setting to high because this should be done before removing beta.

Fixed in stable r12000 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/12000>.

Thanks for fixing this! It makes navigating recipe builds so much easier.