Ignoring binary build outcomes violates user expectations

Bug #602508 reported by Mackenzie Morgan on 2010-07-07
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Tim Penhey

Bug Description

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

However, this page says it failed:
https://code.edge.launchpad.net/~gally-dev/+archive/daily/+build/1856564
This page is reachable by clicking "i386 build..." on the second "success" page listed above.
This page agrees:
https://code.launchpad.net/~gally-dev/+archive/daily/+packages

Related branches

tags: added: recipe

-----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-----

Aaron Bentley (abentley) on 2010-07-07
summary: - Some pages report build success when it really failed
+ Ignoring binary build outcomes violates user expectations
Changed in launchpad-code:
importance: Undecided → Medium
status: New → Triaged
Tim Penhey (thumper) wrote :

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

tags: added: confusing-ui
Changed in launchpad-code:
importance: Medium → High
Tim Penhey (thumper) on 2010-11-08
Changed in launchpad-code:
status: Triaged → In Progress
assignee: nobody → Tim Penhey (thumper)
Changed in launchpad-code:
milestone: none → 10.12
tags: added: qa-needstesting
Changed in launchpad-code:
status: In Progress → Fix Committed
Tim Penhey (thumper) on 2010-11-30
tags: added: qa-ok
removed: qa-needstesting
Jelmer Vernooij (jelmer) wrote :

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

Curtis Hovey (sinzui) on 2010-12-08
Changed in launchpad-code:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers