** Changed in: pyruntest (Ubuntu Trusty)
     Assignee: Thomi Richards (thomir) => Dimitri John Ledkov (xnox)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to pyruntest in Ubuntu.
https://bugs.launchpad.net/bugs/1270812

Title:
  pyruntest fails to build from source in trusty

Status in “pyruntest” package in Ubuntu:
  Confirmed
Status in “pyruntest” source package in Trusty:
  Confirmed

Bug description:
  see https://launchpadlibrarian.net/162444081/buildlog_ubuntu-
  trusty-i386.pyruntest_0.1%2B13.10.20130702-0ubuntu1_FAILEDTOBUILD.txt.gz

  running build
  running build_scripts
  creating build
  creating build/scripts-2.7
  copying and adjusting pyruntest -> build/scripts-2.7
  changing mode of build/scripts-2.7/pyruntest from 664 to 775
     debian/rules override_dh_auto_test
  make[1]: Entering directory `/build/buildd/pyruntest-0.1+13.10.20130702'
  nosetests
  ....F..............
  ======================================================================
  FAIL: tests.FunctionalRunTests.test_can_generate_html_coverage
  ----------------------------------------------------------------------
  _StringException: Traceback (most recent call last):
    File "/build/buildd/pyruntest-0.1+13.10.20130702/tests.py", line 197, in 
test_can_generate_html_coverage
      self.assertThat(code, Equals(0))
    File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 412, in 
assertThat
      raise MismatchError(matchee, matcher, mismatch, verbose)
  MismatchError: 0 != 1

  
  ----------------------------------------------------------------------
  Ran 19 tests in 4.411s

  FAILED (failures=1)
  make[1]: *** [override_dh_auto_test] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pyruntest/+bug/1270812/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to     : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to