Hi all,
I filed a bug to follow-up this topic:
https://bugreports.qt-project.org/browse/QTBUG-43096
Chris your hint on the Qt module initialisation was correct, I was
able to now run on both 5.1.1 and 5.3.1. The results are in line with
what's been discussed so far (the cached performance is not
Hi Gunnar,
Can you get a backtrace which might help pinpoint what's causing it?
I've integrated the patch to 5.4, and it passed CI, so at least in the CI
environments it's not crashing, I think.
I don't have a windows 5.4 build to test against, currently, so I'm not
sure what could cause the probl
On Wednesday 03 December 2014 12:46:55 Sarajärvi Tony wrote:
> Now would be the time to read this through, and comment if you have anything
> to say about this ;)
Hi Tony
> Default configs runs for all submodule builds:
>
> linux-arm-gnueabi-g++_Ubuntu_11.10_x86 -> to be moved to Ubuntu 14.04
>
Hi,
Time for a CI configuration cleanup. With new platforms coming in and limited
resources, we need to reduce the amount of builds we continuously
run in the CI. Thus we are proposing the following changes to the default CI
configurations runs. The nightly builds are the *_state builds that
are
On Tuesday 2. December 2014 23.18.01 Thiago Macieira wrote:
> On Tuesday 02 December 2014 19:19:06 Thiago Macieira wrote:
> > 2014-12-03 05:05:49.524 tst_qwindow[7070:1e07] Persistent UI failed to
> >
> > open file
> > file://localhost/Users/qt/Library/Saved%20Application%20State/com.yourcomp
>
