touch-packages team mailing list archive

[Michał Sawicz <michal.sawicz@xxxxxxxxxxxxx>]

** No longer affects: unity8

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1204982

Title:
  refactored autopilot tests are fail prone for wrong environment setup

Status in Autopilot:
  Invalid
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  The old autopilot tests, when you would launch "autopilot run unity8"
  from within the source directory in tests/autopilot/, it would always
  try to run the local build. If there was no local build, it would
  fail, saying it can't find the binary.

  The new ones, don't. They fall back to the installed binary even
  though loading local tests. This fails in like 99% of the cases. Even
  worse, the error messages you get just totally don't match with the
  code you are examining for debugging. This issue is even worse now
  that the tests require a make install in the builddir (not telling so
  btw).

  If the install step really really needs to be kept (which I'm strongly
  voting against) then there should be a big fat debug output which
  binary is loaded, a big fat warning if the expected local installation
  is not found and in no way falling back to some other unity8 binary
  not having to do anything with the local test suite.

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