[Development] How can Qt 5.6.0 MinGW pass in CI with QTBUG-49971 open?

[Koehne Kai]

> -----Original Message-----
> From: Development [mailto:development-
> bounces+kai.koehne=theqtcompany.com at qt-project.org] On Behalf Of
> Roland Winklmeier
> Sent: Thursday, March 03, 2016 10:52 AM
> To: Thiago Macieira <thiago.macieira at intel.com>
> Cc: development at qt-project.org
> Subject: Re: [Development] How can Qt 5.6.0 MinGW pass in CI with
> QTBUG-49971 open?
> 
> 2016-03-03 9:14 GMT+01:00 Thiago Macieira <thiago.macieira at intel.com
> <mailto:thiago.macieira at intel.com> >:
> 
> 
> 	On quinta-feira, 3 de março de 2016 00:06:41 PST Thiago Macieira
> wrote:
> 	> On quinta-feira, 3 de março de 2016 08:56:35 PST Roland
> Winklmeier wrote:
> 	> > So how is it possible that this error does not show up in CI? I did
> 	> > download the Qt MinGW 4.9 version, so CI should fail to build.
> 	>
> 	> -Wundef is not enabled by either -Wall or -Wextra. It's entirely
> correct C
> 	> source to #if on undefined tokens: they become zeroes.
> 	>
> 	> -Werror is never enabled to end-users either, so QTBUG-49971 is
> not a real
> 	> FTBFS.
> 
> 	But -Wundef and -Werror are part of our headersclean target. So
> you have a
> 	point: how is the CI building this?
> 
> 
> 
> No matter if I download the source from download.qt.io
> <http://download.qt.io>  or clone from git and run the normal build as
> configured in CI, I get the build error. I'm not changing any flags. So my and
> CI configuration should be exactly the same and either both pass or fail. But
> CI passes and the build of several people locally fail. I wonder how thats
> possible.

What mingw toolchain do you use? AFAIK the CI uses

https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.2/threads-posix/dwarf/i686-4.9.2-release-posix-dwarf-rt_v3-rev1.7z/download 

Regards

Kai