Re: [Development] Current problems in CI
On 13 March 2014 10:06, Sarajärvi Tony tony.saraja...@digia.com wrote: Hi No ETA. There are quite a few problems in the autotest side. Just a minute ago the last try failed. Have to fix more... -Tony Thanks Tony. I guess we won't have it back now before Friday? Just getting a little concerned my printing changes won't make the beta after all... Cheers! John. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Current problems in CI
Torsdag 13. mars 2014 16.32.22 skrev John Layt: On 13 March 2014 10:06, Sarajärvi Tony tony.saraja...@digia.com wrote: Hi No ETA. There are quite a few problems in the autotest side. Just a minute ago the last try failed. Have to fix more... -Tony Thanks Tony. I guess we won't have it back now before Friday? Just getting a little concerned my printing changes won't make the beta after all... Looks like we're somewhat back on track. We got a first run for qtbase passing and hopefully start getting the backlog down. Thanks for bearing with us, there were quite a few things comming together making it hard to fix. The printing patches are going to be staged as one of the first things, as agreed. Now we still need to get the dev branch up and then Qt 4. Greetings, Frederik Cheers! John. -- Best regards, Frederik Gladhorn Senior Software Engineer - Digia, Qt Visit us on: http://qt.digia.com ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Current problems in CI
On 13 March 2014 18:08, Frederik Gladhorn frederik.gladh...@digia.com wrote: Torsdag 13. mars 2014 16.32.22 skrev John Layt: On 13 March 2014 10:06, Sarajärvi Tony tony.saraja...@digia.com wrote: Hi No ETA. There are quite a few problems in the autotest side. Just a minute ago the last try failed. Have to fix more... -Tony Thanks Tony. I guess we won't have it back now before Friday? Just getting a little concerned my printing changes won't make the beta after all... Looks like we're somewhat back on track. We got a first run for qtbase passing and hopefully start getting the backlog down. Thanks for bearing with us, there were quite a few things comming together making it hard to fix. The printing patches are going to be staged as one of the first things, as agreed. That's good news. Thanks to the team for all the hard work getting it sorted out, I know it can't be easy keeping it running with us devs constantly changing things :-) I'll be here all night if anything goes astray with my changes... Cheers! John. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Current problems in CI
On 13 March 2014 18:21, John Layt jl...@kde.org wrote: On 13 March 2014 18:08, Frederik Gladhorn frederik.gladh...@digia.com wrote: Looks like we're somewhat back on track. We got a first run for qtbase passing and hopefully start getting the backlog down. Thanks for bearing with us, there were quite a few things comming together making it hard to fix. The printing patches are going to be staged as one of the first things, as agreed. That's good news. Thanks to the team for all the hard work getting it sorted out, I know it can't be easy keeping it running with us devs constantly changing things :-) I'll be here all night if anything goes astray with my changes... And inevitably the iOS build went astray... I now have a patch to fix the QT_NO_PRINTER build for this set of changes and other breakages from earlier code. I've done it as an extra change at https://codereview.qt-project.org/#change,80901 to save having to reset the approval status of all the other changes so anyone can approve just this small change and we can push the whole lot again. If someone can approve I'd be grateful, otherwise I can abuse my maintainer privilege later to push it through overnight. Remind me later to find out why we even bother trying to build the module and plugins if QT_NO_PRINTER is set, it has to be smarter than having every file wrapped in ifdefs. Cheers! John. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Current problems in CI
On 13/03/14 21:14, John Layt jl...@kde.org wrote: On 13 March 2014 18:21, John Layt jl...@kde.org wrote: On 13 March 2014 18:08, Frederik Gladhorn frederik.gladh...@digia.com wrote: Looks like we're somewhat back on track. We got a first run for qtbase passing and hopefully start getting the backlog down. Thanks for bearing with us, there were quite a few things comming together making it hard to fix. The printing patches are going to be staged as one of the first things, as agreed. That's good news. Thanks to the team for all the hard work getting it sorted out, I know it can't be easy keeping it running with us devs constantly changing things :-) I'll be here all night if anything goes astray with my changes... And inevitably the iOS build went astray... I now have a patch to fix the QT_NO_PRINTER build for this set of changes and other breakages from earlier code. I've done it as an extra change at https://codereview.qt-project.org/#change,80901 to save having to reset the approval status of all the other changes so anyone can approve just this small change and we can push the whole lot again. If someone can approve I'd be grateful, otherwise I can abuse my maintainer privilege later to push it through overnight. Remind me later to find out why we even bother trying to build the module and plugins if QT_NO_PRINTER is set, it has to be smarter than having every file wrapped in ifdefs. Looks good. Cheers, Lars ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Current problems in CI
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
Re: [Development] Current problems in CI
On 12 March 2014 11:08, Sarajärvi Tony tony.saraja...@digia.com wrote: 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. Hi Tony, Thanks for your work on this, and sorry to nag, but do we have an ETA for this? Thanks! John. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
