Bug 14730 - libxml-parser-perl ptest intermittent failure
Summary: libxml-parser-perl ptest intermittent failure
Status: RESOLVED FIXED
Alias: None
Product: Package Testing (ptest)
Classification: QA/Testing
Component: ptest (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2022-02-21 07:03 UTC by Oleksiy Obitotskyy
Modified: 2022-02-24 11:25 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oleksiy Obitotskyy 2022-02-21 07:03:09 UTC
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/2870/steps/12/logs/stdio

qemuarm64-ptest ubuntu2004-arm-1

WARNING: core-image-ptest-all-1.0-r0 do_testimage: There were failing ptests.
Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/core/decorator/__init__.py", line 36, in wrapped_f
    return func(*args, **kwargs)
  File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/core/decorator/__init__.py", line 36, in wrapped_f
    return func(*args, **kwargs)
  File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/core/decorator/__init__.py", line 36, in wrapped_f
    return func(*args, **kwargs)
  File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/runtime/cases/ptest.py", line 25, in test_ptestrunner_expectfail
    self.do_ptestrunner()
  File "/home/pokybuild/yocto-worker/qemuarm64-ptest/build/meta/lib/oeqa/runtime/cases/ptest.py", line 112, in do_ptestrunner
    self.fail(failmsg)
AssertionError: Failed ptests:
{'libxml-parser-perl': ['t/decl']}

Cannot run ptests without @expectedFailure as ptests are expected to fail
Comment 1 Richard Purdie 2022-02-24 11:25:36 UTC
Issue was a regression in expat 2.4.5 release, reported to upstream and resolved by the 2.4.6 upgrade.