Re: [Development] CI for QNX 6.5.0
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] Certificate expires soon, new one ordered
Sigh. It looks like some of the tests are using qt-project.org even though
they aren't supposed to:
void
tst_QSslSocket_onDemandCertificates_member::onDemandRootCertLoadingMemberMethods()
{
QString host("qt-project.org");
// not using any root certs -> should not work
QSslSocketPtr socket2 = newSocket();
this->socket = socket2.data();
socket2->setCaCertificates(QList());
socket2->connectToHostEncrypted(host, 443);
QVERIFY(!socket2->waitForEncrypted());
Grr.
Rich.
On 26 January 2015 at 20:54, Richard Moore wrote:
>
>
> On 26 January 2015 at 19:28, Marc Mutz wrote:
>
>> I guess that's the reason why no integration succeeds in qtbase atm
>> (always
>> some ssl test error)?
>>
>> If so, it might be a good idea to suspend qtbase integration tasks until
>> it's
>> fixed, unless people like to have it running as a compilation oracle...
>>
>
> The network test server doesn't depend on the qt-project cert.
>
> Rich.
>
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Certificate expires soon, new one ordered
On 26 January 2015 at 19:28, Marc Mutz wrote: > I guess that's the reason why no integration succeeds in qtbase atm (always > some ssl test error)? > > If so, it might be a good idea to suspend qtbase integration tasks until > it's > fixed, unless people like to have it running as a compilation oracle... > The network test server doesn't depend on the qt-project cert. Rich. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[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 smime.p7s Description: S/MIME cryptographic signature ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Certificate expires soon, new one ordered
On Friday 23 January 2015 15:03:44 Turunen Tuukka wrote: > Hi, > > *.qt-project.org certificate will expire 25th Jan. New one is ordered, but > will take a bit more time to be in use. I guess that's the reason why no integration succeeds in qtbase atm (always some ssl test error)? If so, it might be a good idea to suspend qtbase integration tasks until it's fixed, unless people like to have it running as a compilation oracle... Thanks, Marc -- Marc Mutz | Senior 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
[Development] NOTE: Gerrit maintenance break on Jan-27 (RE: NOTE: Gerrit server update)
Hi, Gerrit upgrade rescheduled for next Tuesday morning, Jan-27, starting 07:00 CET. Estimate for down time is max three hours. BR, Ismo From: development-bounces+ismo.haataja=theqtcompany@qt-project.org [mailto:development-bounces+ismo.haataja=theqtcompany@qt-project.org] On Behalf Of Haataja Ismo Sent: 16. tammikuuta 2015 16:05 To: development@qt-project.org Subject: [Development] NOTE: Gerrit server update Hi, Gerrit server will change to new location during week 4. URL remains unchanged (https://codereview.qt-project.org/). Also some fixes will be deployed: https://bugreports.qt.io/browse/QTQAINFRA-874 https://bugreports.qt.io/browse/QTQAINFRA-892 https://bugreports.qt.io/browse/QTQAINFRA-905 https://bugreports.qt.io/browse/QTQAINFRA-906 https://bugreports.qt.io/browse/QTQAINFRA-909 Cheers, Ismo Haataja ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Running Qt 5.4.0 Applicationat Mac 10.6
Dear Morten, Thank you very much! Sincerely, Robert On Mon, Jan 26, 2015 at 10:53 AM, Sorvig Morten < morten.sor...@theqtcompany.com> wrote: > > > On 26 Jan 2015, at 09:09, Robert Iakobashvili > wrote: > > > > It seems that QStyle returns 0. > > > > Should I create some style in advance and pass it to application? > > Which style could be appropriate for 10.6? > > > > Yes, I know that 10.6 is not a supported target for 5.4.0, > > but any advise or direction would be very much appreciated. > > > > Thank you in advance. > > The code paths that provide 10.6 support have been removed from Qt 5.4. > The commits I am aware of are: > > a198ce8d (QMacStyle) > fc11798e8 (QMacStyle) > 9c92a18b (QCoreWLanEngine) > > You could use the fusion style to avoid QMacStyle, but there would still > be no guarantee that the application runs. Your other option then is to > revert the changes that removes 10.6 support on your local copy of the Qt > source code. > > Morten ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Running Qt 5.4.0 Applicationat Mac 10.6
> On 26 Jan 2015, at 09:09, Robert Iakobashvili wrote: > > It seems that QStyle returns 0. > > Should I create some style in advance and pass it to application? > Which style could be appropriate for 10.6? > > Yes, I know that 10.6 is not a supported target for 5.4.0, > but any advise or direction would be very much appreciated. > > Thank you in advance. The code paths that provide 10.6 support have been removed from Qt 5.4. The commits I am aware of are: a198ce8d (QMacStyle) fc11798e8 (QMacStyle) 9c92a18b (QCoreWLanEngine) You could use the fusion style to avoid QMacStyle, but there would still be no guarantee that the application runs. Your other option then is to revert the changes that removes 10.6 support on your local copy of the Qt source code. Morten ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QSystemTrayIcon label (so-called title) on OS X
On Monday 26 January 2015, Ilya Kowalewski wrote: > The label itself has nothing to do with messages or notifications. As you > can see on the screenshot, it's informative string assigned to the icon > itself. A possible usecase I keep in mind is to display number of unread > messages there (for a messaging application). Adding this to public API is > absolutely fine to me, but as far as I understood from what Thiago said, > this won't get accepted, since it's a platform-wise feature, not available > on other platforms. > That still sounds like the primary notification to me. Note that we sometimes also replace systemtray icon with the most recent notifications icon, since we can't show arbitrary icons in notifications currently. Alternatively you could consider it a different way of showing the tooltip, and set it that way, unless you need a separate string there. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Running Qt 5.4.0 Applicationat Mac 10.6
Hello, Qt-5.4.0 was built from sources at 10.9 build machine with flag -no-c++11 and in qtbase/mkspecs/macx-clang/qmake.conf was set: QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.6 The application does run at 10.6 target but crashes: Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x Crashed Thread: 0 Dispatch queue: com.apple.main-thread Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 org.qt-project.QtWidgets0x000100fcb762 0x100fbe000 + 55138 1 org.qt-project.QtWidgets0x0001010589f5 QStyleFactory::create(QString const&) + 181 2 org.qt-project.QtWidgets0x000100fec2d2 QApplication::style() + 370 3 org.qt-project.QtWidgets0x000100feb624 QApplicationPrivate::initializ e() + 100 4 org.qt-project.QtWidgets0x000100feb460 QApplicationPrivate::construct() + 96 5 com.mydomain.MyApp 0x0001b7b9 main + 41 6 com.mydomain.MyApp 0x00015e74 start + 52 It seems that QStyle returns 0. Should I create some style in advance and pass it to application? Which style could be appropriate for 10.6? Yes, I know that 10.6 is not a supported target for 5.4.0, but any advise or direction would be very much appreciated. Thank you in advance. Regards, Robert ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
