** Changed in: autopkgtest (Ubuntu Xenial)
     Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: autopkgtest (Ubuntu Xenial)
       Status: In Progress => Won't Fix

-- 
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/1847242

Title:
  adt_run test_tree_output_dir always fails on armhf

Status in autopkgtest package in Ubuntu:
  Fix Released
Status in autopkgtest source package in Xenial:
  Won't Fix

Bug description:
  [impact]

  this autopkgtest always fails on armhf

  [test case]

  run autopkgtest on armhf:

  ======================================================================
  FAIL: test_tree_output_dir (__main__.NullRunner)
  source tree, explicit --output-dir
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "/tmp/autopkgtest.SJn7ZH/build.9Ef/src/tests/adt-run", line 454, in 
test_tree_output_dir
      self.assertIn('cpu_model', info)
  AssertionError: 'cpu_model' not found in {'custom_environment': 
['ADT_COLOR=blue', 'ADT_SOMETHING=foo bar'], 'kernel_version': 'Linux 
4.15.0-62-generic #69-Ubuntu SMP Wed Sep 4 20:57:49 UTC 2019', 'virt_server': 
'adt-virt-null', 'cpu_flags': 'fp asimd evtstrm cpuid', 'nproc': '4'}

  [regression potential]

  test case fix only, low

  [other info]

  this specific check is limited on bionic and later to amd64/i386; on
  xenial it's also run on armhf for some reason, but it always fails.
  It should not be run on armhf.

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

_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to     : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

Reply via email to