Delay "contains outdated Ubuntu packages" warning email for builds in progress

Bug #1832319 reported by Stuart Langridge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snap Store Server
Confirmed
Undecided
Unassigned
review-tools
Confirmed
Wishlist
Unassigned

Bug Description

Yesterday I initiated a build of a snap of mine on build.snapcraft.io. All the builds completed apart from s390, which was still queued up. Overnight, I received a warning email saying that the snap "contains outdated Ubuntu packages", on s390. This morning, 12 hours later, the s390 build completed, which will presumably have obviated that error. There is no problem with the s390 builds taking longer to do (presumably there are fewer build machines for that architecture), but it would be nice if I wasn't warned about a problem when there may be a build in-flight which will fix it, especially since as far as I'm aware there's no way to confirm that my enew build does actually fix that problem (there's no "please scan this build for outdated Ubuntu packages" button anywhere).

Revision history for this message
Mike Royal (maos20008) wrote :

I've had similar issues with this too.

Revision history for this message
Daniel Manrique (roadmr) wrote :

Not straightforward to do for now, because the scanner runs as a process that doesn't have information about in-progress builds.

Changed in snapstore:
status: New → Confirmed
importance: Undecided → Wishlist
Daniel Manrique (roadmr)
affects: snapstore → review-tools
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Like Daniel said, this can't really be fixed atm, but I also wonder if the behavior is actually correct. At the time the check was made, s390x was in fact out of date. The fact that a build was happening doesn't necessarily mean that build is going to have the fix anyway. Eg, build starts, USN is published while build is happening. In this case, you'll only be warned that the build is outdated on the next run.

Adding back a snapstore task since this might require work on both sides.

Changed in snapstore:
status: New → Confirmed
Revision history for this message
Stuart Langridge (sil) wrote :

Understood that maybe it's theoretically correct but there is only one action I can take to rectify it, which is "press the button to start a new build", and I've already done that. Sending me an email complaining about a thing I can't fix and indeed have already fixed and now I'm waiting on your build daemon to prove it is just going to annoy people, even if the email is technically correct in what it says :-)

(Note: obviously this is different if I'm not using build.snapcraft.io, but you know whether I am or not.)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.