Hi,
We created task https://bugreports.qt-project.org/browse/QTBUG-29014 to
track the MinGW test failures.
We (Digia) will primarily focus on getting MinGW compile tests enabled
since the tests are already covered by the MSVC ones.
You are welcome to submit fixes, though, please refer to the a
On Wednesday, January 09, 2013 09:48:35 Koehne Kai wrote:
> Maybe the cmake call should add a -G "MinGW Makefiles", or Visual Studio
> shouldn't be in the environment, or both Can some cmake or ActiveQt expert
> comment?
The -G "MinGW Makefiles" was implemented, and seems to have worked.
Thanks,
Koehne Kai wrote:
>>
>> [...] Below is list of failed autotests from already executed MinGW
>> stages:
>>
>> QtActiveQt_dev_Integration [1]
>>
>> === Failures:
>> ===
>> cmake
>> === Totals: 3 tests, 2 passes, 1 fail
>
ect: [Development] CI autotest failures for MinGW
>
[...]
> Below is list of failed autotests from already executed MinGW stages:
>
> QtActiveQt_dev_Integration [1]
>
> === Failures:
> ===
>
Hi,
Before Christmas vacations I announced that configuration for MinGW
CI stage was added among the other new stages. Unfortunately there
was bug in CI scripts which prevented autotest execution on MinGW
builds. This bug has been fixed now and there are already some auto
test results available f