[Development] qtbase CI now takes 6 hours

[Sarajärvi Tony]

Hi

We do have a development side version of the CI where we test our setup. However, not everything is run past that, unfortunately. This Java should have for example. However, it might not have caused problems there, as the problem was somewhat random, but it could have and we should have.

I also stated that Sergio runs a script that marks tests significant if they pass. Don't know what I was thinking. The script changes the 'forcesuccess' status of builds that have passed. Builds (the compilation) have nothing to do with tests however. Tests are not touched by this script.

Perhaps we should stop calling building building, and call it compiling instead. This way we won't confuse terms with the whole build that includes compiling and testing.

-Tony

> -----Original Message-----
> From: Qi Liang
> Sent: 21. toukokuuta 2013 10:29
> To: Sarajärvi Tony; Stephen Kelly
> Cc: development at qt-project.org
> Subject: RE: [Development] qtbase CI now takes 6 hours
> 
> Hi,
> 
> Tony and Stephen, yes, our CI need more attention now.
> 
> Tony, does it look like we need a CI for our CI system? I mean to verify those
> update work or not, for example, the Java update, Windows 8 shutdown and
> etc. Any plan for this?
> 
> Regards,
> Liang
>