group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1831467@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package umockdev - 0.14.2-1

---------------
umockdev (0.14.2-1) unstable; urgency=medium

  * New upstream version 0.14.2:
    - preload: Fix incomplete reads scripts
    - tests: Fix incomplete reads for fuzzy script tests
      (Closes: #767908)
    - tests: Add $SLOW_TESTBED_FACTOR env var for slow architectures
  * Make autopkgtest robust for slow testbeds.
    Set the new `$SLOW_TESTBED_FACTOR` to avoid frequent failures on armhf
    and other slow/shared distro CI hardware. (LP: #1831467)
  * debian/rules: Add hack for code coverage related autoconf regression.

 -- Martin Pitt <mpitt@xxxxxxxxxx>  Wed, 29 Jul 2020 18:08:15 +0200

** Changed in: umockdev (Ubuntu Groovy)
       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/1831467

Title:
  test-umockdev tests flaky on armhf (and sometimes other archs)

Status in umockdev package in Ubuntu:
  Fix Released
Status in umockdev source package in Xenial:
  In Progress
Status in umockdev source package in Bionic:
  In Progress
Status in umockdev source package in Focal:
  In Progress
Status in umockdev source package in Groovy:
  Fix Released

Bug description:
  [impact]

  these tests fail intermittently, due to various timing issues, as well
  as an actual code bug in how data fuzz is calculated.

  it looks like the failures are mostly on armhf, but do happen less
  often on other archs.

  [test case]

  check the previous autopkgtest logs, e.g.
  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/umockdev/20190601_015323_8f795@/log.gz

  [regression potential]

  any regression would likely result in incorrectly failing/passing autopkgtests, or in a incorrect pass or incorrect fail of the ScriptRunner
  to verify the data's level of fuzz.

  [scope]

  as the tests are flaky on armhf all the way back to trusty, this is
  needed for all releases.

  [other info]

  Fixed upstream in PR https://github.com/martinpitt/umockdev/pull/103

  Most of the changes are test case fixes, but there is one fix to
  source code to fix the ScriptRunning function that validates the level
  of fuzz in data, so this is not *only* a testcase fix.

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