-
Notifications
You must be signed in to change notification settings - Fork 48
Closed
Labels
Description
Describe the bug
Bob dev stops in its tracks with a critical errror, when a artifact is not found instead of just building it itself.
The error of no route to host seems also weird. It should be a File Not Found. But its made to look like a Network Error, which I dont think it is.
Steps to reproduce
- Have a layer/basement/default.yaml with
environment:
archiveAppend:
backend: http
name: [ci.bobbuildtool.dev](http://ci.bobbuildtool.dev/)
url: http://ci.bobbuildtool.dev/artifacts/
flags: [download]- bob dev some recipe
bob dev --verbose //package
** CHECKOUT: Layer 'basement' skipped (up to date)
** CHECKOUT: Layer 'basement-gnu-linux' skipped (up to date)
** CHECKOUT: Layer 'ada' skipped (up to date)
** CHECKOUT: Layer '[project]' skipped (up to date)
> [package path...]
MAP-SRC http://ci.bobbuildtool.dev/artifacts//b9/da/ba2c9bbd1b09e25a57d7d63976a07e4e23c6-1.buildid .. error
Build error: ci.bobbuildtool.dev: Cannot download file: [Errno 113] No route to host
Failed package: [package path...]
Backtrace
If applicable, add the backtrace here.
Context
- OS: Debian Bookworm
- Bob version 1.1.0
- Python version 3.11.2
- Proxy is set up correctly ;)
Repo:
Not yet public, might me able to share later