On Mon, Dec 08, 2025 at 01:25:51PM -0700, Soren Stoutner wrote:
Current builds are failing on the following architectures: s390x, hppa,powerpc, ppc64, sparc64.
Big-endian
+print_address unexpected error test results: +Test <00><00><04><38><00><00><04><41><00><00><04><3F><00><00><04><4B><00><00><04><42><00><00><04><30><00><00><04><3D><00><00><04><38><00><00><04><35>(decoding error) +test5@<00><00><04><38><00><00><04><41><00><00><04><3F><00><00><04><4B><00><00><04><42><00><00><04><30><00><00><04><3D><00><00><04><38><00><00><04><35>.net(decoding error) +Test <00><00><04><38><00><00><04><41><00><00><04><3F><00><00><04><4B><00><00><04><42><00><00><04><30><00><00><04><3D><00><00><04><38><00><00><04><35>(decoding error) <test5@<00><00><04><38><00><00><04><41><00><00><04><3F><00><00><04><4B><00><00><04><42><00><00><04><30><00><00><04><3D><00><00><04><38><00><00><04><35>.net(decoding error)>
UTF-16 or UCS-2
The fact that this failure only happens on certain architectures is what puzzles me, particularly because it fails the same way on these architectures. Because I don’t know much about what makes all these failing architectures different that all the ones that succeed, I thought I would ask here hoping that there is something obvious that people more experienced with these architectures might immediately notice.
It's endianness, and 16-bit Unicode is endianness-dependent, so it's not particularly surprising. But that's likely all that can be deducted without looking at the actual test code.
-- WBR, wRAR
Attachment:
signature.asc
Description: PGP signature