libpipeline example fails because it is now run in an empty dir
Bug #1554637 reported by
Leo Arias
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Fix Released
|
High
|
Leo Arias | ||
Bug Description
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.
Revision history for this message
| Leo Arias (elopio) wrote | #1 |
| Changed in snapcraft: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Leo Arias (elopio) |
Revision history for this message
| Leo Arias (elopio) wrote | #2 |
| Changed in snapcraft: | |
| milestone: | none → next |
| Changed in snapcraft: | |
| milestone: | next → 2.4 |
| status: | In Progress → Fix Committed |
| Changed in snapcraft: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm going to update the expected result of the test to go back to green. But I'm also opening a new bug so we revisit this example.