canonical / canonical/craft-application
test: CI backend needs to be system-specific
Open
- Dominant language
- Python
- Stars
- 14
- Forks
- 29
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 12
Description
### Bug Description
https://github.com/canonical/craft-application/commit/d4a3eb919867d94eaae7522c6f1cf658ee9557d8
### To Reproduce
https://github.com/canonical/craft-application/commit/d4a3eb919867d94eaae7522c6f1cf658ee9557d8
### part yaml
```shell
```
### Relevant log output
```shell
n/a
```
Contributor guide
Research direction
Start by reviewing commit d4a3eb919867d94eaae7522c6f1cf658ee9557d8 and the CI backend behavior it changed. Determine how the backend should become system-specific, then verify the resulting CI behavior on the affected systems; the issue provides no file or test path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100