Emails about snapcraft remote build failures contain invalid log reference

[Sebastien Bacher]

I just triggered some snapcraft remote test builds which failed, launchpad emailed me about the failure but the log isn't available

example

'[Snap build #1372318] amd64 build of snapcraft-gnome-system-monitor-132e2f snap package in ubuntu focal-updates
...
 * Build Log: https://launchpad.net/~seb128/+snap/snapcraft-gnome-system-monitor-132e2f/+build/1372318/+files/buildlog_snap_ubuntu_focal_amd64_snapcraft-gnome-system-monitor-132e2f_BUILDING.txt.gz'

but opening the url gives a 'Lost something?' webpage. The log has been downloaded locally by the snapcraft command as gnome-system-monitor_amd64.txt.

I did another build which had the same issue, so it's not a one off error. The

[Colin Watson (cjwatson)]

This is because "snapcraft remote-build" removes the snap after it's finished building it, by design to save space; but the failed-build machinery doesn't know that it's going to do that.

My understanding was that "snapcraft remote-build" would show you the failed build log on the console, if any. Can you confirm that it did so? If so, it's just a matter of working out how to suppress the extra emails.

[Sebastien Bacher (seb128)]

> My understanding was that "snapcraft remote-build" would show you the failed build log on the console, if any. Can you confirm that it did so?

Yes, that's what I meant in the description when I wrote 'The log has been downloaded locally by the snapcraft command as gnome-system-monitor_amd64.txt.', the log file is stored in the directory the snapcraft remote-build was called from.

Remove the extra mails should be enough

[Colin Watson (cjwatson)]

Ah yes, thanks. Perhaps we could add a flag to Snap.requestBuilds or similar to suppress failure emails, and "snapcraft remote-build" could pass it.

[hideou aoi (aoilinux)]

Any progress? Its really annoying...