Hi Olek, On 09-10-2022 21:37, Olek Wojnar wrote:
I have just started the test on one of our workers manually and I can confirm that the patches are all applied.Pardon my ignorance of the finer points of autopkgtest but is there a way to get more-verbose logging?
I started it with --shell-fail. That gave me a shell on the first test that failed and I could then easily confirm that the patches were applied.
Are you using the -ddd option? I can't figure out from the CI logs, for example, whether or not quilt successfully applied patches. One reason I thought patches might not be applied was that I never saw quilt being installed in the test bed.
I think since long you don't need quilt. IIRC dpkg will apply patches natively when you ask it via apt for the source.
Yes, please. Can you verify that the third_party/ijar/common.h file has the following on lines 24 and 25?#include <limits> #include <stdexcept>
autopkgtest [03:49:26]: test java-1: -----------------------]autopkgtest [03:49:26]: test java-1: - - - - - - - - - - results - - - - - - - - - -
java-1 FAIL non-zero exit status 1autopkgtest [03:49:26]: - - - - - - - - - - running shell - - - - - - - - - - root@elbrus:/tmp/autopkgtest-lxc.ookvjd3p/downtmp/build.OBp/src# head -n25 third_party/ijar/common.h | tail -n2
#include <limits> #include <stdexcept>
Those are the lines that fix the "'numeric_limits' is not a member of 'std'" error. If they are present, that confirms that add_include_for_limits.patch is definitely being applied correctly. But if that's the case, then I'm really stumped as to why we're seeing that failure and only on those architectures...
Unfortunately I can't help you with that. Paul
OpenPGP_signature
Description: OpenPGP digital signature
