← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1589752] Re: unit tests in IsDirtyTestCase fail when executed in a platform that's not amd64

 

** Changed in: snapcraft
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1589752

Title:
  unit tests in IsDirtyTestCase fail when executed in a platform that's
  not amd64

Status in Snapcraft:
  Fix Released
Status in snapcraft package in Ubuntu:
  New
Status in snapcraft source package in Xenial:
  Fix Released
Status in snapcraft source package in Yakkety:
  New

Bug description:
  The TestCase sets the project options architecture to amd64, so when
  it is run in a different architecture it will fail.

  ======================================================================
  FAIL: test_build_is_dirty_from_options (snapcraft.tests.test_pluginhandler.IsDirtyTestCase)
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "/tmp/adt-run.6GCmWq/build.jQY/real-tree/snapcraft/tests/test_pluginhandler.py", line 1095, in test_build_is_dirty_from_options
      'Build step was unexpectedly dirty')
  AssertionError: True is not false : Build step was unexpectedly dirty

  ======================================================================
  FAIL: test_build_is_dirty_from_project (snapcraft.tests.test_pluginhandler.IsDirtyTestCase)
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "/usr/lib/python3.5/unittest/mock.py", line 1157, in patched
      return func(*args, **keywargs)
    File "/tmp/adt-run.6GCmWq/build.jQY/real-tree/snapcraft/tests/test_pluginhandler.py", line 1113, in test_build_is_dirty_from_project
      'Build step was unexpectedly dirty')
  AssertionError: True is not false : Build step was unexpectedly dirty

  ======================================================================
  FAIL: test_pull_is_dirty_from_options (snapcraft.tests.test_pluginhandler.IsDirtyTestCase)
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "/tmp/adt-run.6GCmWq/build.jQY/real-tree/snapcraft/tests/test_pluginhandler.py", line 1142, in test_pull_is_dirty_from_options
      'Pull step was unexpectedly dirty')
  AssertionError: True is not false : Pull step was unexpectedly dirty

  ======================================================================
  FAIL: test_pull_is_dirty_from_project (snapcraft.tests.test_pluginhandler.IsDirtyTestCase)
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "/usr/lib/python3.5/unittest/mock.py", line 1157, in patched
      return func(*args, **keywargs)
    File "/tmp/adt-run.6GCmWq/build.jQY/real-tree/snapcraft/tests/test_pluginhandler.py", line 1160, in test_pull_is_dirty_from_project
      'Pull step was unexpectedly dirty')
  AssertionError: True is not false : Pull step was unexpectedly dirty

  [Impact]

   * No visible impact for users.

   * Fixing this test will get us closer to have green executions in
  autopkgtests in all the platforms.

  [Test Case]

   * Run the autopkgtests in a platform that's not amd64,

  [Regression Potential]

   * This could make fail the tests in amd64. But as it's in an
  autopkgtest, any regression will block the new version to get to
  proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1589752/+subscriptions