lpcraft fails to pass output files between jobs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lpci |
Invalid
|
High
|
Jürgen Gmach |
Bug Description
I have recently been attempting to get lpcraft to perform a build and pass its build output to a new job using the `input` section. However, I am unable to successfully run this command. Instead, the `build` stage runs, and then I see the following error:
```
$ lpcraft run --clean --output out
....<snipped>...
Requested input from 'build', but more than one job with that name was previously executed and produced output artifacts.
Full execution log: '/home/
```
In addition to the above error, this also leaves the lxd container around, despite running lpcraft with `--clean`:
$ lxc list --project lpcraft
+------
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+------
| lpcraft-
+------
If I delete the container, the problem simply occurs again and the container does not get deleted.
Here is the `.launchpad.yaml` I am using:
jobs:
build:
series: focal
architectures: amd64
environment:
TOX_
no_proxy: localhost
output:
paths:
- dist/*.whl
- dist/*.tar.gz
packages:
- python3-dev
- python3-pip
- python3-venv
- git
- ffmpeg
run: |-
python3 -m pip install --user --upgrade --upgrade-
python3 -m build .
test:
series: focal
architectures: amd64
environment:
TOX_
no_proxy: localhost
input:
job-name: build
target-
packages:
- python3-dev
- python3-pip
- python3-venv
- git
- git-lfs # Tests
run: |-
export PIP_EXTRA_
# First test seems to be inconsistent + second is deprecated"
python3 -m pytest -sv ./tests/
pipeline:
- build
- test
Cannot reproduce the issue on my setup.
I do experience another issue as soon as I use the `clean` flag, see https:/ /bugs.launchpad .net/lpcraft/ +bug/1986374
Dan mentioned he is rebasing Colin's release command branch onto main.