Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Release to Candidate does not work with adopt-info #47

Open
pedro-avalos opened this issue Oct 30, 2024 · 1 comment
Open

[Bug]: Release to Candidate does not work with adopt-info #47

pedro-avalos opened this issue Oct 30, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@pedro-avalos
Copy link

What happened?

The Release to Candidate action failed to find the snapped package after the remote build finished because the version information was purposefully blank/null (using adopt-info for the version metadata). The workflow could not find the .snap file because the version was null instead of the version that was adopted at build-time.

What should have happened?

Perhaps the workflow should accept any <name>_*_<arch>.snap or even <name>_*.snap file as a valid output of the remote build.

Output of snap info $snap_name

n/a

Output of snap connections $snap_name

n/a

Output of snap version

n/a

Relevant log output

[...]
Creating snap package...
Packed gpu-burn_9aefd7c_amd64.snap
[...]
Revoking proxy token...
[...]
Could not find gpu-burn_null_amd64.snap

Teminal output of app

No response

@pedro-avalos pedro-avalos added the bug Something isn't working label Oct 30, 2024
@pedro-avalos
Copy link
Author

Ah, I just saw there is a PR for this #46

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant