list-plugins integration test is broken when run in adt

Bug #1596112 reported by Sergio Schvezov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Critical
Leo Arias

Bug Description

======================================================================
FAIL: test_list_plugins (test_list_plugins.ListPluginsTestCase)
test_list_plugins.ListPluginsTestCase.test_list_plugins
----------------------------------------------------------------------
testtools.testresult.real._StringException: Traceback (most recent call last):
  File "/tmp/adt-run.1qGfm6/build.Rmd/real-tree/integration_tests/test_list_plugins.py", line 28, in test_list_plugins
    self.assertEqual(expected, output)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 350, in assertEqual
    self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 435, in assertThat
    raise mismatch_error
testtools.matchers._impl.MismatchError: !=:
reference = '''\
ant cmake gulp kernel nil python3 tar-content
autotools copy jdk make nodejs qmake
catkin go kbuild maven python2 scons
'''
actual = '''\
ant catkin copy gulp kbuild make nil python2 qmake tar-content
autotools cmake go jdk kernel maven nodejs python3 scons
'''

[Impact]

 * A failed test in autopkg will block the release.

 * This problem started in master but wasn't released to the distro.

[Test Case]

 * Run the integration suite.

[Regression Potential]

 * None. This affects only the test, the feature is correct. If the test doesn't start passing, the release will be blocked.

Revision history for this message
Sergio Schvezov (sergiusens) wrote :
summary: - list-plugins integration test is broken
+ list-plugins integration test is broken when run in adt
Revision history for this message
Sergio Schvezov (sergiusens) wrote :
Changed in snapcraft:
status: Triaged → Fix Committed
assignee: nobody → Leo Arias (elopio)
Leo Arias (elopio)
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Sergio, or anyone else affected,

Accepted snapcraft into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/snapcraft/2.12 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed
Revision history for this message
Leo Arias (elopio) wrote :

There is nothing to verify in xenial-proposed, so I'm marking this as verified.

Thanks Steve!

tags: added: verification-done
removed: verification-needed
Changed in snapcraft:
status: Fix Committed → Fix Released
Revision history for this message
Chris J Arges (arges) wrote : Update Released

The verification of the Stable Release Update for snapcraft has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Mathew Hodson (mhodson)
no longer affects: Ubuntu Xenial
no longer affects: Ubuntu Yakkety
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers