← Back to team overview

debcrafters-packages team mailing list archive

[Bug 2112576] Re: riscv64 autopkgtest failure due to unexpected text in test/relaxng/invaliddemo.xml

 

I can reproduce the issue locally using autopkgtest-virt-qemu (emulated
riscv64 on amd64). Interestingly, if I execute only the failing test by
specifying --test-name, or if I use --shell-fail to jump in the testbed
(via ssh) and execute the test manually, it passes reliably.

Before investigating deeper, I believe it would be useful to see how
things behave in Debian, but Ubuntu libxml-libxml-perl is currently
ahead of Debian. Also: there's a new upstream version of libxml-libxml-
perl (2.0210). We should be able to do this once forky opens for
development.

--

tl;dr steps to reproduce the issue locally:

0. make sure you have the latest autopkgtest installed
1. autopkgtest-buildvm-ubuntu-cloud -v -a riscv64 --release questing
2. autopkgtest --shell-fail --timeout-factor=100 --no-built-binaries libxml-libxml-perl -- qemu --qemu-architecture=riscv64 --timeout-reboot 3000 --show-boot autopkgtest-questing-riscv64.img

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to libxml-libxml-perl in
Ubuntu.
https://bugs.launchpad.net/bugs/2112576

Title:
  riscv64 autopkgtest failure due to unexpected text in
  test/relaxng/invaliddemo.xml

Status in libxml-libxml-perl package in Ubuntu:
  Incomplete

Bug description:
  test/relaxng/invaliddemo.xml finds the following:

  527s test/relaxng/invaliddemo.xml:1: Relax-NG validity error : Did not expect element TEX.2 there
  527s test/relaxng/invaliddemo.xml:1: Relax-NG validity error : Did not expect text in element  TODO  content
  527s ok 87 - catch validation error for a RelaxNG file
  527s ok 88 - validate using XML::LibXML::RelaxNG
  527s test/relaxng/invaliddemo.xml:1: Relax-NG validity error : Did not expect element TEX.2 there
  527s test/relaxng/invaliddemo.xml:1: Relax-NG validity error : Did not expect text in element  TODO  content

  And it seems to happen for libxml-libxml-perl autopkgtests triggered
  by various packages. Here is one log, for example:

  https://autopkgtest.ubuntu.com/results/autopkgtest-
  questing/questing/riscv64/libx/libxml-libxml-
  perl/20250604_023208_8e755@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml-libxml-perl/+bug/2112576/+subscriptions



References