balena-io-experimental / balena-sound

Build a single or multi-room streamer for an existing audio device using a Raspberry Pi! Supports Bluetooth, Airplay and Spotify Connect
https://balena.io/blog/turn-your-old-speakers-or-hi-fi-into-bluetooth-receivers-using-only-a-raspberry-pi/
MIT License
2.39k stars 427 forks source link

Shows Status: Failed in Releases. Build Failed. Unable to deploy Balena Sound to fleet. #611

Closed RubixStars closed 1 year ago

RubixStars commented 1 year ago

Shows Status: Failed in Releases. Build Failed. Unable to deploy Balena Sound to fleet.

Steps to reproduce the behavior:

  1. Click on 1 click deploy button
  2. Deploy to a fleet containing raspberry pi 3
  3. Go to releases and wait.
  4. Shows Status: Failed

Expected for all services to run seamlessly

Screenshots image image image image

Device information

maggie44 commented 1 year ago

@andrewn may have an idea?

andrewn commented 1 year ago

Is there a reason why the Balena builder wouldn't be able to fetch https://github.com/rust-lang/crates.io-index?

I may be misunderstanding the cargo error though...

Step 10/17 : RUN cargo build     --release     --features alsa-backend,pulseaudio-backend     --verbose
 ---> Running in e2531cf3a38f

Updating
 crates.io index

error
:

failed to get `base64` as a dependency of package `librespot v0.4.2 (/app/librespot-src)`

Caused by:

  failed to fetch `https://github.com/rust-lang/crates.io-index`

Caused by:

  unexpected data at the end of the pack; class=Indexer (15)
andrewn commented 1 year ago

Running balena push gh_andrewn/balena-sound-master-andrewn

Fails with an out-of-memory error...

[spotify]           warning
[spotify]           :
[spotify]            spurious network error (2 tries remaining): failed to mmap. Could not write data: Out of memory; class=Os (2)
[spotify]
maggie44 commented 1 year ago

@RubixStars, are you using the standard Raspberry Pi 3 image, or the 64bit one? Does it fail on both?

andrewn commented 1 year ago

Can you try and build a new release? It should have been fixed in PR #613.

saveriogzz commented 1 year ago

I had the same issue and I confirm that the build now ends correctly. Thanks!