← Back to issue list

test_libpipeline example fails with /snaps/bin/pipelinetest.pipelinetest: No such file or directory

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1560254
Type
issue
State
closed
Author
~snappy-m-o
Labels
—
Created
Updated
Closed

Current evaluation

Ubuntu Core changed the libpipeline executable name; the test was fixed in canonical/snapcraft#389, merged as 26715f38d (implementation 238febdf7).

Resolution: closed resolved

Reason: canonical/snapcraft#389 updated the libpipeline example test for Ubuntu Core's new binary name. It was merged as commit 26715f38d, with implementation commit 238febdf7.

Evaluated by: mr-cal-bot

No scores available.

Issue body

The recent changes in ubuntu-core (edge, not yet released to stable) break the libpipeline example: _StringException: ssh output: {{{b'bash: /snaps/bin/pipelinetest.pipelinetest: No such file or directory\n'}}} Traceback (most recent call last): File "/home/jenkins-slave/workspace/github-snapcraft-examples-tests-cloud/examples_tests/test_libpipeline.py", line 32, in test_libpipeline '/snaps/bin/pipelinetest.pipelinetest', expected) File "/home/jenkins-slave/workspace/github-snapcraft-examples-tests-cloud/examples_tests/__init__.py", line 164, in assert_command_in_snappy_testbed output = self._run_command_in_snappy_testbed(command) File "/home/jenkins-slave/workspace/github-snapcraft-examples-tests-cloud/examples_tests/__init__.py", line 169, in _run_command_in_snappy_testbed return self.snappy_testbed.run_command(command) File "/home/jenkins-slave/workspace/github-snapcraft-examples-tests-cloud/examples_tests/testbed.py", line 68, in run_command ssh_command, stderr=subprocess.STDOUT).decode('utf-8') File "/usr/lib/python3.5/subprocess.py", line 626, in check_output **kwargs).stdout File "/usr/lib/python3.5/subprocess.py", line 708, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '['ssh', '-l', 'ubuntu', '-p', '22', '10.42.62.33', '-o', 'UserKnownHostsFile=/dev/null', '-o', 'StrictHostKeyChecking=no', '-o', 'LogLevel=error', '/snaps/bin/pipelinetest.pipelinetest']' returned non-zero exit status 127

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Ubuntu Core changed the libpipeline executable name; the test was fixed in canonical/snapcraft#389, merged as 26715f38d (implementation 238febdf7).
stealth/space-bunny-alpha — closed resolved Fixed by canonical/snapcraft#389, merged as 26715f38d (implementation 238febdf7), updating the libpipeline test for Ubuntu Core's new binary name and resolving LP #1560254.
stealth/space-bunny-alpha — closed stale The ubuntu-core compatibility report was closed without a recorded fix or explanation after more than 3,800 days of inactivity.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The test_libpipeline CI failure from missing snap binary paths after ubuntu-core updates was abandoned due to outdated test infrastructure and zero activity.
qwen/qwen3.6-35b-a3b — — Abandoned. Closed without resolution due to inactivity. The CI test failure for the libpipeline example was not addressed, likely superseded by updated test paths.

Update history

Date Change
created

Related work

  • Likely Fixed By: canonical/snapcraft#389 (confidence 100%)

    The merged PR updated the test's expected executable name and resolved LP #1560254.

Related issues

Issue Project State Summary Similarity
#1554637 libpipeline example fails because it is now run in an empty dir snapcraft (launchpad) closed Updated the libpipeline example test to expect empty output in the new working directory; merged in snapcraft#368 via commit 0eb3337dc.
76%
#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.
74%