lpcraft run fails locally but succeeds on LP

Bug #1996733 reported by Adam Collard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lpci
Fix Released
Low
Jürgen Gmach

Bug Description

$ cat .launchpad.yaml ; echo EOF
---
pipeline:
  - lint

jobs:
  lint:
    series: jammy
    architectures: amd64
    packages: [git, tox]
    run: tox -e lint,mypy
EOF

on top of https://code.launchpad.net/~maas-committers/maas-ci/+git/system-tests/+ref/master

When running `lpcraft run` locally, i get the following log - https://pastebin.canonical.com/p/yhbtf6PyN6/

But when LP runs the job on the buildfarm it passes - https://code.launchpad.net/~adam-collard/maas-ci/+git/system-tests/+build/14232

Related branches

Revision history for this message
Adam Collard (adam-collard) wrote :

Think this was a "dirty" .tox which pointed to a python and a virtualenv that doesn't exist - by removing the `.tox` directory and re lpcrafting, the job succeeded

Changed in lpcraft:
status: New → Invalid
Revision history for this message
Jürgen Gmach (jugmac00) wrote :

Adam, as we do not intend to update the current design (for reasons specified in an upcoming MP), I'll update our documentation and point out to this issue.

Changed in lpcraft:
status: Invalid → In Progress
importance: Undecided → Low
assignee: nobody → Jürgen Gmach (jugmac00)
Jürgen Gmach (jugmac00)
Changed in lpcraft:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.