← Back to issue list

Launchpad builds failing today

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1807141
Type
issue
State
closed
Author
~ceejay-7
Labels
—
Created
Updated
Closed

Current evaluation

No snapcraft change involved: cjwatson reported builds on Launchpad were passing again (failure was "/bin/ping" missing, likely transient), advising drop of unsupported ppc64el/s390x; bug later auto-expired by ~janitor for 60 days inactivity.

Resolution: closed stale

Reason: No fixing PR or commit exists in the snapcraft repo; maintainer ~cjwatson (2019-01-23) reported the same snap's Launchpad builds were now succeeding, and the bug was closed by ~janitor (2019-03-25) with "[Expired for Snapcraft because there has been no activity for 60 days.]" after the reporter stopped responding.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Today all my builds are failing for some reason... All with ... Sorry, an error occurred in Snapcraft: We would appreciate it if you created a bug report at https://launchpad.net/snapcraft/+filebug with the above text included. so here they are... https://build.snapcraft.io/user/dceejay/nodered.snap/397716 ..5 ..7 ..8

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed stale No snapcraft change involved: cjwatson reported builds on Launchpad were passing again (failure was "/bin/ping" missing, likely transient), advising drop of unsupported ppc64el/s390x; bug later auto-expired by ~janitor for 60 days inactivity.
stealth/space-bunny-alpha — closed stale Recent Launchpad builds were fine except on unsupported ppc64el and s390x architectures; the issue later expired after 60 days without activity.
stealth/space-bunny-alpha — closed stale Launchpad Node-RED builds were reported failing with a generic Snapcraft error, but no diagnosis, fix, or follow-up was documented.
stealth/space-bunny-alpha — closed stale Launchpad Snapcraft build failures were closed with no documented fix or maintainer explanation after years of inactivity.
qwen/qwen3.6-35b-a3b — — Launchpad build failures reported by an external contributor were closed without discussion or resolution. No fix was implemented, and the report appears abandoned.
qwen/qwen3.6-35b-a3b — — Closed without comments. The reported Launchpad and Snapcraft build failures were resolved externally or abandoned, as the issue stems from an upstream build service rather than repository code.
qwen/qwen3.6-35b-a3b — — Closed without comments or resolution. The reported transient Launchpad build failures were likely resolved externally or abandoned.
qwen3.6-35b-a3b-mtp-q6 — — Closed as abandoned. The reported transient Launchpad build failures received no comments or fixes, indicating an external resolution or stale report.

Update history

Date Change
created

Related issues

Issue Project State Summary Similarity
#4821 remote build: hangs when logging into Launchpad snapcraft closed Partly mitigated by Launchpad retries in craft-application; the CI login hang was closed as unsupported, with snapcraft.io recommended for CI builds.
73%
#2099923 Snapcraft builds are failing: install of snap "snapcraft" failed snapcraft (launchpad) open Reported Launchpad Bionic non-i386 builds cannot install Snapcraft 7.x/stable because core20 needs snapd 2.61; the issue remains open, untriaged, and unanswered.
71%