libpipeline example fails because it is now run in an empty dir
Metadata
Current evaluation
Updated the libpipeline example test to expect empty output in the new working directory; merged in snapcraft#368 via commit 0eb3337dc.
Resolution: closed resolved
Reason: PR #368 adjusted the expected test output and was merged as f4f02c0d2 with implementation commit 0eb3337dc, restoring the test suite to green.
Evaluated by: mr-cal-bot
No scores available.
Issue body
our libpipeline example executes a ls | grep c. Previously it was run in the snap directory, which made it print two lines. After [1] it is being run in and empty directory, which makes ls return nothing, obviously.
[1] https://github.com/ubuntu-core/snappy/pull/589
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Updated the libpipeline example test to expect empty output in the new working directory; merged in snapcraft#368 via commit 0eb3337dc. | |
| stealth/space-bunny-alpha | — | closed resolved | The libpipeline example test was fixed by expecting empty output in the new working directory; canonical/snapcraft#368 merged as commit 0eb3337dc. | |
| stealth/space-bunny-alpha | — | closed resolved | Updated the libpipeline example test to expect empty ls output in an empty working directory; merged via canonical/snapcraft#368 (commit 0eb3337dc). | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The libpipeline example fails when run in an empty directory instead of the snap directory, causing ls to return no output. No fix or follow-up was provided. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. PR #589 changed execution to an empty directory, breaking the libpipeline example. No fix or discussion was recorded, indicating the report was abandoned. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcraft#368
(confidence 100%)
Merged change updating the libpipeline test for execution in an empty directory.
-
Caused By:
snappy#589
(confidence 99%)
The issue identifies this PR as the change that moved example execution into an empty directory.
-
Related To:
snapcraft (launchpad)#1554641
(confidence 95%)
Follow-up issue opened to reconsider the example's behavior separately from the failing test.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1554641 libpipeline example needs to be reviewed | snapcraft (launchpad) | closed | The libpipeline example test was updated by ubuntu-core/snapcraft#368, merged as f4f02c0d2, to handle the empty working directory and grep behavior. | |
| #368 examples_tests: update the expected result of the libpipeline test | snapcraft | merged | Merged in canonical/snapcraft#368 via 0eb3337dc; the libpipeline example test now expects empty ls output when the snap runs in an empty working directory. | |
| #1550108 libpipeline example will fail when skiping the install | snapcraft (launchpad) | closed | Fixed by merged snapcraft PR #341 (merge commit 509011969), which skips the libpipeline output assertion when installation is skipped. | |
| #1560254 test_libpipeline example fails with /snaps/bin/pipelinetest.pipelinetest: No such file or directory | snapcraft (launchpad) | closed | Ubuntu Core changed the libpipeline executable name; the test was fixed in canonical/snapcraft#389, merged as 26715f38d (implementation 238febdf7). | |
| #387 libpipeline example test: update the binary name | snapcraft | closed | Closed unmerged in favor of rebased #389, which merged the libpipeline binary-name test update via commit 238febdf7. | |
| #326 examples_tests: fix the libpipeline test. | snapcraft | merged | Merged PR #326 as commit 8611ef560, refactoring example tests into independent files and fixing the libpipeline test for LP #1546771. |