This is what I got while testing on the 4 main platforms. (ubuntu22 to follow soon)
Debian 11 amd64: OK Debian 11 arm64 failed Failed test: (2023-01-09 08:48:49.174 +0100) general.m:37 ... -classNamed returns the correct class Failed test: (2023-01-09 08:48:49.175 +0100) general.m:61 ... -principalClass returns TestClass for +bundleForClass:[TestClass class] Debian 10 amd64 failed Failed test: (2023-01-09 08:48:36.765 +0100) general.m:37 ... -classNamed returns the correct class Failed test: (2023-01-09 08:48:36.765 +0100) general.m:61 ... -principalClass returns TestClass for +bundleForClass:[TestClass class] Debian 10 arm64 failed Failed set: basic.m:9 ... problem in TLS support. (this might be to build environment. Not sure what it could be. This one is built on a raspberry pi 4) So it seems the failed test for class names seems independent of architecture or Debian version which is rather puzzling... > On 9 Jan 2023, at 08:28, Fred Kiefer <[email protected]> wrote: > > > >> Am 09.01.2023 um 07:58 schrieb Andreas Fink <[email protected]>: >> >> I usually build packages for Debian 10 & 11 for amd64 and arm64 >> >> I have encountered make check returning an error on Debian11 arm64 but not >> on Debian 11 amd64 >> >> Built on Debian 11 intel: All OK! >> Built on Debian 11 on arm64: 2 Failed tests >> Failed test: (2023-01-09 07:39:12.574 +0100) general.m:37 ... >> -classNamed returns the correct class >> Failed test: (2023-01-09 07:39:12.576 +0100) general.m:61 ... >> -principalClass returns TestClass for +bundleForClass:[TestClass class] >> >> I'm surprised as this stuff is not really architecture specific usually. >> > > Which version of libobjc are you building against and is it the same for both > architectures?
