Closed furgo16 closed 4 days ago
I don't know how to get at the log file that it references, but I've re-triggered with debug logging enabled, so maybe that will tell us something.
And, no. No useful details, as far as I can tell: https://github.com/FreeCAD/FreeCAD-snap/actions/runs/11301166736/job/31451278645
Any idea how we can get our hands on the reference log file?
I'm thinking perhaps it needs to be uploaded as an artifact too to make it available in the UI?
Or perhaps an easier option would be to call snapcraft
from the workflow file with an option to be more verbose:
snapcraft --help
Usage:
snapcraft [help] <command>
Summary: Package, distribute, and update snaps for Linux and IoT
Global options:
-h, --help: Show this help message and exit
-v, --verbose: Show debug information and be more
verbose
-q, --quiet: Only show warnings and errors, not
progress
--verbosity: Set the verbosity level to 'quiet',
'brief', 'verbose', 'debug' or
'trace'
-V, --version: Show the application version and
exit
[...]
I'm testing doing both on my fork. I'll submit a PR once the builds in the fork finish and I can confirm it works.
Related PR: https://github.com/FreeCAD/FreeCAD-snap/pull/129
Thanks @chennes for the quick merge. We now have the log downloadable as an artifact after the build failure => https://github.com/FreeCAD/FreeCAD-snap/actions/runs/11337190566
Pending further analysis, and at a quick glance, it seems that for some reason during the snapcraft
execution the repositories are unexpectedly switched from jammy
(Ubuntu 22.04) to noble
(Ubuntu 24.04). Then when the elmer-csc-ubuntu:elmer-csc-ppa
is refreshed, the failure occurs, as it has no noble
packages.
The daily builds (see run #874 and #875) are currently failing since two days: https://github.com/FreeCAD/FreeCAD-snap/actions
The error in question is happening during
snapcraft build
:It's a strange one: if I understand it correctly, it would seem that snapcraft is not able to reach Ubuntu's apt server's (or KDE Neon's apt servers, where I believe the packages are being pulled from as per snapcraft.yaml). It would seem that there have not been recent changes in this repo to trigger this failure.
Another data point: on my fork I activated this workflow and it works, at least when manually triggered: https://github.com/furgo16/FreeCAD-snap/actions/runs/11301498114
Could perhaps an admin have a look, and potentially also trigger a manual workflow run? Thanks!