Re: [Development] Setting up test server for QtNetwork tests

[Sarajärvi Tony]

Hi

That manual is probably the only official one we have. Up  until Qt 5.5 we've 
been using that one ourselves as well.
We did have a work in progress version on top of Ubuntu 12.04: 
https://gitorious.org/qtqa/tosarajas-sysadmin-nts.git/?p=qtqa:tosarajas-sysadmin-nts.git;a=blob;f=README.network_test_server.txt;h=2b745d077e98f2cf64c4ab8e0391e8e0cbf51118;hb=HEAD

But as newer versions of backend services fixed various things, our autotests 
weren't fixed to handle the situation. Thus we were stuck with the old one.

Now in Qt 5.6 we use yet another one, and sadly I have no knowledge what it 
contains. It's on my todo list to figure out. Most likely a mixture of the two 
above.

-Tony

> -Original Message-
> From: Development [mailto:development-boun...@qt-project.org] On
> Behalf Of Konstantin Tokarev
> Sent: 27. tammikuuta 2016 18:17
> To: development@qt-project.org
> Subject: [Development] Setting up test server for QtNetwork tests
> 
> Hello,
> 
> What is the recommended (and possibly easiest) way to set up test server
> for QtNetwork?
> 
> I've found manual [1]. Is it the preferred way? If so, is Ubuntu 10.04 
> required,
> or other versions (e.g., 12.04 or 14.04) may be used as well?
> 
> Isn't there any ready-to-use VirtualBox or Docker image with test server?
> 
> [1]
> http://code.qt.io/cgit/qtqa/sysadmin.git/tree/README.network_test_serve
> r.txt
> 
> --
> Regards,
> Konstantin
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] qtdeclarative-5.6.0-beta build failure on rhel6

[Sarajärvi Tony]

> -Original Message-
> From: Development [mailto:development-boun...@qt-project.org] On
> Behalf Of Takahiro Hashimoto
> Sent: 19. tammikuuta 2016 12:36
> To: development@qt-project.org
> Cc: Rex Dieter 
> Subject: Re: [Development] qtdeclarative-5.6.0-beta build failure on rhel6
> 
> Hi.
> 
> Sorry I don't have any info about C++11 code in 5.6 branch. I'd like to
> comment for Simon's question about devltoolset requirement.
> 
> According to this thread [1] maybe the binary distribution of Qt 5 requires
> newer(4.7?) libstdc++ than the one which is provided by RHEL/CentOS
> 6.(4.4.7)

Yes that and also GCC gets updated when we install devtoolset.

> This might lead updating wiki article of building qt5 to add this workaround.
> 
> The Red Hat Developer Toolset has been released 4 times for RHEL5/6
> release
> (1.0 to 3.0) and currently only 3.0 is supported on RHEL6. [2]
> 
> I think These are reason why for this requirement.
> And I don't know if the older version of Qt5(5.0,5.1..) could be built with
> gcc 4.4...
> 
> By the way, RHEL6 is now at second half of its 10 years support life cycle.
> [3] I think it would be better to start to consider about Qt5 support for
> RHEL7.  As RHEL7 has gcc 4.8, the devtoolset is not needed.
> 
> 
> [1] http://forum.qt.io/topic/30140/solved-qt-creator-could-not-find-or-load-
> the-qt-platform-plugin-xcb/
> 
> [2] https://access.redhat.com/support/policy/updates/dts
> [3] https://access.redhat.com/support/policy/updates/errata
> 
> 
> Regards.
> Takahiro
> 
> 
> On 2016年1月18日月曜日 15時58分09秒 JST Hausmann Simon wrote:
> > I'm surprised as well that this slipped through. Looks like MSVC 2010
> > supports this bit as well.
> >
> > It is true however that we require devtoolset 3 for RHEL 6. Does anyone
> > remember the reason?
> >
> >
> > Simon
> >
> >   Original Message
> > From: Olivier Goffart
> > Sent: Monday, January 18, 2016 16:26
> > To: development@qt-project.org
> > Cc: Rex Dieter
> > Subject: Re: [Development] qtdeclarative-5.6.0-beta build failure on rhel6
> >
> > On Montag, 18. Januar 2016 08:31:01 CET Rex Dieter wrote:
> > > I'm trying to build(bootstrap) qt-5.6.0-beta stack on rhel6, and have run
> > > into a build failure in qtdeclarative,
> >
> > 
> >
> > > beta/tools/qmlimportscanner/main.cpp:376: error: no matching function
> for
> > > call to 'find_if(QList::const_iterator,
> >
> > std::find_if is new in C++11
> > And it was used in https://codereview.qt-project.org/125853/ in the 5.6
> > which still does not require C++11.
> >
> > Apparently the CI does not try to build this with non-c++11 enabled
> > compilers?
> >
> > --
> > Olivier
> >
> > Woboq - Qt services and support - https://woboq.com -
> https://code.woboq.org
> > ___
> > Development mailing list
> > Development@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/development
> > ___
> > Development mailing list
> > Development@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/development
> 
> 
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] QtMetrics 2 launched!

[Sarajärvi Tony]

Hi

Qt Metrics site has been renewed to better serve the needs of the developers. 
Please visit http://testresults.qt.io/qtmetrics/

The UI has been renewed to support responsiveness and bookmarkable URLs, and to 
make content of the pages easier to read.

The data is structured now so that only the (daily) Qt5 state builds are 
included. You can view either the Qt5 state build results or the test results 
in the Qt5 state builds across the branches. Hierarchy of the build and test 
data is as follows:

-  project ("Qt5" or the testset parent project like "QtBase")

-  configuration (e.g. "macx-clang_developer-build_OSX_10.10")

-  testset (e.g. "tst_qftp")

-  test function (e.g. "connectToHost")

-  test row (e.g. "WithoutProxy:ok01")

With the Qt Metrics you can for example:

-  see a quick overview to the latest build and test status

-  see the build status for windows platform configurations

-  see test status for all testsets in QtBase

-  see which testsets, test functions and testrows are failing in 
macx-clang_developer-build_OSX_10.10

-  see top failing testsets and test functions

-  see the list of flaky testsets

-  see the blacklisted test functions and test rows that are currently 
passing the testing, and therefore the blacklisted tag could maybe be removed

In case of questions, proposals, and improvement ideas, please contact the 
development team https://wiki.qt.io/Qt_Metrics_2_Description#SUPPORT

If interested, you are welcome to contribute new features and views.

(same in https://forum.qt.io/topic/59091/qt-metrics-site-has-been-renewed)


Tony Sarajärvi
CI Tech Lead

The Qt Company / Digia Finland Ltd, Elektroniikkatie 10, 90590 Oulu, Finland
Email: tony.saraja...@theqtcompany.com
http://qt.io
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qt
Qt Twitter: @QtbyDigia, @Qtproject
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] IT maintenance break next weekend affecting the CI

[Sarajärvi Tony]

Hi

Beginning at 8:00 EEST on Saturday 29th of August lasting until 20:00 EEST on 
Sunday we will have an IT maintenance break. All CI servers (except Macs) will 
be shut down for ESXI upgrade. This means that you might experience aborted 
builds and commits that aren't going anywhere. The maintenance wont' affect 
qt.io domain.

Thank you for your patience,
-Tony

Tony Sarajärvi
CI Tech Lead

The Qt Company / Digia Finland Ltd, Elektroniikkatie 10, 90590 Oulu, Finland
Email: tony.saraja...@theqtcompany.commailto:tony.saraja...@theqtcompany.com
http://qt.io
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qthttp://www.facebook.com/qt
Qt Twitter: @QtbyDigia, @Qtproject
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 4.8: disabling the CI and closing for anything except security fixes

[Sarajärvi Tony]

 -Original Message-
 From: development-bounces+tony.sarajarvi=theqtcompany.com@qt-
 project.org [mailto:development-
 bounces+tony.sarajarvi=theqtcompany@qt-project.org] On Behalf Of
 Thiago Macieira
 Sent: 14. elokuuta 2015 3:40
 To: development@qt-project.org
 Subject: [Development] Qt 4.8: disabling the CI and closing for anything
 except security fixes
 
 I recently tried to fix a very simple bug in Qt 4.8 but I can't get the change
 to integrate because the CI seems to have fallen into disrepair.
 
 Instead of using valuable QA time in fixing the CI for 4.8, I'd like to 
 propose
 instead that we simply disable the CI for that version and close Qt 4.8 for
 any submission except security fixes. Gerrit would be configured for pure
 merging instead of staging, but that would only be enabled to Gerrit admins
 and they'd only do it after confirmation from the security team (security@qt-
 project.org).
 
 Any objections?

Not from me ;)

-Tony

 --
 Thiago Macieira - thiago.macieira (AT) intel.com
   Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] 5.5 CI having problems on tst_qmimedatabase-xml

[Sarajärvi Tony]

I remember some test regading files and folders having a problem a year or two 
ago. The problem was that the tests weren't cleaned up. So windows ran out of 
random folder and / or files it could create. So if the next machine happened 
to pick up the build, it might pass, but the ones that had a lot of test data 
lying around couldn't test anymore.

As I logged into that particular machine that ran that build, its 
Users\qt\AppData\Local\Temp is quite loaded with stuff like
tst_qfileinfo-RYGJOI
tst_qfileinfo-sXgxSH
tst_qfileinfo-t6LYMr
...
All of those folders.

If I recall, previously the tests began failing as we had 255 or 256 of those.

The folder currently has 988 files and 3018 folders in it, beginning with tst_*
It has 23161 files and 3744 folders in total in it :P

Other files or directories mostly named the same are:
tst_qsharedpointer
tst_qsqltablemodel
tst_qdeclarativewebview
tst_qfilediaglo2
tst_qmimedatabase
etc...


I'll cleanup the temp folder now and at least this number 2 machine is then 
cleaned up from this mess.

-T



 -Original Message-
 From: development-bounces+tony.sarajarvi=theqtcompany.com@qt-
 project.org [mailto:development-
 bounces+tony.sarajarvi=theqtcompany@qt-project.org] On Behalf Of
 Thiago Macieira
 Sent: 3. elokuuta 2015 8:57
 To: development@qt-project.org
 Subject: Re: [Development] 5.5 CI having problems on tst_qmimedatabase-
 xml
 
 On Monday 13 July 2015 14:48:40 Thiago Macieira wrote:
  This test began failing about a week ago, for no apparent reason. I don't
  think it's a Qt issue, but more of a CI issue.
 
  It's failing on:
 
  FAIL!  : tst_QMimeDatabase::initTestCase() 'm_temporaryDir.isValid()'
  returned FALSE. ()
  c:
 
 \work\build\qt\qtbase\tests\auto\corelib\mimetypes\qmimedatabase\qmi
 medataba
  se- xml\../tst_qmimedatabase.cpp(84) : failure location
 
  Since m_temporaryDir is default-constructed, this implies somehow that
  C:\temp or C:\tmp is not writeable.
 
  Can someone look into this?
 
 This is still happening.
 --
 Thiago Macieira - thiago.macieira (AT) intel.com
   Software Architect - Intel Open Source Technology Center
 
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] testresults.qt-project.org will discontinue!!!

[Sarajärvi Tony]

All should be OK now!

Note that logs are now located in the new host testresults.qt.io/ci
The status page as well is now there: testresults.qt.io/ci/status
And QtMetrics http://testresults.qt.io/qtmetrics

Regards,
-Tony

From: Sarajärvi Tony
Sent: 26. helmikuuta 2015 15:20
To: development@qt-project.org
Subject: testresults.qt-project.org will discontinue!!!

Hi

Terribly sorry for the late notice, but even I wasn't aware of the tight 
schedule before yesterday.

Testresults.qt-project.org will be powered off during the weekend. The content 
has been transferred over to testresults.qt.io already and it will host the 
services (CI status, QtMetrics and logs) from now on.

We will shut down the CI briefly in a moment so that we reconfigure the new 
host for it. To our understanding, it shouldn't affect the current jobs 
running, except that their logs won't update before we restart the CI. It will 
also naturally prevent anything staged from going into integration before we 
restart the CI.

Estimated downtime 60 min.

Regards,
-Tony

Tony Sarajärvi
CI Tech Lead

The Qt Company / Digia Finland Ltd, Elektroniikkatie 10, 90590 Oulu, Finland
Email: tony.saraja...@theqtcompany.commailto:tony.saraja...@theqtcompany.com
http://qt.io
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qthttp://www.facebook.com/qt
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] testresults.qt-project.org will discontinue!!!

[Sarajärvi Tony]

Hi

Terribly sorry for the late notice, but even I wasn't aware of the tight 
schedule before yesterday.

Testresults.qt-project.org will be powered off during the weekend. The content 
has been transferred over to testresults.qt.io already and it will host the 
services (CI status, QtMetrics and logs) from now on.

We will shut down the CI briefly in a moment so that we reconfigure the new 
host for it. To our understanding, it shouldn't affect the current jobs 
running, except that their logs won't update before we restart the CI. It will 
also naturally prevent anything staged from going into integration before we 
restart the CI.

Estimated downtime 60 min.

Regards,
-Tony

Tony Sarajärvi
CI Tech Lead

The Qt Company / Digia Finland Ltd, Elektroniikkatie 10, 90590 Oulu, Finland
Email: tony.saraja...@theqtcompany.commailto:tony.saraja...@theqtcompany.com
http://qt.io
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qthttp://www.facebook.com/qt
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI replaced Ubuntu 12.04 with 14.04 in dev branch

[Sarajärvi Tony]

Hi

As planned earlier, we replaced Ubuntu 12.04 configurations with Ubuntu 14.04 
configurations in dev branch just a few seconds ago.

All 14.04 configuration should have forcesuccess and insignificant on to begin 
with, if we didn't miss anything.

We will keep several eyes on the dev branch now to see what we missed.

Good luck,
-Tony

Tony Sarajärvi
CI Tech Lead

The Qt Company / Digia Finland Ltd, Elektroniikkatie 10, 90590 Oulu, Finland
Email: tony.saraja...@theqtcompany.commailto:tony.saraja...@theqtcompany.com
http://qt.io
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qthttp://www.facebook.com/qt
Qt Twitter: @QtbyDigia, @Qtproject
--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] CI configuration changes

[Sarajärvi Tony]

Hi

Here's a wiki page describing the planned changed along with a bit of version 
information of the tools:

http://qt-project.org/wiki/Qt-5.5.0-tools-and-versions

-Tony

 -Original Message-
 From: development-bounces+tony.sarajarvi=theqtcompany.com@qt-
 project.org [mailto:development-
 bounces+tony.sarajarvi=theqtcompany@qt-project.org] On Behalf Of
 Rutledge Shawn
 Sent: 21. tammikuuta 2015 9:41
 To: Turunen Tuukka
 Cc: Thiago Macieira; development@qt-project.org
 Subject: Re: [Development] CI configuration changes
 
 
 On 21 Jan 2015, at 08:19, Turunen Tuukka
 tuukka.turu...@theqtcompany.com wrote:
 
 
  On 20/01/15 21:44, Thiago Macieira thiago.macie...@intel.com wrote:
 
  On Tuesday 20 January 2015 19:21:04 Sarajärvi Tony wrote:
  What's your timeline for this?
 
  If I don't get any objections here, I could start the work immediately.
  Goal
  is to do it right away, so that we have time to verify the platforms
  before
  5.5 feature freeze.
  If you're looking at this for before the Qt 5.5
  feature freeze, OS X 10.7 will break and will be effectively
  unsupported
  for 5.5 because I won't bother fixing forkfd for it.
 
  My understanding is that OS X 10.7 is allowed to break in 5.5.
 
  Usually we give people a one version notice... So we shouldn't allow it
  to
  break in 5.5, but announce that support drops in 5.6.
 
  OS X 10.7 has been listed as Tier 2 already for Qt 5.4:
  http://doc.qt.io/qt-5/supported-platforms.html
 
  That said, we should of course carefully consider whether or not it is
  supported with Qt 5.5.
 
 Maybe we should leave it in CI for the 5.5 timeframe.  What would we have
 to give up to do that?
 
 This is an example of why I'd like our CI system to be transformed into a
 distributed one: it should be possible for anyone to add machines to the pool.
 Even if some of them are non-binding. e.g. a contributed machine would
 only be able to do +1/-1 on a patch, as a warning that a certain patch will
 break a tier 2 platform.  There are many such platforms which we aren't
 testing.
 
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Changes fail to integrate due to unexpected errors

[Sarajärvi Tony]

Fixed. 3 builds were running on the Windows machines and I aborted them. They 
were going to fail anyways. Now things should be back to normal... not meaning 
that things would work fluently ;)

-Tony

 -Original Message-
 From: development-bounces+tony.sarajarvi=theqtcompany.com@qt-
 project.org [mailto:development-
 bounces+tony.sarajarvi=theqtcompany@qt-project.org] On Behalf Of
 Sarajärvi Tony
 Sent: 2. helmikuuta 2015 9:07
 To: Keränen Pasi; development@qt-project.org
 Subject: Re: [Development] Changes fail to integrate due to unexpected
 errors
 
 I found the reason behind these failures. Our reboot script has vanished
 from our Jenkins configurations. If a build has been aborted, the processes
 are left hanging and reserving the files prohibiting Windows from deleting
 them. Fixing the reboot issue as soon as find the culprit.
 
 -Tony
 
  -Original Message-
  From: development-bounces+tony.sarajarvi=theqtcompany.com@qt-
  project.org [mailto:development-
  bounces+tony.sarajarvi=theqtcompany@qt-project.org] On Behalf Of
  Keränen Pasi
  Sent: 2. helmikuuta 2015 7:38
  To: development@qt-project.org
  Subject: Re: [Development] Changes fail to integrate due to unexpected
  errors
 
  Hi,
 
 
  Same issue with [2] in qtcanvas3d as well, several tries on Friday and
  over the weekend have failed due problems with CI.
 
 
  [2] https://codereview.qt-project.org/#/c/104158/
 
  Regards,
  Pasi
 
  On 02/02/15 03:14, Aaron McCarthy mccarthy.aa...@gmail.com wrote:
 
  Hi,
  
  Changes, such as [1], to the qtlocation repository have been failing to
  integrate for the last few days with errors similar to:
  
  An unexpected error occurred, most likely due to no fault in the tested
  code
  itself :(
  Please point some CI administrator towards this problem. Meanwhile, it
  may be
  worthwhile to attempt the build again.
`git clone qtgitreadonly:qt/qtqa.git _qtqa_latest' exited with code 128
  at
  _testconfig/test.pl line 1103.
Build log:
  http://testresults.qt-
  project.org/ci/QtLocation_dev_Integration/build_0034
  1/win32-mingw491_developer-build_qtlibinfix_Windows_7/log.txt.gz
  
  
  Can a CI administrator please investigate the issue.
  
  
  [1] https://codereview.qt-project.org/101972
  
  Cheers,
  
  --
  Aaron McCarthy
  ___
  Development mailing list
  Development@qt-project.org
  http://lists.qt-project.org/mailman/listinfo/development
 
  ___
  Development mailing list
  Development@qt-project.org
  http://lists.qt-project.org/mailman/listinfo/development
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Changes fail to integrate due to unexpected errors

[Sarajärvi Tony]

I found the reason behind these failures. Our reboot script has vanished from 
our Jenkins configurations. If a build has been aborted, the processes are left 
hanging and reserving the files prohibiting Windows from deleting them. Fixing 
the reboot issue as soon as find the culprit.

-Tony

 -Original Message-
 From: development-bounces+tony.sarajarvi=theqtcompany.com@qt-
 project.org [mailto:development-
 bounces+tony.sarajarvi=theqtcompany@qt-project.org] On Behalf Of
 Keränen Pasi
 Sent: 2. helmikuuta 2015 7:38
 To: development@qt-project.org
 Subject: Re: [Development] Changes fail to integrate due to unexpected
 errors
 
 Hi,
 
 
 Same issue with [2] in qtcanvas3d as well, several tries on Friday and
 over the weekend have failed due problems with CI.
 
 
 [2] https://codereview.qt-project.org/#/c/104158/
 
 Regards,
 Pasi
 
 On 02/02/15 03:14, Aaron McCarthy mccarthy.aa...@gmail.com wrote:
 
 Hi,
 
 Changes, such as [1], to the qtlocation repository have been failing to
 integrate for the last few days with errors similar to:
 
 An unexpected error occurred, most likely due to no fault in the tested
 code
 itself :(
 Please point some CI administrator towards this problem. Meanwhile, it
 may be
 worthwhile to attempt the build again.
   `git clone qtgitreadonly:qt/qtqa.git _qtqa_latest' exited with code 128
 at
 _testconfig/test.pl line 1103.
   Build log:
 http://testresults.qt-
 project.org/ci/QtLocation_dev_Integration/build_0034
 1/win32-mingw491_developer-build_qtlibinfix_Windows_7/log.txt.gz
 
 
 Can a CI administrator please investigate the issue.
 
 
 [1] https://codereview.qt-project.org/101972
 
 Cheers,
 
 --
 Aaron McCarthy
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
 
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI broken

[Sarajärvi Tony]

Hi

The CI will remain broken at least today. We have no idea why the RSA keys are 
messed up on the servers even though we copy paste everything from a working 
server. Investigations continue tomorrow...

-Tony

Tony Sarajärvi
CI Tech Lead

The Qt Company / Digia Finland Ltd, Elektroniikkatie 10, 90590 Oulu, Finland
Email: tony.saraja...@theqtcompany.commailto:tony.saraja...@theqtcompany.com
http://qt.io
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qthttp://www.facebook.com/qt
Qt Twitter: @QtbyDigia, @Qtproject
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] CI broken

[Sarajärvi Tony]

I think I got everything up and running again. At least nothing is complaining 
currently.

Checking the status again in 11 hours when I get to work.

Regards,
-Tony

From: development-bounces+tony.sarajarvi=theqtcompany@qt-project.org 
[mailto:development-bounces+tony.sarajarvi=theqtcompany@qt-project.org] On 
Behalf Of Sarajärvi Tony
Sent: 27. tammikuuta 2015 15:49
To: development@qt-project.org
Subject: [Development] CI broken

Hi

The CI will remain broken at least today. We have no idea why the RSA keys are 
messed up on the servers even though we copy paste everything from a working 
server. Investigations continue tomorrow...

-Tony

Tony Sarajärvi
CI Tech Lead

The Qt Company / Digia Finland Ltd, Elektroniikkatie 10, 90590 Oulu, Finland
Email: tony.saraja...@theqtcompany.commailto:tony.saraja...@theqtcompany.com
http://qt.io
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qthttp://www.facebook.com/qt
Qt Twitter: @QtbyDigia, @Qtproject
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] CI for QNX 6.5.0

[Sarajärvi Tony]

Hi

Would it be enough if we added it only to the nightly 'state' builds? Having it 
in the general configurations would once again increase the load that's already 
quite high. Building it once a day per branch for the whole Qt5 wouldn't be 
that bad.

-Tony

 -Original Message-
 From: development-bounces+tony.sarajarvi=theqtcompany.com@qt-
 project.org [mailto:development-
 bounces+tony.sarajarvi=theqtcompany@qt-project.org] On Behalf Of
 Rafael Roquetto
 Sent: 26. tammikuuta 2015 21:57
 To: Qt Project Development Mailing-List
 Subject: [Development] CI for QNX 6.5.0
 
 Hello,
 
 What would be the possibility of getting the CI system to build for QNX 6.5.0,
 apart from 6.6.0 which it already does?
 
 Currently, I have been manually searching for merge requests that cause
 regressions but from time to time something always manages to slip thru,
 last
 case being https://codereview.qt-project.org/#/c/103616/.
 
 I understand QNX 6.5.0 compiler is somewhat old, but I personally believe it
 is important to continue supporting it, since there are still a lot of 6.5.0
 deployments around, specially on environments where migration to a newer
 version is anything but trivial, since we are talking about high scale systems
 here.
 
 Having the CI test for QNX 650 too would be really handy.
 
 Any comments?
 
 Regards,
 Rafael
 --
 Rafael Roquetto | rafael.roque...@kdab.com | Software Engineer
 Klarälvdalens Datakonsult AB, a KDAB Group company
 Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
 KDAB - Qt Experts - Platform-independent software solutions
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] CI configuration changes

[Sarajärvi Tony]

Hi all!

Thanks for all the feedback we received. Based on those and the changes needed 
we have updated our proposal a bit.

Binary packages are currently built with Ubuntu 11.10 because they deploy on 
different distros quite well. That's something we aim for, so that we don't 
have to start creating a secondary set of installers for another set of 
distros. We also need to upgrade the compiler version we use so that 
QtWebEngine can update to a newer Chromium version. To achieve this we are 
currently testing creating binaries RHEL 6.6b to see how they deploy, and it's 
looking promising. Other options we have are openSUSE 13.1 and Ubuntu 14.04 
currently, and opinions are welcomed here.

We also want to expand our CI coverage to newer platforms and free up some 
capacity to new platforms not yet in the CI. 
Thus we came up with these concrete changes to the CI, mainly to be done in the 
5.5 time frame:
 
- We will drop 11.10 targets from the CI regarding the 'dev' branch.

- Ubuntu 12.04 LTS will be updated to be 14.04 LTS in 'dev' branch.

- OSX 10.7 will be dropped in 'dev' branch.

- OSX 10.7 will be moved to nightly builds (_state builds) in '5.4.x' branches.

- Windows 10 will be added to the CI for 'dev' branch as soon as we have it 
available.

- The *pkg* configs on different platforms are to be moved to nightly builds as 
well.

- A few configurations are moved from Ubuntu to RHEL to correlate to the weight 
shift.

A summary of the configuration for 'dev' branch would look smt like this:

linux-arm-gnueabi-g++_Ubuntu_14.04_x64
linux-g++_static_Ubuntu_14.04_x64

linux-android-g++_Ubuntu_14.04_x64
linux-android_armeabi-g++_Ubuntu_14.04_x64
linux-imx6-armv7a_Ubuntu_14.04_x64
linux-qnx-armv7le_Ubuntu_14.04_x64
linux-qnx-x86_Ubuntu_14.04_x64

linux-g++_developer-build_openSUSE_13.1_x64

linux-x86-g++_shadow-build_RHEL_66_x64 (we have to cross-compile x86 on RHEL)
linux-g++_no-widgets_RHEL_66_x64
linux-g++_developer-build_qtnamespace_qtlibinfix_RHEL_66_x64

macx-clang_no-framework_OSX_10.8
macx-clang_static_OSX_10.9
macx-clang_developer-build_OSX_10.9
macx-ios-clang_OSX_10.9
macx-clang_developer-build_qtnamespace_OSX_10.10

win32-mingw491_developer-build_qtlibinfix_opengl_Windows_7
win32-msvc2010_developer-build_qtnamespace_Windows_7
win32-msvc2010_opengl_dynamic_Windows_10 (Windows 8.1 until then)
win64-msvc2013_developer-build_qtnamespace_Windows_81
wince70embedded-armv4i-msvc2008_Windows_7
winphone-arm-msvc2013_Windows_81
winrt-x64-msvc2013_Windows_81

-Tony


 -Original Message-
 From: development-bounces+tony.sarajarvi=theqtcompany.com@qt-
 project.org [mailto:development-
 bounces+tony.sarajarvi=theqtcompany@qt-project.org] On Behalf Of
 Sarajärvi Tony
 Sent: 4. joulukuuta 2014 14:26
 To: Thiago Macieira; development@qt-project.org
 Subject: Re: [Development] CI configuration changes
 
  -Original Message-
  From: development-bounces+tony.sarajarvi=theqtcompany.com@qt-
  project.org [mailto:development-
  bounces+tony.sarajarvi=theqtcompany@qt-project.org] On Behalf Of
  Thiago Macieira
  Sent: 3. joulukuuta 2014 19:33
  To: development@qt-project.org
  Subject: Re: [Development] CI configuration changes
 
  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
 
 Hi :)
 
 
   Default configs runs for all submodule builds:
  
   linux-arm-gnueabi-g++_Ubuntu_11.10_x86 - to be moved to Ubuntu
  14.04
   linux-g++_shadow-build_Ubuntu_11.10_x86 - to be moved to Ubuntu
  14.04
  
   linux-g++_developer-build_qtnamespace_qtlibinfix_Ubuntu_11.10_x64 -
  to be
   removed
 
  Looks good, considering there's a namespace+infix left running below.
 
   linux-g++_no-widgets_Ubuntu_12.04_x64
  
   linux-android-g++_Ubuntu_12.04_x64
   linux-android_armeabi-g++_Ubuntu_12.04_x64
   linux-imx6-armv7a_Ubuntu_12.04_x64
   linux-qnx-armv7le_Ubuntu_12.04_x64
   linux-qnx-x86_Ubuntu_12.04_x64
  
   linux-g++_developer-build_OpenSuSE_13.1_x64
  
   linux-g++_developer-build_qtnamespace_qtlibinfix_RHEL65_x64
  
   macx-clang_developer-build_qtnamespace_OSX_10.7 - to be removed
 
  I don't see any other 10.7 remaining. Does this means we'll slowly stop
  supporting 10.7?
 
 It was still in the whole Qt5 build mentioned below, and moved to nightly
 builds to be as non-blocking. But I reopened the discussion over here... I
 won't make any drastic changes just yet.
 
 Also, I didn't think about this yesterday, but these changes were intended
 for both 5.4 and dev (future 5.5 ) branches. We could however have them
 different with the vm-cloner coming (separate templates cloned for every
 branch).
 
  I will not be sorry to see it go, but if it goes I promise you we'll break
  10.7 support within one week (the forkfd work failed on 10.7 for unknown
  reasons and I will submit it with clear conscience as soon as the 10.7 it 
  out
  of CI).
 
   macx-clang_no

Re: [Development] CI configuration changes

[Sarajärvi Tony]

 -Original Message-
 From: development-bounces+tony.sarajarvi=theqtcompany.com@qt-
 project.org [mailto:development-
 bounces+tony.sarajarvi=theqtcompany@qt-project.org] On Behalf Of
 Thiago Macieira
 Sent: 20. tammikuuta 2015 18:21
 To: development@qt-project.org
 Subject: Re: [Development] CI configuration changes
 
 On Tuesday 20 January 2015 11:38:24 Sarajärvi Tony wrote:
  - OSX 10.7 will be dropped in 'dev' branch.
 
 What's your timeline for this?

If I don't get any objections here, I could start the work immediately. Goal is 
to do it right away, so that we have time to verify the platforms before 5.5 
feature freeze.

 If you're looking at this for before the Qt 5.5
 feature freeze, OS X 10.7 will break and will be effectively unsupported for
 5.5 because I won't bother fixing forkfd for it.

My understanding is that OS X 10.7 is allowed to break in 5.5.

 
 Given that you said that 10.7 will be on nightly builds for 5.4.x and not for
 5.5.x, I'm assuming you meant for this to happen before the feature freeze.
 
Yes :)


 --
 Thiago Macieira - thiago.macieira (AT) intel.com
   Software Architect - Intel Open Source Technology Center
 
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] 5.4.1 branch has now been added to the CI

[Sarajärvi Tony]

Hi!

The subject says it all...

-Tony

Tony Sarajärvi
CI Tech Lead
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI wrap up of 2014

[Sarajärvi Tony]

Hi all!

Last day of the year and time to wrap up what has changed in the CI during the 
last year, and a few words about what's to come.


· New Apple hardware was installed

o   24 x quad core mac minis with upgraded memory

o   Configured them to use our LUN instead of internal hard drives

o   With these we were able to get rid of stand-alone minis running things and 
replaced them with virtual machines

o   This immediately helped the situation where we were running out of hardware 
to run all mac configurations which caused queues to build up

· Autotest blacklisting was introduced which has helped getting builds 
passing where tests are flaky

· Lots of different platforms were added to add the variety were we 
test Qt on:

o   OpenSUSE

o   RHEL 6.5

o   QNX 6.5.0 and 6.6.0

o   OS X 10.10

o   Windows 8.1

o   Winphone

· QtMetrics got new cool features like Build time graphs and detailed 
failure tables from autotests.

o   http://testresults.qt-project.org/qtmetrics/metricspageci.php

o   http://qt-project.org/wiki/QtMetrics_How_To_Read

· Nightly builds are set up (builds with postfix '_state')

o   Once a day a broader set of configurations are run with all autotests run

o   Logs are published to testresults and inserted into QtMetrics

o   Doesn't block, but is only informative of the current state

· And naturally we keept upgrading xcodes, visual studios, mesa 
drivers, openssl etc that's just daily maintenance work

---

To be able to cope with this increasingly complex environment we have developed 
something called VM-cloner. The main idea behind it is that we no longer have 
dozens of virtual machines up and running that are maintained with puppet 
scripts or similar. VM-cloner will clone the virtual machines on-the-fly from 
templates as is needed by any particular job. And after a build is done with 
them, the machines are deleted and the resources are freed.
In bullets:

· Maintenance is reduced to template images which can be verified to 
work before taken into use

· No unnecessary virtual machines occupy resources

· Load is balanced throughout our servers enabling more efficient use 
of our hardware (builds are faster ;))

· Less disk space is needed as cloned virtual machines are linked 
clones of the template image

· We can now support several machine configurations simultaneously. 
Meaning we can build different Qt branches simultaneously without the need to 
reconfigure the virtual machines.

· Possibility to not delete a machine after build if debugging is needed

· Doesn't face Jenkins' problems with rebooting nodes

VM-cloner is already partly in use and will expand to cover more submodules in 
upcoming weeks. We will gradually transfer builds over to it, so that we can 
verify everything working.

---

We also have a new CI coming. This is planned to replace the very unstable 
Junkins. It will also optimize the building so that we will have an artifact 
storage where we store already built binaries and reuse them whenever possible 
making builds a lot faster...in theory. More about this next year.

---

We will also clean up the configuration a bit. We will move stuff from blocking 
CI to nightly builds and also remove old platforms. Other threads are already 
ongoing about this, but it's difficult to get a consensus of what should remain 
in the CI. We don't have resources to test everything after all.

---

Listing of dependencies. Currently we say that Qt 5.4 builds in RHEL 6.5 for 
example. This might not be the whole truth as you might need to install a 
devtoolset from a custom repository to get things working. And on top of that 
you might need to say -no-c++11 to configure. So personally I'd like to see a 
list of dependencies per submodule as they are, and not a list of operating 
systems the submodules work on if you modify them. Per submodule, because 
QtWebEngine for example will need a newer GCC version than the other modules. 
This doesn't prevent us from building on a specific platform and claiming we do 
that, but we can't say that Qt works on that platform right out of the box. 
Something to think about...

Qt New Year 2015!
-Tony

Tony Sarajärvi
CI Tech Lead
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] CI configuration changes

[Sarajärvi Tony]

 -Original Message-
 From: development-bounces+tony.sarajarvi=theqtcompany.com@qt-
 project.org [mailto:development-
 bounces+tony.sarajarvi=theqtcompany@qt-project.org] On Behalf Of
 Thiago Macieira
 Sent: 3. joulukuuta 2014 19:33
 To: development@qt-project.org
 Subject: Re: [Development] CI configuration changes
 
 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

Hi :)

 
  Default configs runs for all submodule builds:
 
  linux-arm-gnueabi-g++_Ubuntu_11.10_x86 - to be moved to Ubuntu
 14.04
  linux-g++_shadow-build_Ubuntu_11.10_x86 - to be moved to Ubuntu
 14.04
 
  linux-g++_developer-build_qtnamespace_qtlibinfix_Ubuntu_11.10_x64 -
 to be
  removed
 
 Looks good, considering there's a namespace+infix left running below.
 
  linux-g++_no-widgets_Ubuntu_12.04_x64
 
  linux-android-g++_Ubuntu_12.04_x64
  linux-android_armeabi-g++_Ubuntu_12.04_x64
  linux-imx6-armv7a_Ubuntu_12.04_x64
  linux-qnx-armv7le_Ubuntu_12.04_x64
  linux-qnx-x86_Ubuntu_12.04_x64
 
  linux-g++_developer-build_OpenSuSE_13.1_x64
 
  linux-g++_developer-build_qtnamespace_qtlibinfix_RHEL65_x64
 
  macx-clang_developer-build_qtnamespace_OSX_10.7 - to be removed
 
 I don't see any other 10.7 remaining. Does this means we'll slowly stop
 supporting 10.7?

It was still in the whole Qt5 build mentioned below, and moved to nightly 
builds to be as non-blocking. But I reopened the discussion over here... I 
won't make any drastic changes just yet.

Also, I didn't think about this yesterday, but these changes were intended for 
both 5.4 and dev (future 5.5 ) branches. We could however have them different 
with the vm-cloner coming (separate templates cloned for every branch).
 
 I will not be sorry to see it go, but if it goes I promise you we'll break
 10.7 support within one week (the forkfd work failed on 10.7 for unknown
 reasons and I will submit it with clear conscience as soon as the 10.7 it out
 of CI).
 
  macx-clang_no-framework_OSX_10.8
 
  macx-clang_developer-build_OSX_10.9
 
  macx-ios-clang_OSX_10.9
 
  macx-clang_developer-build_OSX_10.10 - to be replaced by
  clang_developer-build_qtnamespace_OSX_10.10
 
  win32-mingw47_developer-build_qtlibinfix_Windows_7 - to be replaced
 by
  win32-mingw49_developer-build_qtlibinfix_Windows_7
  win32-mingw48_developer-build_qtlibinfix_opengl_Windows_7 - to be
 moved to
  nightly builds
 
  win32-msvc2010_Windows_7 - to be removed
  win32-msvc2010_developer-build_qtnamespace_Windows_7
  win32-msvc2010_developer-build_angle_Windows_7 - to be removed
  win32-msvc2010_opengl_dynamic_Windows_7 - to be moved to
 windows 10
  eventually
 
  wince70embedded-armv4i-msvc2008_Windows_7
 
  win64-msvc2012_developer-build_qtnamespace_Windows_81 - to be
 moved to
  nightly builds win64-msvc2013_developer-
 build_qtnamespace_Windows_81
 
  winphone-arm-msvc2013_Windows_81
 
  winrt-x64-msvc2013_Windows_81
 
 Rest looks fine.

Cheers :)

 
  When building the whole Qt5 (not e.g. QtBase) we have these added
 already,
  but we would change them as following:
 
  linux-g++_bin-pkg-config_Ubuntu_11.10_x86 - to be moved to nighty
 builds
  (state builds) linux-g++_static_Ubuntu_12.04_x64
  macx-clang_bin-pkg-config_OSX_10.7 - to be moved to nighty builds
  macx-clang_static_OSX_10.9
  win32-msvc2010_bin-pkg-config_Windows_7 - to be moved to nightly
 builds
  win32-msvc2010_static_Windows_7 - to be moved to windows 10
 eventually
 
  Also we might add RHEL5.8 to nightly builds if it looks like we have spare
  time.
 
  --
  PRIVACY AND CONFIDENTIALITY NOTICE
  This message and any attachments are intended only for use by the named
  addressee and may contain privileged and/or confidential information. If
  you are not the named addressee you should not disseminate, copy or
 take
  any action in reliance on it. If you have received this message in error,
  please contact the sender immediately and delete the message and any
  attachments accompanying it. Digia Plc does not accept liability for any
  corruption, interception, amendment, tampering or viruses occurring to
 this
  message. --
 
 Can you drop this note from the message when posting to the mailing
 list.You've posted to a public mailing list and the email got archived all
 over the internet.

LOL! :D Didn't realize people actually read footers :P
 --
 Thiago Macieira - thiago.macieira (AT) intel.com
   Software Architect - Intel Open Source Technology Center
 
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI configuration changes

[Sarajärvi Tony]

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 triggered once a day and the logs are published to QtMetrics.

Now would be the time to read this through, and comment if you have anything to 
say about this ;)

Default configs runs for all submodule builds:

linux-arm-gnueabi-g++_Ubuntu_11.10_x86 - to be moved to Ubuntu 14.04
linux-g++_shadow-build_Ubuntu_11.10_x86 - to be moved to Ubuntu 14.04

linux-g++_developer-build_qtnamespace_qtlibinfix_Ubuntu_11.10_x64 - to be 
removed

linux-g++_no-widgets_Ubuntu_12.04_x64

linux-android-g++_Ubuntu_12.04_x64
linux-android_armeabi-g++_Ubuntu_12.04_x64
linux-imx6-armv7a_Ubuntu_12.04_x64
linux-qnx-armv7le_Ubuntu_12.04_x64
linux-qnx-x86_Ubuntu_12.04_x64

linux-g++_developer-build_OpenSuSE_13.1_x64

linux-g++_developer-build_qtnamespace_qtlibinfix_RHEL65_x64

macx-clang_developer-build_qtnamespace_OSX_10.7 - to be removed

macx-clang_no-framework_OSX_10.8

macx-clang_developer-build_OSX_10.9

macx-ios-clang_OSX_10.9

macx-clang_developer-build_OSX_10.10 - to be replaced by 
clang_developer-build_qtnamespace_OSX_10.10

win32-mingw47_developer-build_qtlibinfix_Windows_7 - to be replaced by 
win32-mingw49_developer-build_qtlibinfix_Windows_7
win32-mingw48_developer-build_qtlibinfix_opengl_Windows_7 - to be moved to 
nightly builds

win32-msvc2010_Windows_7 - to be removed
win32-msvc2010_developer-build_qtnamespace_Windows_7
win32-msvc2010_developer-build_angle_Windows_7 - to be removed
win32-msvc2010_opengl_dynamic_Windows_7 - to be moved to windows 10 eventually

wince70embedded-armv4i-msvc2008_Windows_7

win64-msvc2012_developer-build_qtnamespace_Windows_81 - to be moved to nightly 
builds
win64-msvc2013_developer-build_qtnamespace_Windows_81

winphone-arm-msvc2013_Windows_81

winrt-x64-msvc2013_Windows_81


When building the whole Qt5 (not e.g. QtBase) we have these added already, but 
we would change them as following:

linux-g++_bin-pkg-config_Ubuntu_11.10_x86 - to be moved to nighty builds 
(state builds)
linux-g++_static_Ubuntu_12.04_x64
macx-clang_bin-pkg-config_OSX_10.7 - to be moved to nighty builds
macx-clang_static_OSX_10.9
win32-msvc2010_bin-pkg-config_Windows_7 - to be moved to nightly builds
win32-msvc2010_static_Windows_7 - to be moved to windows 10 eventually

Also we might add RHEL5.8 to nightly builds if it looks like we have spare time.

Regards,
-Tony

Tony Sarajärvi
CI Tech Lead

The Qt Company / Digia Finland Ltd, Elektroniikkatie 10, 90590 Oulu, Finland
Email: tony.saraja...@theqtcompany.commailto:tony.saraja...@theqtcompany.com
http://qt.io
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qthttp://www.facebook.com/qt
Qt Twitter: @QtbyDigia, @Qtproject
--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI Jenkins update

[Sarajärvi Tony]

Hi

Since the 10.10 mac failures you've been experiencing are caused by Java 8 
incompatibility in our current Jenkins 
(https://issues.jenkins-ci.org/browse/JENKINS-21341) , I will update our 
Jenkins to 1.580.1. This will interrupt the 2 builds that are currently 
running, but I'll restage them if I can.

-Tony

Tony Sarajärvi
CI Tech Lead

The Qt Company / Digia Finland Ltd, Elektroniikkatie 10, 90590 Oulu, Finland
Email: tony.saraja...@theqtcompany.commailto:tony.saraja...@theqtcompany.com
http://qt.io
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qthttp://www.facebook.com/qt
Qt Twitter: @QtbyDigia, @Qtproject
--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] CI Jenkins update

[Sarajärvi Tony]

Looks like I have to postpone this till tomorrow. IT is doing maintenance work 
on the servers, and shut them down.

Note that that as well affects your builds so that they will be interrupted. We 
will check the status of the different jobs first thing tomorrow morning and 
see if they remained in some odd state and require our attention.

-Tony

From: development-bounces+tony.sarajarvi=theqtcompany@qt-project.org 
[mailto:development-bounces+tony.sarajarvi=theqtcompany@qt-project.org] On 
Behalf Of Sarajärvi Tony
Sent: 30. marraskuuta 2014 13:07
To: development@qt-project.org
Subject: [Development] CI Jenkins update

Hi

Since the 10.10 mac failures you've been experiencing are caused by Java 8 
incompatibility in our current Jenkins 
(https://issues.jenkins-ci.org/browse/JENKINS-21341) , I will update our 
Jenkins to 1.580.1. This will interrupt the 2 builds that are currently 
running, but I'll restage them if I can.

-Tony

Tony Sarajärvi
CI Tech Lead

The Qt Company / Digia Finland Ltd, Elektroniikkatie 10, 90590 Oulu, Finland
Email: tony.saraja...@theqtcompany.commailto:tony.saraja...@theqtcompany.com
http://qt.io
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qthttp://www.facebook.com/qt
Qt Twitter: @QtbyDigia, @Qtproject
--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] CI broken again

[Sarajärvi Tony]

That QtDeclarative 5.4 needs our attention. As of now we have no idea why it 
has begun failing. We can't recall changing anything on the macs except 
updating xcode

-Tony

From: BogDan [mailto:bog_dan...@yahoo.com]
Sent: 17. lokakuuta 2014 16:03
To: Sarajärvi Tony; Qt Development Group
Subject: Re: [Development] CI broken again

Some tests fails even the patches that we are trying to push are not released.
Check 
https://codereview.qt-project.org/#/c/97244https://codereview.qt-project.org/#/c/97244/
 and 
https://codereview.qt-project.org/#/c/96681https://codereview.qt-project.org/#/c/96681/

Cheers,
BogDan.

From: Sarajärvi Tony 
tony.saraja...@theqtcompany.commailto:tony.saraja...@theqtcompany.com
To: BogDan bog_dan...@yahoo.commailto:bog_dan...@yahoo.com; Qt Development 
Group development@qt-project.orgmailto:development@qt-project.org
Sent: Friday, October 17, 2014 3:58 PM
Subject: RE: [Development] CI broken again

Hi

What exactly is broken?

-T

From: 
development-bounces+tony.sarajarvi=theqtcompany@qt-project.orgmailto:development-bounces+tony.sarajarvi=theqtcompany@qt-project.org
 [mailto:development-bounces+tony.sarajarvi=theqtcompany@qt-project.org] On 
Behalf Of BogDan
Sent: 17. lokakuuta 2014 10:54
To: Qt Development Group
Subject: [Development] CI broken again

Hello,

  It seems that CI is broken for a few days, is anyone working on it? When 
should we expect a fix?

Thanks!

Cheers,
BogDan.


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] CI broken again

[Sarajärvi Tony]

Hi

What exactly is broken?

-T

From: development-bounces+tony.sarajarvi=theqtcompany@qt-project.org 
[mailto:development-bounces+tony.sarajarvi=theqtcompany@qt-project.org] On 
Behalf Of BogDan
Sent: 17. lokakuuta 2014 10:54
To: Qt Development Group
Subject: [Development] CI broken again

Hello,

  It seems that CI is broken for a few days, is anyone working on it? When 
should we expect a fix?

Thanks!

Cheers,
BogDan.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Adding new network tests

[Sarajärvi Tony]

Hi

 -Original Message-
 From: development-bounces+tony.sarajarvi=digia@qt-project.org
 [mailto:development-bounces+tony.sarajarvi=digia@qt-project.org] On
 Behalf Of Mandeep Sandhu
 Sent: 12. kesäkuuta 2014 9:16
 To: Thiago Macieira
 Cc: development@qt-project.org
 Subject: Re: [Development] Adding new network tests
 
 
  Whenever possible, use the mini-http server, as it is less likely to cause
  network timeouts.
 
 Ok. Although since I'm testing out a lot of redirection scenario's, it
 might be better to use a real webserver for generating different types
 of redirect responses (permanent/temporary, redirect to HTTPS,
 with/without auth etc).
 
 
  If you really need something server-side, then the QA guys can help you
 with
  the testserver.
 
 Whom can I get in touch with for configuring a webserver on CI?

That would be us in the CI team.  We'll have to prioritize a bit, but setting 
up a web server shouldn't take that long.
I'll start a private mail conversation amongst us to reduce spam here.

Regards,
-Tony

 
 Thanks,
 -mandeep
 
 
  --
  Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
 
  ___
  Development mailing list
  Development@qt-project.org
  http://lists.qt-project.org/mailman/listinfo/development
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI down

[Sarajärvi Tony]

Hi

Our CI is suffering from network problems. Investigation is ongoing. Until the 
problem is solved, the CI doesn't build anything.

Thank you for your patience,
-Tony

Tony Sarajärvi
CI Tech Lead
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI Jenkins will be updated today

[Sarajärvi Tony]

Hi

We will update Jenkins to hopefully a more stable version. We have tried it 
already on dev side and the update process went fine.

The update will happen after the current qt5 release integration build, which 
will occur around noon, i.e. in 3 hours or so.

Cheers,

-Tony

Tony Sarajärvi
CI Tech Lead
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] CI Jenkins will be updated today

[Sarajärvi Tony]

Hi

We will update Jenkins to hopefully a more stable version. We have tried it 
already on dev side and the update process went fine.

The update will happen after the current qt5 release integration build, which 
will occur around noon, i.e. in 3 hours or so.


We already began the update process. Have to sort out new errors with Groovy 
scripts that seem to cause builds to fail. 

-Tony
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Periodical digest from CI

[Sarajärvi Tony]

Hi everybody

A few pointers from the CI side.

* OpenSUSE 13.1 was brought back a while ago. We fixed the reboot issues with 
it. It had actually to do with Jenkins not noticing nodes going offline. The 
fix might have caused instability on the Windows side however. You might have 
noticed new random failures on Windows as you get a notification like this: 
FATAL: channel is already closed. We suspect this might be due to the fix for 
openSUSE, but we don't know why.

* As openSUSE 13.1 has now been brought back, I removed openSUSE 12.3 from the 
CI. We will continue with 13.1 for a while, as it is an Evergreen version of 
openSUSE and has extended support.

* We have also added RHEL6 x64 to the CI quite recently. The autotests require 
some looking into, but else it seems to be working quite nicely. Also some GCC 
version matching on our dev branch is something I'm trying to have a look at.

* Also Mac 10.9 is in. And like expected with a new OS, autotests have new 
failures.

* Test XML logs are now being uploaded to testresults.qt-project.org. They will 
be copied to the same place where the console logs from Jenkins are located. We 
hope these will help you hunt down problems. We are also working on getting 
this more precise data to QtMetrics eventually. This again seems to cause 
instability on Jenkins. The artifact archiver in Jenkins has crashed at least 
twice since yesterday. Newer versions of Jenkins have already quite a few fixes 
for the archiver, and we're running tests to see if we can switch to a newer 
version. We picked the LTS version 1.532.3 of Jenkins for testing. Hopefully 
we'll switch to it soon.

* Don't recall if I've already mentioned this, but the QtMetrics page ( 
http://testresults.qt-project.org/qtmetrics ) is a lot faster now. We did a 
simple cache for the latest data and it now opens pretty much immediately. I 
hope you get more out of it now as the user experience should be a lot better.

* I hope I still have a few of you with me this far ;) Hot topic: autotests. As 
you already read above, we have failing autotests on a variety of platforms. We 
need ideas on how to get them fixed and most of all we need them fixed! The 
most urgent or most failing ones are listed manually here once a week: 
http://testresults.qt-project.org/qtmetrics/autoteststatus/index.html . 

* Related to fixing autotests is also the matter of running autotests on 
embedded devices. Currently a lot of autotests rely on a desktop machine and / 
or a window server. Current autotests should be flagged in a matter, so that 
they aren't built or run on an embedded platform that hasn't the prerequisites 
for the test to be successful. Ideas around this and instructions on how to 
solve these failing tests are expected to this dev-list :)

* We have once a week a meeting in Freenode on #qt-qa @ 14:00 EE(S)T regarding 
the CI. Feel free to participate and don't be afraid to ask questions or come 
with new suggestions. It's been rather quiet there recently, and we should pick 
it up. You may also ping me outside the meeting. I'm hanging around with the 
nick 'tosaraja'.

* Do you want to see someone from the CI team at the Contributor's summit in 
Berlin in June? Currently our participation is a bit open, but if you send us a 
request to be there, you might turn the scale towards us actually showing our 
faces there :)

Wishing you a good summer,
-Tony


Tony Sarajärvi
CI Tech Lead
Digia, Qt

Digia Plc
Elektroniikkatie 10 
FI-90590 Oulu 

Email: tony.saraja...@digia.com 
http://qt.digia.com 
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercial 
Qt Twitter: www.twitter.com/qtcommercial 

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI Jenkins restart

[Sarajärvi Tony]

Hi

We got tired of restarting Jenkins twice a week, so I tweaked the machine a 
bit. It now has 6 cores instead of 2, it has 24 gigs of memory instead of 8, I 
adjusted Jenkins to use max heap size of 8gb instead of 1gb and maxpermsize was 
increased to 4096 from 512.

Sorry for breaking your current builds, but I hope the system will run more 
smoothly from now on.

Regards,
-Tony

Tony Sarajärvi
CI Tech Lead
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI changes: Win8 removed, Win 8.1 added.

[Sarajärvi Tony]

Hi all!

Small announcement. Windows 8 x64 machines will not be used for building 
anymore. The current configurations have been modified so that previous Win 8 
x64 builds with VS2012 have been replaced with Win 8 x64 VS2013 builds. Same Qt 
configure args are used.

Windows  8.1 x86 will come at some point.

We'll keep an extra eye on the CI to see that this change actually works.

Thanks,
-Tony

Tony Sarajärvi
CI Tech Lead
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Current problems in CI

[Sarajärvi Tony]

Hi

Currently we are blocking QtBase_dev and qt4. We need to get a fix for an 
autotest through so that any commit will have a chance to pass the CI.

Also, you might have noticed a few problems in the CI with breaking builds. 
Jenkins crashed and lost track of qtbase_dev and crashed a few other builds. In 
the aftermath one of the build nodes ended up not being able to clean the work 
areas. Had to go in and do that manually.

Services have now been reset, and we're trying to build the autotest fixes 
currently. After that we'll open the gates again.

Thanks,
-Tony

Tony Sarajärvi
CI Tech Lead
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] About having a cdash dashboard for Qt

[Sarajärvi Tony]

Hi

While in Berlin, I was asked if Qt couldn't have a dashboard to which anyone 
could append build and test results of Qt in different platform and compilers. 
Just like this one for CMake: http://open.cdash.org/index.php?project=CMake

Does anyone have any experience setting up a page like that?

And, before I can even start asking questions, I would like to hear your ideas 
around this subject. What are the things we should publish, take into account 
and all that. Or, do we even see this as something useful after all.

Regards,
-Tony

Tony Sarajärvi
CI Tech Lead
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] CI broken again?

[Sarajärvi Tony]

Here's the debug print from the client side of one failure I suspect falls 
under this category we're discussing here:

QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) not using authentication
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) _q_controlSocketStateChanged 
QAbstractSocket::HostLookupState
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) _q_controlSocketStateChanged 
QAbstractSocket::ConnectingState
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] not 
proxying
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] 
waitForWrite 1
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) _q_controlSocketStateChanged 
QAbstractSocket::ConnectedState
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] 
_q_controlSocketConnected
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] 
_q_controlSocketBytesWritten
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification socks5state 
AuthenticationMethodsSent bytes available 2
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification calling 
parseAuthenticationMethodReply()
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] setting [ 
qt-test-server.qt-test-net : 143 ]
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] sending 
size: 33 data: { 5 1 0 3 26 113 116 45 116 101 115 116 45 115 101 114 118 101 
114 46 113 116 45 116 101 115 116 45 110 101 116 0 143 }
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] 
_q_controlSocketBytesWritten
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification bytes available 
after parsing: 0
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification socks5state 
RequestMethodSent bytes available 148
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification calling 
parseRequestMethodReply()
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] 
parseRequestMethodReply()
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] size: 148 
data: { 5 0 0 1 10 212 1 1 215 203 42 32 79 75 32 91 67 65 80 65 66 73 76 73 84 
89 32 73 77 65 80 52 114 101 118 49 32 76 73 84 69 82 65 76 43 32 73 68 32 69 
78 65 66 76 69 32 83 84 65 82 84 84 76 83 32 76 79 71 73 78 68 73 83 65 66 76 
69 68 93 32 100 101 118 45 113 116 45 116 101 115 116 45 115 101 114 118 101 
114 32 67 121 114 117 115 32 73 77 65 80 32 118 50 46 52 46 49 50 45 68 101 98 
105 97 110 45 50 46 52 46 49 50 45 50 32 115 101 114 118 101 114 32 114 101 97 
100 121 13 10 }
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] got [  
QHostAddress( 10.212.1.1 )  : 55243 ]
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) queueing connectionNotification
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification bytes available 
after parsing: 138
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification more bytes 
available, calling _q_controlSocketReadNotification() again , read 
notifications enabled? false
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) setReadNotificationEnabled( true )
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification socks5state 
Connected bytes available 138
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification connected
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] size: 138 
data: { 42 32 79 75 32 91 67 65 80 65 66 73 76 73 84 89 32 73 77 65 80 52 114 
101 118 49 32 76 73 84 69 82 65 76 43 32 73 68 32 69 78 65 66 76 69 32 83 84 65 
82 84 84 76 83 32 76 79 71 73 78 68 73 83 65 66 76 69 68 93 32 100 101 118 45 
113 116 45 116 101 115 116 45 115 101 114 118 101 114 32 67 121 114 117 115 32 
73 77 65 80 32 118 50 46 52 46 49 50 45 68 101 98 105 97 110 45 50 46 52 46 49 
50 45 50 32 115 101 114 118 101 114 32 114 101 97 100 121 13 10 }
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification calling 
emitReadNotification()
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) queueing readNotification, setting notification 
pending to true
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 
QSocks5SocketEngine(0x99e730) 

Re: [Development] CI broken again?

[Sarajärvi Tony]

Hi

We've discovered (just lately) that in some cases incoming TCP packages are 
bundled together. Somewhere along the line in our network code the first TCP 
packet is drawn from buffers, but the remainders are left there. It's a random 
thing, which we can reproduce in our test rig where we develop the new network 
test server (that's supposed to replace this old one as soon as we get it 100% 
working). Peter is working on the problem it and hopefully we'll get a patch 
for it soon.

Reagards,
-Tony

 -Original Message-
 From: development-bounces+tony.sarajarvi=digia@qt-project.org
 [mailto:development-bounces+tony.sarajarvi=digia@qt-project.org] On
 Behalf Of BogDan
 Sent: 6. helmikuuta 2014 14:26
 To: Mandeep Sandhu; Thiago Macieira
 Cc: development@qt-project.org
 Subject: Re: [Development] CI broken again?
 
 Hi,
 
 
 In your case, the QDnsLookup failure is caused by your code. It happened
 100%
 of the time that the QDnsLookup test was executed and it did not happen
 when
 your change wasn't present.
 
 
 
 It can't be related to my change as the same tests pass 100% of the time on
 my local setup (Ubuntu 13.10) and moreover my changes do not kick-in if the
 name server is not specified (which is the case with all the failing test 
 cases).
 
 
 The latest test failures seemed to be due to timeout rather than anything
 else. The 'waitForDone()' function is exiting with a failure due to DNS lookup
 timeout. The current timeout is set to 10 secs. This is quite large, but 
 still,
 could there be a network issue with the CI setup?
 
 
 
   Ok, maybe his patch has some problems, but I'm pretty sure that my patch
 was staged without his patch a few times and it still failed :( . A little 
 help
 from CI folks will be very appreciated!
 
   Is a little bit frustrating to fix a problem in a few minutes and wait a 
 few days
 to integrate it :).
 
 Cheers,
 BogDan.
 
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Remove OSX 10.6 Build?

[Sarajärvi Tony]

 
 On Jan 20, 2014, at 7:55 PM, Allan Sandfeld Jensen k...@carewolf.com
 wrote:
 
  On Monday 20 January 2014, Thiago Macieira wrote:
  On segunda-feira, 20 de janeiro de 2014 17:36:26, Kurt Pattyn wrote:
  The CI system is still building for OSX 10.6.
  Given the fact that OSX is at version 10.9 now, shouldn't the build for
  10.6 be removed, and ideally replaced with a build for OSX 10.9?
 
  Only if we decide to stop supporting 10.6 entirely. So the question is: do
  we drop it?
 
  Mac devs, what say you?
 
  Could we drop support for build on 10.6, but still support it as runtime
  platform? That seems to be how Apple prefers to support older versions.
 The
  question is of course if out CI system would be able to handle building on
  10.7 but running  on 10.6
 
 
 IIRC, this has been the official statement since Qt 5.0. And yet, for some
 reason, the CI is treating 10.6 as any other platform.
 
 If you do the math from the data available here
 http://www.netmarketshare.com/operating-system-market-
 share.aspx?qprid=10qpcustomd=0 (that's December 2013), 10.6 accounts
 for slightly less than 20% of all the OS X versions. Let's suppose those
 numbers reflect the reality.
 
 Is 20% a lot? I don't know. Is that 20% the same proportion for Qt 5 
 end-users?
 Or Qt 5 developers making a life out of it? Absolutely no idea. Do I see that
 many bugs reported on 10.6? No, not at all.
 
 The truth is, market share doesn't mean anything. Point in case: According to
 the link above, OS X is less than 8% of the total market share. Should we then
 drop the Mac port completely?
 
 For all I know, that twenty-something percent of Mac users running 10.6 or
 earlier are all grandma and grandpa who only use Safari, Skype, and maybe
 some spreadsheet software for tax returns. For all I know, none of them use
 any Qt 5 based software. And why would they? They haven't updated their
 system in years. But maybe I'm wrong, and I'd like to be proven so.
 
 So, can someone tell me what that 20% really means for Qt 5 and its
 developers? This is what it means for me.
 
 We are not that many working on the Mac port. I can think about 6-8 people,
 including me, and AFAIK none of us works 100% on the Mac port (I'd say the
 average is below 50%, so that's 3-4 full-time people maximum). And the
 widgets Mac style code is a mess because we still support 10.6. And we can't
 still use ARC because of 10.6 and some old Xcode version. And have you seen
 the CoreWLAN bear management plugin and how we support 10.6?
 Fullscreen mode hacks? Thank 10.6. Building WebKit and C++ 11, anyone?
 
 Don't give me But 20% market share or The XP of Apple when the debate
 about ending support for 10.6 comes. Give me facts. Give me numbers that
 concern Qt 5. Give me reasons why we should keep parts of Qt in such
 unsatisfactory state.
 
 I only work on my little things, and 10.6 is a burden for me. So, you who work
 out there, that see people using Qt 5 apps, tell me, is it worth it?

Have you noticed this thread 
http://lists.qt-project.org/pipermail/development/2014-January/015078.html ?

You are talking about dropping 10.6 support, whereas we are dropping 10.7 as 
well from the CI.
I know support and CI aren't the same thing, but you might want to object our 
plan which as of now hasn't received any criticism.

Our 5.3 plan is here: 
https://wiki.it.local/display/QTCOM/Qt5.3+Supported+host+platforms

Br,
-Tony
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Suggested platforms for CI, packaging and RTA in Qt 5.3

[Sarajärvi Tony]

 Hi, these are great news for me. Do you plan to use RHEL6's default
 compiler (which is GCC 4.4, and therefore *very* limited C++11 support), or
 the Red Hat Developer Toolset [1] which, as of the 2.0 version, comes with
 GCC 4.8?
 
 Also, the list contains RedHat enterprise_6_x32. However, x32 is an
 experimental ABI using 32bit pointers on 64bit CPUs of the x86-64 family
 [1], so it might be better to call it something else -- perhaps i686 or
 just 32bit?
 


Hi

We are trying to use as old toolsets as possible, so that the binaries created 
are as backward compatible as possible. Currently 4.4.7 as you said is still in 
our machines, but that might change as we investigate what we have to update. 
We still haven't had time to get Qt compiling all the way.

I change the naming on the suggestion to x86 which it should have been. X32 was 
a pure typo as I just copy pasted from my source.

Br,
-Tony
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Remove OSX 10.6 Build?

[Sarajärvi Tony]

  
   On Jan 20, 2014, at 7:55 PM, Allan Sandfeld Jensen k...@carewolf.com
   wrote:
  
On Monday 20 January 2014, Thiago Macieira wrote:
On segunda-feira, 20 de janeiro de 2014 17:36:26, Kurt Pattyn wrote:
The CI system is still building for OSX 10.6.
Given the fact that OSX is at version 10.9 now, shouldn't the build 
for
10.6 be removed, and ideally replaced with a build for OSX 10.9?
   
Only if we decide to stop supporting 10.6 entirely. So the question is:
 do
we drop it?
   
Mac devs, what say you?
   
Could we drop support for build on 10.6, but still support it as runtime
platform? That seems to be how Apple prefers to support older
 versions.
   The
question is of course if out CI system would be able to handle building
 on
10.7 but running  on 10.6
  
  
   IIRC, this has been the official statement since Qt 5.0. And yet, for some
   reason, the CI is treating 10.6 as any other platform.
  
   If you do the math from the data available here
   http://www.netmarketshare.com/operating-system-market-
   share.aspx?qprid=10qpcustomd=0 (that's December 2013), 10.6
 accounts
   for slightly less than 20% of all the OS X versions. Let's suppose those
   numbers reflect the reality.
  
   Is 20% a lot? I don't know. Is that 20% the same proportion for Qt 5 end-
  users?
   Or Qt 5 developers making a life out of it? Absolutely no idea. Do I see
 that
   many bugs reported on 10.6? No, not at all.
  
   The truth is, market share doesn't mean anything. Point in case:
 According
  to
   the link above, OS X is less than 8% of the total market share. Should we
  then
   drop the Mac port completely?
  
   For all I know, that twenty-something percent of Mac users running 10.6
 or
   earlier are all grandma and grandpa who only use Safari, Skype, and
 maybe
   some spreadsheet software for tax returns. For all I know, none of them
  use
   any Qt 5 based software. And why would they? They haven't updated
 their
   system in years. But maybe I'm wrong, and I'd like to be proven so.
  
   So, can someone tell me what that 20% really means for Qt 5 and its
   developers? This is what it means for me.
  
   We are not that many working on the Mac port. I can think about 6-8
  people,
   including me, and AFAIK none of us works 100% on the Mac port (I'd say
  the
   average is below 50%, so that's 3-4 full-time people maximum). And the
   widgets Mac style code is a mess because we still support 10.6. And we
  can't
   still use ARC because of 10.6 and some old Xcode version. And have you
  seen
   the CoreWLAN bear management plugin and how we support 10.6?
   Fullscreen mode hacks? Thank 10.6. Building WebKit and C++ 11, anyone?
  
   Don't give me But 20% market share or The XP of Apple when the
  debate
   about ending support for 10.6 comes. Give me facts. Give me numbers
 that
   concern Qt 5. Give me reasons why we should keep parts of Qt in such
   unsatisfactory state.
  
   I only work on my little things, and 10.6 is a burden for me. So, you who
  work
   out there, that see people using Qt 5 apps, tell me, is it worth it?
 
  Have you noticed this thread http://lists.qt-
  project.org/pipermail/development/2014-January/015078.html ?
 
  You are talking about dropping 10.6 support, whereas we are dropping 10.7
  as well from the CI.
  I know support and CI aren't the same thing, but you might want to object
  our plan which as of now hasn't received any criticism.
 
  Our 5.3 plan is here:
  https://wiki.it.local/display/QTCOM/Qt5.3+Supported+host+platforms
 
 
 And the public link: https://qt-
 project.org/wiki/Qt_5_3_CI_packaging_RTA_environments


Thank you :) I'll close that tab now. Second time I pasted the internal link by 
mistake ;)

-Tony
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Suggested platforms for CI, packaging and RTA in Qt 5.3

[Sarajärvi Tony]

Hi all!

We'd like to open a discussion about the platforms used in the CI, packaging 
(creates the installer binaries) and release test automation. Do note, that 
this list isn't the supported platform -list. This is a subset of that trying 
to achieve a broad coverage of different platforms and configurations.

Our goal is to use the latest platforms, commonly used platforms, platforms 
with extended support and a broad variety of windowing systems.

The current suggestion is public now and it's located here:  
http://qt-project.org/wiki/Qt_5_3_CI_packaging_RTA_environments

Feel free to start commenting.

Our plan to start using RedHat is based on further widening the support for our 
installers. It's still a trial, and we don't know if we are going to succeed.

Regards,
-Tony

Tony Sarajärvi
CI Tech Lead
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
Mobile: +358 050 482 1416
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Maintanance break in CI on Saturday

[Sarajärvi Tony]

Hi all!

IT updated our routers or switches, and this new firmware might be the cause 
for the recent problems we're having. CI can't check anything out from 
Gitorious or Gerrit. IT will revert the firmware at 17:00 EET and see if that 
solves the problem.

Regards,
-Tony

From: development-bounces+tony.sarajarvi=digia@qt-project.org 
[mailto:development-bounces+tony.sarajarvi=digia@qt-project.org] On Behalf 
Of Sarajärvi Tony
Sent: 12. joulukuuta 2013 15:51
To: development@qt-project.org
Subject: [Development] Maintanance break in CI on Saturday

Hi all!

IT will start maintenance work on our CI infrastructure at 9:00 EET. This will 
cause an hour of downtime for our CI as our Jenkins and network test server 
will be moved.

This will cause any build currently running at that point to fail most likely.

After that they will work on different build hosts, causing our OpenSuSE 
capacity to shift down a notch. We will still have a few of them building, but 
if you decide to stage submodules simultaneously on Saturday, you can expect 
some delays on your results :)

Regards,
-Tony

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI will update to VS2012 SP4

[Sarajärvi Tony]

Hi all

The CI is using VS2012 SP2 currently. We will start updating them to SP4 next 
week.

Any objections?

Also VS2013 will be installed on the Win 8 machines. One configuration will be 
either changed to that or a new one will be created to cover it.

Regards,
-Tony
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Maintanance break in CI on Saturday

[Sarajärvi Tony]

Hi all!

IT will start maintenance work on our CI infrastructure at 9:00 EET. This will 
cause an hour of downtime for our CI as our Jenkins and network test server 
will be moved.

This will cause any build currently running at that point to fail most likely.

After that they will work on different build hosts, causing our OpenSuSE 
capacity to shift down a notch. We will still have a few of them building, but 
if you decide to stage submodules simultaneously on Saturday, you can expect 
some delays on your results :)

Regards,
-Tony

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI hardware failures

[Sarajärvi Tony]

Hi all!

We are experiencing hardware failures. Due to this, CI might be queuing stuff 
more than usual. We should still be able to run jobs, but with less machines 
doing the jobs.

Thank you for your patience.

-Tony
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Problem in the CI - solved

[Sarajärvi Tony]

Hi all

Seems we had some problem in the CI. Log said that the machines couldn't 
establish SSH connection to Gerrit. A dozen or so submodules had ended up being 
stuck in integrating for you (error state for us). I just hit retry from our 
end and it looks like things work again.

This means, that all your submissions are now going through, but they got stuck 
in queue. We have 12 modules building simultaneously (though some in queue), 
and it will take some time for the CI to process them all.

Thank you for your patience.

-Tony
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] INFO: CI maintenance break next weekend

[Sarajärvi Tony]

Hi

We will have a maintenance break on our servers and network services on 
Saturday 28th Sep at 08:00 EEST, lasting until Sunday 29th Sep 20:00 EEST.

This might affect your builds, since different parts of the CI infra will be 
down periodically. Auto re-try systems can cope with some of them, but you can 
expect more failures than usual during this time.

Regards,
-Tony

Tony Sarajärvi
CI Tech Lead
Digia, Qt

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] INFO: CI maintenance break at 28th September.

[Sarajärvi Tony]

Sorry about the misinformation in the Subject. The dates are right, but it's 
not now on Saturday, it's the weekend next week.

-Tony

 -Original Message-
 From: Hausmann Simon
 Sent: 18. syyskuuta 2013 14:38
 To: development@qt-project.org
 Cc: Sarajärvi Tony
 Subject: Re: [Development] INFO: CI maintenance break next weekend
 
 On Wednesday 18. September 2013 10.54.52 Sarajärvi Tony wrote:
  Hi
 
  We will have a maintenance break on our servers and network services on
  Saturday 28th Sep at 08:00 EEST, lasting until Sunday 29th Sep 20:00 EEST.
 
  This might affect your builds, since different parts of the CI infra will be
  down periodically. Auto re-try systems can cope with some of them, but you
  can expect more failures than usual during this time.
 
 That's a very unfortunate timing, given that Monday is feature freeze and
 we're all trying hard to get changes through the CI system until then -
 including the weekend.
 
 
 Simon
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt CI improvements

[Sarajärvi Tony]

Hi all!

Our IT has planned a few improvements to our CI. You might be glad to hear 
about these. These changes are addressing random failures in autotests we have 
experiencing.
Please let us know if you have any concerns regarding these. These changes will 
come only after 5.1, so that we don't break anything that at least works 
somehow currently.



1.  Qt-test-server.it.local  qt-test-server.CI.LOCAL re-location ( The 
network test server machines in autotests )

-These server will be also relocated to dedicated host, currently there 
are running on same hosts with build machines

o   when builds are running these servers are affected by performance problems

-Another issues with these servers is they are constantly running low 
on disk space which causes instability to builds

o   these will be fixed adding more disk space when relocation is done


2.  Qt CI infrastructure machines will be moved to a dedicated ESX host

-This is due to a high capacity and resource demands

-This way, machines get mode CPU time and function faster

-Time table end of July


3.  Creation of Secondary GIT mirror for CI clients

-Due to a heavy load on current CI GIT it would be better to create 
another GIT server to balance the load

-One GIT mirror would server windows CI clients and another GIT mirror 
linux clients

-this would split the load and this should fix all performance problems 
which currently occurs

-time table end of July


4.  CI Build machines re-provisioning

-CI build machines will re-provisioned when they are migrated to new 
SAN system

-Timetable on end of July or after 5.1 release

-On same time windows and linux machines ratio on ESX host will be 
changed

o   4 linux and 1 windows CI machine per host



5.  More monitoring to CI infra host

-currently added all critical hosts and components to monitoring


6.  Jenkins awareness of VMware esx resources via vpshere API

-Jenkins enterprise product under investigation

-Possible use of open source plugins to Jenkins

-If we get Jenkins to understand what is happening on ESX server level 
we could optimize builds more and possible safe money on hardware costs

Regards,
-Tony

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI status as of 31. May 2013 - Staging Disabled

[Sarajärvi Tony]

Hi

Staging has been disabled for a short while.

Some of those 'network problems' could be related to the Jenkins and integrator 
server running low on memory. We suspect that Jenkins running on Java leaks 
memory (kind of ironic with Java) or simply just eats up everything it can get. 
After odd symptoms has appeared a reboot has helped in the past. So I'll try 
that right after this ongoing QtBase build has finished.

Regards,
-Tony
---
Hi

A summary of all the problems and current status.


1)  Jenkins drops connections to clients - PROBLEM SPREADS

Initially this was only a windows problem, that occurred when we updated Java 
from U7 to U17. Apparently at the same time, some of the Javas on some machines 
got f#¤ked and we ended up with servers that didn't really have neither or 
both. This was partially fixed with reverting back to U7 with Puppet. However 
we still had some machines having this mess even today. Janne Anttila aided us 
and went through all 50 machines by hand and fixed the Java versions.



Today (22.5.) we also found one Mac 10.7 that has the same symptoms. Reason for 
this unknown. Cure: We brought the node offline and will look at it later.



---

30.5. More and more machines are affected by this, both virtual machines and 
physical machines alike are affected. Reason still unknown, but we'll start 
investigating.





2)  Windows 8's cmd.exe problem - WORKAROUND FOUND

We have Janne Anttila working on this problem now and we got good investigation 
reports from Friedemann on this. Thank you for that, and I'll give you an 
update if we get a solution for this. I'll discuss whether or not we'll 
'forcesuccess' this for the time being. From what I've heard, that's something 
many of you would like to see ;)

---

This has been a problem since last year. Randomly Windows 8 fails builds due to 
this. Won't go any deeper on that one here.

---

30.5. Janne A. has apparently figured out where things go wrong, but not the 
reason why. He also has a workaround coming to the CI to circumvent the problem.



3)  Network problems - WORKAROUND COMING

30.5. This causes builds to fail Git operations for example. We'll implement 
some retry to circumvent these problems. Still at some point, we'll have to 
investigate what the underlying problem is, but currently it's in our backlog.


Regards,
-Tony

Tony Sarajärvi
Senior Software Designer
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
Mobile: +358 050 482 1416
http://qt.digia.com
| Bloghttp://blog.digia.com/ | Twitterhttps://twitter.com/digiaonline | 
LinkedInhttp://www.linkedin.com/company/5119 | 
YouTubehttp://www.youtube.com/digiaonline | 
Facebookhttp://www.facebook.com/digiaonline |
--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI status as of 23. May 2013

[Sarajärvi Tony]

Hi

A summary of all the problems and current status.


1)  Jenkins drops connections to clients - PARTIALLY FIXED

Initially this was only a windows problem, that occurred when we updated Java 
from U7 to U17. Apparently at the same time, some of the Javas on some machines 
got f#¤ked and we ended up with servers that didn't really have neither or 
both. This was partially fixed with reverting back to U7 with Puppet. However 
we still had some machines having this mess even today. Janne Anttila aided us 
and went through all 50 machines by hand and fixed the Java versions.



Today (22.5.) we also found one Mac 10.7 that has the same symptoms. Reason for 
this unknown. Cure: We brought the node offline and will look at it later.



2)  Android builds failing - FIXED
We still had one node (ci-ubuntu1204-x64-06) which had a broken Android SDK. I 
manually went and removed the remains and let Puppet reinstall it. Now 
everything seems to be working, and we are enforcing these builds again.
---

Initially you saw failing builds, as we ran on update on the tool chain. A 
32bit tool chain was replaced with a 64bit. Puppet isn't limited to removing 
stuff while a build is running, so some builds crashed as the Android NDK was 
removed beneath them. Then the new version required a new 64bit host definition 
to the configure, which we found out after a build break. I added it to the 
configure line, but the old one remained in the environment variable settings, 
which I didn't know about. Problems are partially fixed, but we still have a 
few changes that are needed. If I glanced through the last mail correctly, we 
need to update tools to newer ones.



But, all Android builds are currently 'forcesuccess', which means that they 
will pass regardless of the build result.



3)  CMake - FIXED

Actually there was no problem in CMake, but we just had to wait for a commit to 
go through that fixed these errors. So no problem exists anymore.

---

We updated Cmake to 2.8.11. Could be that this caused Windows 8 builds to cause 
fatal errors in linking. Still under investigation what causes this.



4)  Windows 8's cmd.exe problem - NOT FIXED

We have Janne Anttila working on this problem now and we got good investigation 
reports from Friedemann on this. Thank you for that, and I'll give you an 
update if we get a solution for this. I'll discuss whether or not we'll 
'forcesuccess' this for the time being. From what I've heard, that's something 
many of you would like to see ;)

---

This has been a problem since last year. Randomly Windows 8 fails builds due to 
this. Won't go any deeper on that one here.



Since the problems mentioned above don't hinder our daily work, I won't be 
posting this mail every day. I'll just send you informative mails whenever we 
break something or come up with a solution for something.

Regards,
-Tony

Tony Sarajärvi
Senior Software Designer
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
Mobile: +358 050 482 1416
http://qt.digia.com
| Bloghttp://blog.digia.com/ | Twitterhttps://twitter.com/digiaonline | 
LinkedInhttp://www.linkedin.com/company/5119 | 
YouTubehttp://www.youtube.com/digiaonline | 
Facebookhttp://www.facebook.com/digiaonline |
--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Builds failing due to android host

[Sarajärvi Tony]

Updating the NDK began causing new and new problems, so Android builds are 
marked as 'forcesuccess' for the time being.

Regards,
-Tony

From: Sarajärvi Tony
Sent: 21. toukokuuta 2013 13:07
To: development@qt-project.org
Subject: Builds failing due to android host

Hi

If your build failed due to this message Can not detect the android host. 
Please use -android-ndk-host option to specify one you can just safely restage 
it. We made changes to our Puppet configuration regarding Androids, and yes, 
the CI team caused this fail.

We have a small known problem with Puppet, that currently running builds don't 
prevent Puppet from running.
Due to this, Puppet could potentially remove compile tools from under the 
build. Also, when a build finishes, it reboots the machine. This reboot kills 
the Puppet process and everything it was doing currently. This is most likely 
what happened to Android tools. They were being upgraded to 64 bit tools, and 
on some machines Puppet was killed during this process.

It will automatically retry in 90 minutes (which is Puppet's current timeout). 
Thus at some point it will fix itself.

We have a change for this already inbound so that Puppet doesn't do this, but 
it's been incoming since February, so don't hold your breath ;)

-Tony




Tony Sarajärvi
Senior Software Designer
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
Mobile: +358 050 482 1416
http://qt.digia.com
| Bloghttp://blog.digia.com/ | Twitterhttps://twitter.com/digiaonline | 
LinkedInhttp://www.linkedin.com/company/5119 | 
YouTubehttp://www.youtube.com/digiaonline | 
Facebookhttp://www.facebook.com/digiaonline |
--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Builds failing due to android host

[Sarajärvi Tony]

We have always something coming ;) And we didn't realize that this could cause 
problems. We got a request to update the tool chain and we just did as 
requested. We should have tested this on the dev side, but we don't have the 
luxury of time on our side. From now on, we don't upgrade or update anything 
before verifying on the dev side.

-Tony

From: Shaw Andy
Sent: 22. toukokuuta 2013 11:32
To: Sarajärvi Tony; development@qt-project.org
Subject: RE: Builds failing due to android host

Maybe I missed something, but why are upgrades like this being done in the 
middle of a release cycle? With Qt 5.1 final due in not too long then shouldn't 
these kind of upgrades wait until after the final release in order to avoid 
this sort of thing being a problem for the release?

Andy

From: development-bounces+andy.shaw=digia@qt-project.org 
[mailto:development-bounces+andy.shaw=digia@qt-project.org] On Behalf Of 
Sarajärvi Tony
Sent: 22. mai 2013 10:27
To: development@qt-project.org
Subject: Re: [Development] Builds failing due to android host

Updating the NDK began causing new and new problems, so Android builds are 
marked as 'forcesuccess' for the time being.

Regards,
-Tony

From: Sarajärvi Tony
Sent: 21. toukokuuta 2013 13:07
To: development@qt-project.org
Subject: Builds failing due to android host

Hi

If your build failed due to this message Can not detect the android host. 
Please use -android-ndk-host option to specify one you can just safely restage 
it. We made changes to our Puppet configuration regarding Androids, and yes, 
the CI team caused this fail.

We have a small known problem with Puppet, that currently running builds don't 
prevent Puppet from running.
Due to this, Puppet could potentially remove compile tools from under the 
build. Also, when a build finishes, it reboots the machine. This reboot kills 
the Puppet process and everything it was doing currently. This is most likely 
what happened to Android tools. They were being upgraded to 64 bit tools, and 
on some machines Puppet was killed during this process.

It will automatically retry in 90 minutes (which is Puppet's current timeout). 
Thus at some point it will fix itself.

We have a change for this already inbound so that Puppet doesn't do this, but 
it's been incoming since February, so don't hold your breath ;)

-Tony




Tony Sarajärvi
Senior Software Designer
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
Mobile: +358 050 482 1416
http://qt.digia.com
| Bloghttp://blog.digia.com/ | Twitterhttps://twitter.com/digiaonline | 
LinkedInhttp://www.linkedin.com/company/5119 | 
YouTubehttp://www.youtube.com/digiaonline | 
Facebookhttp://www.facebook.com/digiaonline |
--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Builds failing due to android host

[Sarajärvi Tony]

Do we ever have a situation that something is not late into a release 
process? If it's not 5.1, it's 5.1.1, or 5.2 beta, or 5.2 RC, or 5.2.1...  not 
to mention our 4.x builds :)

-Tony

From: Shaw Andy
Sent: 22. toukokuuta 2013 12:42
To: Sarajärvi Tony; development@qt-project.org
Subject: RE: Builds failing due to android host

That doesn't make it a valid thing to still do, testing or not. I am not sure 
what others think but do we want to still do upgrades to things on CI this late 
into a release process?

Andy

From: Sarajärvi Tony
Sent: 22. mai 2013 10:54
To: Shaw Andy; development@qt-project.org
Subject: RE: Builds failing due to android host

We have always something coming ;) And we didn't realize that this could cause 
problems. We got a request to update the tool chain and we just did as 
requested. We should have tested this on the dev side, but we don't have the 
luxury of time on our side. From now on, we don't upgrade or update anything 
before verifying on the dev side.

-Tony

From: Shaw Andy
Sent: 22. toukokuuta 2013 11:32
To: Sarajärvi Tony; development@qt-project.org
Subject: RE: Builds failing due to android host

Maybe I missed something, but why are upgrades like this being done in the 
middle of a release cycle? With Qt 5.1 final due in not too long then shouldn't 
these kind of upgrades wait until after the final release in order to avoid 
this sort of thing being a problem for the release?

Andy

From: development-bounces+andy.shaw=digia@qt-project.org 
[mailto:development-bounces+andy.shaw=digia@qt-project.org] On Behalf Of 
Sarajärvi Tony
Sent: 22. mai 2013 10:27
To: development@qt-project.org
Subject: Re: [Development] Builds failing due to android host

Updating the NDK began causing new and new problems, so Android builds are 
marked as 'forcesuccess' for the time being.

Regards,
-Tony

From: Sarajärvi Tony
Sent: 21. toukokuuta 2013 13:07
To: development@qt-project.org
Subject: Builds failing due to android host

Hi

If your build failed due to this message Can not detect the android host. 
Please use -android-ndk-host option to specify one you can just safely restage 
it. We made changes to our Puppet configuration regarding Androids, and yes, 
the CI team caused this fail.

We have a small known problem with Puppet, that currently running builds don't 
prevent Puppet from running.
Due to this, Puppet could potentially remove compile tools from under the 
build. Also, when a build finishes, it reboots the machine. This reboot kills 
the Puppet process and everything it was doing currently. This is most likely 
what happened to Android tools. They were being upgraded to 64 bit tools, and 
on some machines Puppet was killed during this process.

It will automatically retry in 90 minutes (which is Puppet's current timeout). 
Thus at some point it will fix itself.

We have a change for this already inbound so that Puppet doesn't do this, but 
it's been incoming since February, so don't hold your breath ;)

-Tony




Tony Sarajärvi
Senior Software Designer
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
Mobile: +358 050 482 1416
http://qt.digia.com
| Bloghttp://blog.digia.com/ | Twitterhttps://twitter.com/digiaonline | 
LinkedInhttp://www.linkedin.com/company/5119 | 
YouTubehttp://www.youtube.com/digiaonline | 
Facebookhttp://www.facebook.com/digiaonline |
--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] qtbase CI now takes 6 hours

[Sarajärvi Tony]

Hi

I finally have some time to give you a proper answer :)

 -Original Message-
 From: Stephen Kelly [mailto:stephen.ke...@kdab.com]
 Sent: 17. toukokuuta 2013 10:34
 To: Sarajärvi Tony
 Cc: development@qt-project.org
 Subject: Re: [Development] qtbase CI now takes 6 hours
 
 On Friday, May 17, 2013 06:14:12 you wrote:
  Hi
 
  I'm responsible for keeping the CI up and running and having it stable. So
  in cases like this, you may point a finger at me and ask what's going on.
  Currently quite a few things, and I'll try to summarize here what's going
  on.
 
 Hi Tony,
 
 Thanks for responding. I have some follow-ups.
 
 1) Can you add the time taken to integrate to the report emails?

I think so. I haven't tested this, but I recon something like this would work.
Add these lines after line 1040 to the 'qt-jenkins-integrator.pl':

---
my $duration_in_seconds = $build-{ duration } / 1000;
my ($days,$hours,$minutes,$seconds) = (gmtime 
$duration_in_seconds)[7,2,1,0];
$hours += $days * 24;

$formatted .= \nDuration of build: $hours h, $minutes min, $seconds sec.;
---

That's a bit difficult to test, since our development version doesn't send 
emails at all. Guess I'd have to enable it or something.

 
 2) Can you notify this list when you know a CI blocker has been introduced?
 (like the improvements you mentioned which were held back until after beta1
 and which cause some problems, and the current network tests failing, which
 you might be aware of) That way we don't have to point a finger at you and ask
 what's going on.

I'll take this as a lesson learned. I'll try to keep you more up to speed on 
what's going on :)

 
 3) Can you disable staging when such problems occur, so that everyone knows
 that it won't work anyway?

I wished I could have done that, but I don't know how to do that. I'll 
investigate how that could be achieved. Same thing crossed my mind though.

 
 4) You say you're responsible for keeping CI up and running. Does that include
 keeping branches merging and keeping qt5.git up to date? If not, then as I
 wrote before I think we still need a better way of tracking that.

No. The CI team doesn't look or touch the content of the repos at all, not 
counting qtqa and sysadmin repos that include the tools which we keep up to 
date.

 
 5) It's quite easy to see when the integration failed due to cloning, and when
 it failed due to a problematic integration machine (eg macx-clang_developer-
 build_qtnamespace_OSX_10.7), or a network server issue. The problem is we
 don't really know if anything is being done to address some of those issues.
 Is anything being done about https://bugreports.qt-project.org/browse/QTBUG-
 30646 ? Either fixing the problems that are occuring
 on it, or disabling it in places where it still causes problems (qtbase and
 qtdeclarative)?

Flaky test cases are trouble, we know. We try to mark them as insignificant as 
we stumble upon them, although it's not exactly our job in the CI. We can't 
look into every failing build and look at the details behind it, and keep 
metrics of failing cases. For this we have created the QtMetrics web-page, 
which I will send an announcement of probably right after I answer you on this.

Who the person would then be to mark them as insignificant? I'm not quite sure. 
Sergio manually runs a script that marks them the other way around. If 
something passes and has been marked as insignificant, the script creates a 
task that removes that flag. This of course might create problems on Flaky 
tests that fail once every 10 builds. 

 
 6) I see that some Windows machines seems to be persistently failing in a way
 which reminds me of macx-clang_developer-build_qtnamespace_OSX_10.7. Are
 you
 aware of that/have it on your needs-fix radar?

Windows machines have a few problems that are persistent:

Windows 8 64bit and its cmd.exe problem is one: 
https://bugreports.qt-project.org/browse/QTQAINFRA-597. That one causes builds 
to just simply randomly fail. And we haven't found a root cause for that yet, 
nor are we actively looking for it either. We instead fix other problems that 
we currently do know how to fix.

Windows 8 64bit and shutdown.exe crashes at shutdown (no bug report). This 
causes our machines not to restart properly after a build has been completed. 
This makes the nodes go offline and builds that are in queue will never start 
building. Very annoying, and we have no idea what causes this randomly.

Then we had this Java issue last week. Apparently when we tried to upgrade our 
java from Update 7 to Update 17, Jenkins starts disconnecting the nodes. The 
disconnection happens seemingly at random. We had disconnects happening 
everywhere between 10 minutes to 3 hours in to the build. For some reason, 
Puppet didn't upgrade all the nodes to Update 17. Still, the ones remaining at 
U7 had problems as well. The only logical reason we found was, that the update 
had done something to the U7, but not completely

Re: [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@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
 

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Network test server for Ubuntu 12.04 x64 available for Puppet - test version

[Sarajärvi Tony]

Hi

For all you who have tried to install a network test server: a Puppet 
configuration for Ubuntu 12.04 x64 is now available.

It's still in my personal Gitorious branch, as it still needs testing before 
pushed through to production. Also I will flag these 12.04 changes so that we 
still have the 10.04 configuration left there.

All qtbase networkselftests passed with this, but there might still be 
something I missed in the configuration.
Tomorrow I'll reinstall a server from scratch using this myself to see what I 
might have missed.

https://qt.gitorious.org/~tosaraja/qtqa/tosarajas-sysadmin-nts

Send any feedback straight to me :)

Good luck!
-Tony

Tony Sarajärvi
Senior Software Designer
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
IRC: freenode - #qt-qa
Mobile: +358 050 482 1416
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Network test server for Ubuntu 12.04 x64 available for Puppet - test version

[Sarajärvi Tony]

Hi

Ah yes, I could have added the bootstrap, although it would just have been a 
copy of 11.10. I'm wondering why it didn't work for you. Is the log you refer 
to Puppet's log? Can you send it to me, and I'll have a look at it?

And yes, lots of documentation still need working on. I just bundled up all my 
changes I had done so far and gave it to you as soon as I got all needed 
services up and running. Of the pre-existing problems, I also worked on 
cleaning up the puppet log, so that it doesn't try to start the services on 
each puppet run.

Regards,
-Tony

From: shane.kea...@accenture.com [mailto:shane.kea...@accenture.com]
Sent: 24. huhtikuuta 2013 18:26
To: Sarajärvi Tony; development@qt-project.org
Subject: RE: [Development] Network test server for Ubuntu 12.04 x64 available 
for Puppet - test version

Hi Tony,

Thanks for working on this.
I found some issues so far:

You didn't add a bootstrap script for ubuntu 12.04
When using the 10.04 script, the file 
/etc/apt/sources.list.d/bootstrap-puppet.list is invalid, causing the script to 
abort.
When using the 11.10 script, it fills the log with Skipping because of failed 
dependencies, and Could not evaluate: Could not retrieve information from 
environment production source(s)

README.network_test_server.txt needs to be updated too.

The existing scripts have not worked for setting up network test server since 
the move from Nokia to Digia, so some of the failures may be due to this 
pre-existing problem.
--

From: development-bounces+shane.kearns=accenture@qt-project.org 
[mailto:development-bounces+shane.kearns=accenture@qt-project.org] On 
Behalf Of Sarajärvi Tony
Sent: 24 April 2013 13:33
To: development@qt-project.org
Subject: [Development] Network test server for Ubuntu 12.04 x64 available for 
Puppet - test version

Hi

For all you who have tried to install a network test server: a Puppet 
configuration for Ubuntu 12.04 x64 is now available.

It's still in my personal Gitorious branch, as it still needs testing before 
pushed through to production. Also I will flag these 12.04 changes so that we 
still have the 10.04 configuration left there.

All qtbase networkselftests passed with this, but there might still be 
something I missed in the configuration.
Tomorrow I'll reinstall a server from scratch using this myself to see what I 
might have missed.

https://qt.gitorious.org/~tosaraja/qtqa/tosarajas-sysadmin-nts

Send any feedback straight to me :)

Good luck!
-Tony

Tony Sarajärvi
Senior Software Designer
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
IRC: freenode - #qt-qa
Mobile: +358 050 482 1416
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--



This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited.

Where allowed by local law, electronic communications with Accenture and its 
affiliates, including e-mail and instant messaging (including content), may be 
scanned by our systems for the purposes of information security and assessment 
of internal compliance with Accenture policy.

__

www.accenture.comhttp://www.accenture.com
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Periodical digest from CI (04/2013)

[Sarajärvi Tony]

I believe you meant Win 7 with VS2010 and 64bit. And yes that cmake seems to be 
fixed. Took a while to verify since I managed to build the wrong sources twice 
;)

Thank you!

-Tony

-Original Message-
From: development-bounces+tony.sarajarvi=digia@qt-project.org 
[mailto:development-bounces+tony.sarajarvi=digia@qt-project.org] On Behalf 
Of Stephen Kelly
Sent: 12. huhtikuuta 2013 15:53
To: development@qt-project.org
Subject: Re: [Development] Periodical digest from CI (04/2013)

On Friday, April 12, 2013 12:36:45 Sarajärvi Tony wrote:
 If you have any concerns or questions regarding the CI or you just want to
 talk with us, you can find us in IRC (freenode / #qt or #qt-qa)

Is the issue with the cmake tests on Win8 64 bit resolved?

Thanks,

-- 
Stephen Kelly stephen.ke...@kdab.com | Software Engineer
KDAB (Deutschland) GmbH  Co.KG, a KDAB Group Company
www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090
KDAB - Qt Experts - Platform-Independent Software Solutions
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Periodical digest from CI (04/2013)

[Sarajärvi Tony]

When I googled for reasons, I found out that there are many. The obvious ones 
would be related to PATH, but that doesn't explain why it doesn't happen every 
time. Nor have I been able to fix the problem with changing the PATH.

I have since created 2 new setups. A windows 7 64bit and a windows 8 32 bit. 
Just as a try to narrow down the problem to either Win8 or the 64bit. Neither 
worked, since both of these two new computers pass and don't reproduce the 
problem.

Debugging this is hard. It's like quantum mechanics, try to look at something 
and you change the setup so that it doesn't reproduce. Because of this, I've 
set up a task for myself to just recreate Win8 64bit from scratch, and see if 
it still occurs.

-Tony

-Original Message-
From: development-bounces+tony.sarajarvi=digia@qt-project.org 
[mailto:development-bounces+tony.sarajarvi=digia@qt-project.org] On Behalf 
Of Thiago Macieira
Sent: 12. huhtikuuta 2013 17:52
To: development@qt-project.org
Subject: Re: [Development] Periodical digest from CI (04/2013)

On sexta-feira, 12 de abril de 2013 12.36.45, Sarajärvi Tony wrote:
 As the cmd.exe problem for our Windows 8 builds still exists, we set up two
 new servers just to narrow down the problem.

I've wondered about that one every time one of the builds fails after 
compiling everything because perl can't find cmd.exe.

How is that possible? Do you have any theories how that can happen? Did the 
build somehow erase cmd.exe during the build? Did PATH somehow get corrupted? 
Windows 8 bug?

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Periodical digest from CI (04/2013)

[Sarajärvi Tony]

Hi all!

Our CI team has been busy putting out small bush fires here and there. There's 
always something broken that needs fixing and investigating.

We have added more Windows and Mac machines to the CI system, so the build 
cycle should be a bit faster on those parts. However, we have had problems with 
our Git mirroring, causing builds to fail to the initial check-out. This is 
something that's under investigation right now.

The slow cycle implementation is happening. Difficult to give you estimates, 
but my priority one is getting this up and running ASAP.

We also have a new network test server on top of Ubuntu 12.04. It's currently 
being tested before taken into use. The puppet configuration is still not done 
for this, but we'll create it once we take it into production use. Hopefully 
you will also have less problems getting this new one up and running then.

As the cmd.exe problem for our Windows 8 builds still exists, we set up two new 
servers just to narrow down the problem. One Windows 7 64bit and one Windows 8 
32bit. However, we haven't been able to reproduce the problem in either of 
those. As a next step, we might just recreate the Windows 8 64bit computers 
from scratch and see if that helps.

If you have any concerns or questions regarding the CI or you just want to talk 
with us, you can find us in IRC (freenode / #qt or #qt-qa)

Regards,
-Tony

Tony Sarajärvi
Senior Software Designer
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
Mobile: +358 050 482 1416
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI was not working properly from last Thursday until yesterday 11.3.

[Sarajärvi Tony]

Hi

We had problems with Linuces and perhaps Macs since last Thursday up until 
yesterday (11.mar) noon. Puppet runs got stuck and took up all of the free CPU 
power. Puppet was fixed, but the situation got fixed only after each server 
re-ran Puppet AND rebooted so that the Puppet's that were stuck got killed. 
Now, if your build happened to run on such a server, it's possible that 
timeouts in test cases occurred, since Puppet pulled all the resources of the 
server. The problem has been fixed and I recommend running a re-run now on odd 
builds from that problematic period.

Regards,
-Tony

Tony Sarajärvi
Senior Software Designer
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
Mobile: +358 050 482 1416
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Periodical digest from CI

[Sarajärvi Tony]

Hi!

From time to time I'll be informing you, the community, about what's happening 
here at the CI. These posts will be informal and hopefully just give you some 
kind of idea what we are working on. Suggestions on what we should change and 
open discussion over the CI topic is encouraged.

I personally just started working here in the beginning of January, meaning 
I've had a lot of learning to do. I'm still trying to put all the pieces 
together on how things work in our CI. My contributions so far have been minor, 
but I'm hoping to soon get through somewhat larger changes.

So, what's been done since I started here? Well we have a lot of more hardware 
capacity set up. This means shorter CI cycles for everyone. We have also 
changed the build parameters so that they cover even more different setups. And 
we are still working on adding more stages as hardware capacity allows for this.

Automated release testing is something new that's coming. With these we are 
trying to ensure that the packages can be installed properly in different 
circumstances and the tools for that work. This will give you a better user 
experience as you don't stumble on problems on the first thing when you are 
trying to install Qt.

We are also working on making the build node updating more safe. The logic 
behind Puppet controlled runs is being changed so that the update process 
itself shouldn't break building. We also have a few ideas on how to track 
stability in general, so that problems trigger emails to us right away.

Then we are having quite much problems with Windows 8 machine builds resulting 
in Can't spawn cmd.exe. The root cause for these is still unknown, even 
though we have spent several days trying to figure this one out. Random breaks 
are the most tricky ones.

Also inbound we have more detailed statistics of builds where we try to 
centralize all build data to a public web page. We don't have any time 
estimates for this, but it's definitely something we would like to see created.

Sincerely,

-Tony


Tony Sarajärvi
Senior Software Designer
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
Mobile: +358 050 482 1416
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI system is temporarily down

[Sarajärvi Tony]

Hi all

The CI system is suffering from network configuration problems and is not 
working currently. The problem has been fixed, but it will take a moment for 
every computer to get updated.

Regards
-Tony

Tony Sarajärvi
Senior Software Designer
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
Mobile: +358 050 482 1416
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt CI team presentation

[Sarajärvi Tony]

Hi all!

A quick introduction of the Qt CI team in Digia.

Our team consists of 3 persons and we are divided on to two sites, Oulu and 
Tampere, Finland.
I (Tony Sarajärvi) work as the team Teach lead and my position is here in Oulu. 
If you can't decide who to contact in CI related matters, then I'm the one to 
contact.
Sitting beside me is Heikki Halmet. He is currently working on Puppet 
configurations, packaging and squish.
In Tampere we have Simo Fält, and he is currently working on fixing Jenkins 
stages and looking after Gerrit.

We are in no way confined to those tasks. Whenever we get a task done, we pick 
the next one from the board. Only our personal skills and the priority of the 
task define what we work with at any given time.

Our backlog is quite huge currently, so we have to prioritize. This means that 
your small bug or change might get left unhandled for quite some time even 
though it might only take a moment to fix. Contact me if something needs to be 
processed faster and I'll have a look if we can re-prioritize it. Currently we 
are working on getting the bugs out of the system and perhaps increase 
performance a bit before we add new features.

We also have the CI wiki page at https://qt-project.org/wiki/CI_Overview which 
I will try to keep up to date.

Best Regards
-Tony


Tony Sarajärvi
Senior Software Designer
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.saraja...@digia.commailto:tony.saraja...@digia.com
Mobile: +358 050 482 1416
http://qt.digia.com
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qtcommercialhttp://www.facebook.com/qtcommercial
Qt Twitter: www.twitter.com/qtcommercialhttp://www.twitter.com/qtcommercial

--
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development