In the JSC team we've had tremendous difficulty not break the Qt ARMv7 bot, despite our testing of the ARMv7 build ourselves. It turns out that the Qt build is misconfigured and is using the ARMv6 backend despite being labelled as a v7 bot. We don't test or develop the v6 backend, so don't test it -- when coupled with the qt arm bot claiming to be building for v7 confusion reigns.
Sorry to leave you confused, but you are not right, the Qt ARMv7 is not missconfigured. I suppose you know that the ARMv7 architecture covers the ARM Cortex-A, ARM Cortex-M, ARM Cortex-R families. Each family support Thumb-2 instruction set, and Cortex-A and Cortex-R support ARM instruction set. The Qt ARMv7 bot is using the following architecture specific compiler options: -marm -mcpu=cortex-a8 -mfloat-abi=softfp -mfpu=vfpv3-d16 So the QT ARMv7 buildbot tests the ARMv7 architecture (Cortex-A8). I think the main confusion is between the name of ARMAssembler and ARMv7Assembler rather instead of name of buildbot. In 2009 Anno Domini I suggested to use ARM* and Thumb2* prefixes for the two different assemblers. I still think these or similar names will describe better the differences. So, I close this bug.