I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests. There are currently no found changes at least in Qt upstream to backport arm64 related fixes.
Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening:
https:/ /launchpadlibra rian.net/ 288487533/ buildlog_ ubuntu- yakkety- arm64.ubuntu- push-qml_ 0.1+15. 10.20150826. 1-0ubuntu2_ BUILDING. txt.gz
I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests. There are currently no found changes at least in Qt upstream to backport arm64 related fixes.
Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: /launchpadlibra rian.net/ 288516465/ buildlog_ ubuntu- yakkety- arm64.online- accounts- api_0.1+ 16.10.20161006. 1-0ubuntu1_ BUILDING. txt.gz /launchpadlibra rian.net/ 288515705/ buildlog_ ubuntu- xenial- arm64.online- accounts- api_0.1+ 16.04.20161006. 1-0ubuntu1_ BUILDING. txt.gz /launchpadlibra rian.net/ 288515510/ buildlog_ ubuntu- vivid-arm64. online- accounts- api_0.1+ 15.04.20161006. 1-0ubuntu1_ BUILDING. txt.gz
https:/
https:/
https:/
This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24.