Hi,
after yet another 5 hour wait just to be greeted with yet another random
failure with no build logs I'm getting really tired of the poor reliability of
the Qt CI system.
https://codereview.qt-project.org/#/c/157590/
has been greeted with genuine failures, failures in qtdeclarative,
qtxmlp
age-
> From: Development [mailto:development-
> bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of Sean Harmer
> Sent: lauantaina 30. huhtikuuta 2016 22.26
> To: development@qt-project.org
> Subject: [Development] Qt CI reliability
>
> Hi,
>
> after yet another 5 hou
On Saturday 30 of April 2016 20:26:20 Sean Harmer wrote:
> Hi,
Hi,
> after yet another 5 hour wait just to be greeted with yet another random
> failure with no build logs I'm getting really tired of the poor reliability
> of the Qt CI system.
I'm sorry about that.
> https://codereview.qt-project
On Monday 02 May 2016 05:05:07 Tuukka Turunen wrote:
> Hi Sean,
>
> Firstofall, I do apologize for the inconvenience caused by the CI system. We
> are fully aware of the situation, and the effect is has for productivity.
> All the developers of The Qt Company are using exactly the same CI system.
On Monday 02 May 2016 11:14:24 Jędrzej Nowacki wrote:
> On Saturday 30 of April 2016 20:26:20 Sean Harmer wrote:
> > Hi,
>
> Hi,
>
> > after yet another 5 hour wait just to be greeted with yet another random
> > failure with no build logs I'm getting really tired of the poor
> > reliability
> > o
On Tuesday 03 of May 2016 14:54:50 Sean Harmer wrote:
> On Monday 02 May 2016 11:14:24 Jędrzej Nowacki wrote:
> > On Saturday 30 of April 2016 20:26:20 Sean Harmer wrote:
> (...)
> What would be a *very* useful feature would be if we can trigger a test
> build of a change on a particular configurat
> -Original Message-
> From: sean.harmer On Behalf Of Sean Harmer
> Sent: tiistaina 3. toukokuuta 2016 15.45
> To: development@qt-project.org
> Cc: Tuukka Turunen
> Subject: Re: [Development] Qt CI reliability
>
>
> So in summary, I appreciate the CI is a
On Tuesday 03 May 2016 17:36:49 Jędrzej Nowacki wrote:
> On Tuesday 03 of May 2016 14:54:50 Sean Harmer wrote:
> > Do you mean VM template? If so then yes that's again something that should
> > ideally be verified before deployment.
>
> Eh, wrong phrasing. Templates are tested. The problem is tha
And more problems today:
http://testresults.qt.io/logs/qt/qt3d/83275e6eb72baa5f80d4fbaaf84bc0ffd1b59762/LinuxUbuntu_15_04x86_64LinuxUbuntuTouch_15_04armv7GCCDisableTests_OpenGLES2/f09f2056189e7df3613966a77c6b671ff3d5ea88/buildlog.txt.gz
results in a 404. I hope this doesn't last all of the holida
On Thursday 05 May 2016 13:01:24 Sean Harmer wrote:
> And more problems today:
>
> http://testresults.qt.io/logs/qt/qt3d/83275e6eb72baa5f80d4fbaaf84bc0ffd1b597
> 62/LinuxUbuntu_15_04x86_64LinuxUbuntuTouch_15_04armv7GCCDisableTests_OpenGLE
> S2/f09f2056189e7df3613966a77c6b671ff3d5ea88/buildlog.txt.
> -Original Message-
> From: Development [mailto:development-
> bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of Sean Harmer
> Sent: torstaina 5. toukokuuta 2016 15.19
> To: development@qt-project.org
> Subject: Re: [Development] Qt CI reliability
>
> On
> Determining architecture... ()
> make: Warning: File `../../../qt/qtbase/config.tests/arch/arch.pro' has
> modification time 1.3e+03 s in the future
> /home/qt/work/build/bin/qmake -qtconf /home/qt/work/build/bin/qt.conf
> -nocache -spec /home/qt/work/qt/qtbase/mkspecs/linux-g++ LIBS+=
> QMAKE_CX
12 matches
Mail list logo
