busybox demo test fails in yakkety with x1/busybox.test: No such file or directory

Bug #1623621 reported by Leo Arias
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Fix Released
High
Leo Arias

Bug Description

======================================================================
ERROR: demos_tests.test_busybox.BusyBoxTestCase.test_busybox
----------------------------------------------------------------------
output: {{{b'touch: x1/busybox.test: No such file or directory\n'}}}

Traceback (most recent call last):
  File "/tmp/adt-run.vdw3UB/build.MsX/real-tree/snaps_tests/demos_tests/test_busybox.py", line 33, in test_busybox
    '')
  File "/tmp/adt-run.vdw3UB/build.MsX/real-tree/snaps_tests/__init__.py", line 236, in assert_command_in_snappy_testbed
    output = self.run_command_in_snappy_testbed(command, cwd)
  File "/tmp/adt-run.vdw3UB/build.MsX/real-tree/snaps_tests/__init__.py", line 248, in run_command_in_snappy_testbed
    return self.snappy_testbed.run_command(command, cwd)
  File "/tmp/adt-run.vdw3UB/build.MsX/real-tree/snaps_tests/testbed.py", line 52, in run_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 '/snap/bin/busybox.touch ~/snap/busybox/$(ls ~/snap/busybox)/busybox.test' returned non-zero exit status 1

This error is caused because now a common directory is created next to the x1 directory.

Tags: tests
Revision history for this message
Leo Arias (elopio) wrote :
Changed in snapcraft:
milestone: none → 2.18
status: In Progress → Fix Committed
Changed in snapcraft:
status: Fix Committed → 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.