Thank you Christian for the sponsorship, the test environment and the
commands.
The first test that is failing looks for a string phrase
(test/suite_decryption.py @ line 271
self.assertTrue(self.grepOutput('Who has 192.168.1.1')) ). I put a line
of debug in the countOutput function
** Changed in: lto-disabled-list (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961901
Title:
3.6.2-1 FTBFS in Jammy on
This bug was fixed in the package lto-disabled-list - 22
---
lto-disabled-list (22) jammy; urgency=medium
* Add wireshark @ arm64 s390x (LP: #1961901)
-- Miriam España Acebal Thu, 24 Feb 2022
13:11:15 +0100
** Changed in: lto-disabled-list (Ubuntu)
Status: New => Fix
Repro:
$ cd ~/wireshark-3.6.2/obj-s390x-linux-gnu
$ /usr/bin/cmake -E env PYTHONIOENCODING=UTF-8 /usr/bin/python3.10
../test/test.py --verbose --program-path
/root/wireshark-3.6.2/obj-s390x-linux-gnu/run suite_decryption
This will trigger the same fails, but run just this test.
And to pick
Thanks, I reviewed and sponsored the lto-disabled change.
For the remaining s390x issue please use the s390x containers that we
set up to debug this Miriam
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/lto-disabled-list/+git/lto-disabled-list/+merge/416029
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961901
Title:
Hi!
I made several buildings in a ppa (arm64,s 390x and proposed pocket)
here [1], with three scenarios:
1) the optimization moutline-atomics (sorry for the misunderstanding) plus
disabling Bsymbolic-functions -> doesn't work
2) only disabling Bsymbolic-functions (in a bad attempt to restrict
And by opening my eyes (thanks Miriam) this wasn't ever on amd64 but only arm64
(+s390x).
Ok, so ignore my local tests, we'll need arm64 or s390x systems for this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "build as-is locally against jammy-proposed on x86 -
working"
https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/1961901/+attachment/5563424/+files/wireshark_3.6.2-1_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
FYI debdiff used in local tests https://paste.ubuntu.com/p/W4JvNthN9H/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961901
Title:
3.6.2-1 FTBFS in Jammy on x86/s390x
To manage notifications
Hmm,
I quickly rebuilt as-is and with both suggestions disabled in local sbuild.
They BOTH worked fine which implies that the build issue on launchpad is
a) only happening on launchpad
or
b) something in jammy-proposed has been fixed in the last few days/hours that
resolved this
In both cases:
Hi Miriam
moutline-atomics was an arm related optimization - that was related to CPC
work, but not here. Sorry if my quick hint in the meeting was misleading.
I meant to quick try:
1. disable LTO https://wiki.ubuntu.com/ToolChain/LTO
2. do not use symbolic-functions
For arm64, the execution of test 15 (/wmem/datastruct/tree) of 37 -
suite_unittests ends in SIGSEGV.
Adding the compilation flag "-moutline-atomics" didn't work... I'm
still investigating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: wireshark (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961901
Title:
3.6.2-1 FTBFS in Jammy on x86/s390x
14 matches
Mail list logo
