Re: [Development] QML Audio on Android
On Thu, 2014-02-06 at 00:41 +0100, Bruno Coudoin wrote: Should I report a bug for these? Another test on Android (Nexus 5 / 4.4.2) with a different set of issues: - The Audio are auto played by defaults, even if we force autoPlay to false - The ogg vorbis sound plays fine - It is not possible to control the volume once the application is started. Yes, please report those issues as bugs and post the links here. I'd like to follow the progress as well. All in all multimedia on Android still seems to be quite buggy. Had some issues with videos as well. Cheers, Conny ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Removing MSVC2008 from the CI build farm?
In addition, it’s still required for WinCE. I don’t think we can remove 2008 just yet. Cheers, Lars From: Chris Colbert sccolb...@gmail.commailto:sccolb...@gmail.com Date: Thursday 6 February 2014 02:28 To: Thiago Macieira thiago.macie...@intel.commailto:thiago.macie...@intel.com Cc: development@qt-project.orgmailto:development@qt-project.org development@qt-project.orgmailto:development@qt-project.org Subject: Re: [Development] Removing MSVC2008 from the CI build farm? There are still some very large enterprise users running on vc2008 build systems. Would this mean that all hope for building new releases on vc2008 would be lost, or that it just may take more effort than normal? As it stands, I had to apply some manual fixes to get 5.1 to build with vc2008, but it wasn't the end of the world. My $0.02 is that it may be a year or two too early to completely kick vc2008. After all, it's still the compiler which ships with the Windows 7 .NET 3.5 SDK... On Wed, Feb 5, 2014 at 11:50 AM, Thiago Macieira thiago.macie...@intel.commailto:thiago.macie...@intel.com wrote: Hello guys Is it maybe time to get rid of MSVC 2008 from our build farm? Do the new versions support wince builds? c:\work\build\qt\qtbase\tests\auto\corelib\global\qtendian\tst_qtendian.cp p(140) : fatal error C1001: An internal error has occurred in the compiler. Build log: http://testresults.qt-project.org/ci/QtBase_dev_Integration/build_02794/w ince70embedded-armv4i-msvc2008_Windows_7/log.txt.gz -- Thiago Macieira - thiago.macieira (AT) intel.comhttp://intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.orgmailto: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] Bug fixes to Stable or Dev branch?
On Wednesday 05 February 2014 17:45:35 Turunen Tuukka wrote: Hi, Regarding Qt 5.2.2 - let's see how well 5.2.1 is received. We have now 1,5 months shorter cycle than the usual 6 months for Qt 5.3. I agree that it was a long wait between 5.1.1 and 5.2.0. FWIW with my Canonical hat we would appreciate a 5.2.x release with https://bugreports.qt-project.org/browse/QTBUG-36430 and https://bugreports.qt-project.org/browse/QTBUG-36289 fixed. We can distro- patch but having it in an official release makes it easier for everyone. Cheers, Albert Yours, Tuukka Lähettäjä: development-bounces+tuukka.turunen=digia@qt-project.org [development-bounces+tuukka.turunen=digia@qt-project.org] k#228;ytt#228;j#228;n Gladhorn Frederik [frederik.gladh...@digia.com] puolesta Lähetetty: 5. helmikuuta 2014 17:46 Vastaanottaja: development@qt-project.org Aihe: Re: [Development] Bug fixes to Stable or Dev branch? We have the branch model to make it easy to choose the right branch, usually without worrying about the releases too much. Normal bug fixes go always to stable. Stable is guaranteed to be merged into dev before the next release, so you'll never have to worry, no patch gets lost. Show stoppers just before the release might have to go into the release branch, this should really be the exception. Sometimes a bug is less critical and/or involves huge changes, these may have to go into the dev branch pending the approvers and your judgement. By the way, I heard quite a few requests for more patch releases, maybe we should aim for 5.2.2 with hopefully only stability improvements. Greetings, Frederik From: development-bounces+frederik.gladhorn=digia@qt-project.org [development-bounces+frederik.gladhorn=digia@qt-project.org] on behalf of Giuseppe D'Angelo [dange...@gmail.com] Sent: Wednesday, February 05, 2014 4:19 PM To: jl...@kde.org Cc: development@qt-project.org Subject: Re: [Development] Bug fixes to Stable or Dev branch? On 5 February 2014 15:55, John Layt jl...@kde.org wrote: Hi, I've seeing contradictory advice on Gerrit as to which branch to push bug- fixes to, some say there will be no 5.2.2 so to use dev instead, others say to keep using stable in case there is. What is the current official policy? Oh, and please remember when making such decisions to clearly communicate them to this list, not everyone is in the office or on IRC. The policy didn't change, see Where to push a change? http://qt-project.org/wiki/Branch-Guidelines It doesn't matter that 5.2.2 is not planned. If the change qualifies for stable, push it to stable. -- Giuseppe D'Angelo ___ 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] Removing MSVC2008 from the CI build farm?
No bad idea, 2008 is the last version supporting anything older than the new WEC2013 which we don't support yet, so its not likely to drop in the comming years without dropping CE support too. -- Björn Breitmeyer | bjoern.breitme...@kdab.com | Software Engineer KDAB (Deutschland) GmbHCo KG, a KDAB Group company Germany: +49-30-521325470, Sweden (HQ): +46-563-540090 KDAB - Qt Experts - Platform-independent software solutions Am Mittwoch, 5. Februar 2014, 08:50:10 schrieb Thiago Macieira: Hello guys Is it maybe time to get rid of MSVC 2008 from our build farm? Do the new versions support wince builds? c:\work\build\qt\qtbase\tests\auto\corelib\global\qtendian\tst_qtendian. cp p(140) : fatal error C1001: An internal error has occurred in the compiler. Build log: http://testresults.qt-project.org/ci/QtBase_dev_Integration/build_02794/ w ince70embedded-armv4i-msvc2008_Windows_7/log.txt.gz smime.p7s Description: S/MIME cryptographic signature ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] CI broken again?
CI continues to fail during build AND tests at seemingly random places. Any idea whats going on or when it'll be fixed? -mandeep On Wed, Feb 5, 2014 at 3:17 PM, Mandeep Sandhu mandeepsandhu@gmail.comwrote: Something similar happened to me too on the dev branch. Tried merging a change. First a test case failed (tst_QDnsLookup) even though it runs fine on my local setup. I tried re-staging the change but now I got some merge errors. Local update of dev and rebase worked. -mandeep On Wed, Feb 5, 2014 at 2:50 PM, BogDan bog_dan...@yahoo.com wrote: Hello, I'm trying for two days to merge this https://codereview.qt-project.org/77207 patch, but CI doesn't like me. It is a know issue or just me? Should I wait for other patches to be merged before I'll try the 8th time? :) 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] CI broken again?
Em qui 06 fev 2014, às 14:28:52, Mandeep Sandhu escreveu: CI continues to fail during build AND tests at seemingly random places. Any idea whats going on or when it'll be fixed? It's normal operating procedure. Some tests are flaky and are known to cause issues every now and then. 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. -- 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] To patch release or not (was: Bug fixes to Stable or Dev branch?)
Hi Tuukka and all, just like Albert said, it's not so much about the time until the next release. It's more about delivering even more stable Qt releases with less changes that are more reliable. While I generally think that we are doing quite a good job in improving the quality of Qt with both minor and patch releases, some people really appreciate releases with those few bug fixes like Albert mentioned. Looking at the stable branch it seems like there are 116 commits for qtbase alone in the stable branch. I have heard from quite a few people that they would really appreciate those patch releases and ideally we get into the habit of making releases so smooth that it doesn't cost any extra effort. (we're not quite there but getting better and better at making releases) Greetings, Frederik (forgive me for top posting, I'm on a broken web mail client here...) From: Turunen Tuukka Sent: Wednesday, February 05, 2014 6:45 PM To: Gladhorn Frederik; development@qt-project.org Subject: VS: [Development] Bug fixes to Stable or Dev branch? Hi, Regarding Qt 5.2.2 - let's see how well 5.2.1 is received. We have now 1,5 months shorter cycle than the usual 6 months for Qt 5.3. I agree that it was a long wait between 5.1.1 and 5.2.0. Yours, Tuukka Lähettäjä: development-bounces+tuukka.turunen=digia@qt-project.org [development-bounces+tuukka.turunen=digia@qt-project.org] k#228;ytt#228;j#228;n Gladhorn Frederik [frederik.gladh...@digia.com] puolesta Lähetetty: 5. helmikuuta 2014 17:46 Vastaanottaja: development@qt-project.org Aihe: Re: [Development] Bug fixes to Stable or Dev branch? We have the branch model to make it easy to choose the right branch, usually without worrying about the releases too much. Normal bug fixes go always to stable. Stable is guaranteed to be merged into dev before the next release, so you'll never have to worry, no patch gets lost. Show stoppers just before the release might have to go into the release branch, this should really be the exception. Sometimes a bug is less critical and/or involves huge changes, these may have to go into the dev branch pending the approvers and your judgement. By the way, I heard quite a few requests for more patch releases, maybe we should aim for 5.2.2 with hopefully only stability improvements. Greetings, Frederik From: development-bounces+frederik.gladhorn=digia@qt-project.org [development-bounces+frederik.gladhorn=digia@qt-project.org] on behalf of Giuseppe D'Angelo [dange...@gmail.com] Sent: Wednesday, February 05, 2014 4:19 PM To: jl...@kde.org Cc: development@qt-project.org Subject: Re: [Development] Bug fixes to Stable or Dev branch? On 5 February 2014 15:55, John Layt jl...@kde.org wrote: Hi, I've seeing contradictory advice on Gerrit as to which branch to push bug- fixes to, some say there will be no 5.2.2 so to use dev instead, others say to keep using stable in case there is. What is the current official policy? Oh, and please remember when making such decisions to clearly communicate them to this list, not everyone is in the office or on IRC. The policy didn't change, see Where to push a change? http://qt-project.org/wiki/Branch-Guidelines It doesn't matter that 5.2.2 is not planned. If the change qualifies for stable, push it to stable. -- Giuseppe D'Angelo ___ 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] CI broken again?
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? -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
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
Re: [Development] CI broken again?
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] To patch release or not (was: Bug fixes to Stable or Dev branch?)
Hi, I have nothing against patch releases, on the contrary ;) If there is good content to go out as Qt 5.2.2 / Creator 3.0.2 for example in beginning of March - and we believe it is possible to create such a release without risking Qt 5.3 schedule - I¹m all for it. I would assume this is a topic release team will discuss on their Monday meetings. ‹ Tuukka On 06/02/14 11:39, Gladhorn Frederik frederik.gladh...@digia.com wrote: Hi Tuukka and all, just like Albert said, it's not so much about the time until the next release. It's more about delivering even more stable Qt releases with less changes that are more reliable. While I generally think that we are doing quite a good job in improving the quality of Qt with both minor and patch releases, some people really appreciate releases with those few bug fixes like Albert mentioned. Looking at the stable branch it seems like there are 116 commits for qtbase alone in the stable branch. I have heard from quite a few people that they would really appreciate those patch releases and ideally we get into the habit of making releases so smooth that it doesn't cost any extra effort. (we're not quite there but getting better and better at making releases) Greetings, Frederik (forgive me for top posting, I'm on a broken web mail client here...) From: Turunen Tuukka Sent: Wednesday, February 05, 2014 6:45 PM To: Gladhorn Frederik; development@qt-project.org Subject: VS: [Development] Bug fixes to Stable or Dev branch? Hi, Regarding Qt 5.2.2 - let's see how well 5.2.1 is received. We have now 1,5 months shorter cycle than the usual 6 months for Qt 5.3. I agree that it was a long wait between 5.1.1 and 5.2.0. Yours, Tuukka Lähettäjä: development-bounces+tuukka.turunen=digia@qt-project.org [development-bounces+tuukka.turunen=digia@qt-project.org] k#228;ytt#228;j#228;n Gladhorn Frederik [frederik.gladh...@digia.com] puolesta Lähetetty: 5. helmikuuta 2014 17:46 Vastaanottaja: development@qt-project.org Aihe: Re: [Development] Bug fixes to Stable or Dev branch? We have the branch model to make it easy to choose the right branch, usually without worrying about the releases too much. Normal bug fixes go always to stable. Stable is guaranteed to be merged into dev before the next release, so you'll never have to worry, no patch gets lost. Show stoppers just before the release might have to go into the release branch, this should really be the exception. Sometimes a bug is less critical and/or involves huge changes, these may have to go into the dev branch pending the approvers and your judgement. By the way, I heard quite a few requests for more patch releases, maybe we should aim for 5.2.2 with hopefully only stability improvements. Greetings, Frederik From: development-bounces+frederik.gladhorn=digia@qt-project.org [development-bounces+frederik.gladhorn=digia@qt-project.org] on behalf of Giuseppe D'Angelo [dange...@gmail.com] Sent: Wednesday, February 05, 2014 4:19 PM To: jl...@kde.org Cc: development@qt-project.org Subject: Re: [Development] Bug fixes to Stable or Dev branch? On 5 February 2014 15:55, John Layt jl...@kde.org wrote: Hi, I've seeing contradictory advice on Gerrit as to which branch to push bug- fixes to, some say there will be no 5.2.2 so to use dev instead, others say to keep using stable in case there is. What is the current official policy? Oh, and please remember when making such decisions to clearly communicate them to this list, not everyone is in the office or on IRC. The policy didn't change, see Where to push a change? http://qt-project.org/wiki/Branch-Guidelines It doesn't matter that 5.2.2 is not planned. If the change qualifies for stable, push it to stable. -- Giuseppe D'Angelo ___ 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] CI broken again?
Em qui 06 fev 2014, às 12:54:59, Sarajärvi Tony escreveu: 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. That's normal. We get as many bytes as FIONREAD tells us that are available. The only requirement is that we get a new read activation on select the next time around, which we will. -- 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] CI broken again?
Em qui 06 fev 2014, às 16:01:05, Mandeep Sandhu escreveu: 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). That doesn't mean anything. The difference might be the type of DNS servers available. For example, I wrote a QDnsLookup test that tried to query a record containing multiple RR types. It passed on my machine. But on the CI farm, the DNS server is too nice and sends more information than the DNS request really asked for, causing the test to fail. It's not a CI farm problem. It's a problem with the test I wrote. I don't know what your change caused of problems. But if the tst_QDnsLookup failure happened four times exactly the same way when that change was staged, I'm calling that change the culprit. Maybe your code doesn't have a bug and this is a problem in the server, maybe it does have a bug you haven't thought of, but either way your change causes the test to fail in the farm. You need to modify the test so it doesn't fail. 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? Yes, but it's unlikely to be the case. The only times that tst_QDnsLookup has failed in the past 6 months are when your change was staged. The correlation factor is way too high. -- 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] To patch release or not (was: Bug fixes to Stable or Dev branch?)
Em qui 06 fev 2014, às 09:39:23, Gladhorn Frederik escreveu: just like Albert said, it's not so much about the time until the next release. It's more about delivering even more stable Qt releases with less changes that are more reliable. While I generally think that we are doing quite a good job in improving the quality of Qt with both minor and patch releases, some people really appreciate releases with those few bug fixes like Albert mentioned. Looking at the stable branch it seems like there are 116 commits for qtbase alone in the stable branch. See the big green area at the right side: http://www.macieira.org/~thiago/qt-stats/current/qt.branch.absolute.png I have heard from quite a few people that they would really appreciate those patch releases and ideally we get into the habit of making releases so smooth that it doesn't cost any extra effort. (we're not quite there but getting better and better at making releases) We should consider making releases of 5.2.x after 5.3's alpha even. 5.3.0 is some 3 months away. -- 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] QtDBus in official Windows and OSX installers
Em qui 06 fev 2014, às 17:28:40, Roland Winklmeier escreveu: But my main question is, is there a chance QtDBus is shipped officially and what needs to be done for that. I guess one point is to run the dbus unit tests, but what else needs to be done to ship it at least in an experimental state? Or is the answer just No, this will never happen? It should already be included in the Mac installers. If it isn't, it's a regression bug and needs to be fixed. For Windows, I don't know. I know configure.exe can enable D-Bus, but I've never even tried, so I don't know what it takes. -- 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] CI broken again?
On Thu, Feb 6, 2014 at 10:10 PM, Thiago Macieira thiago.macie...@intel.comwrote: Em qui 06 fev 2014, às 16:01:05, Mandeep Sandhu escreveu: 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). That doesn't mean anything. The difference might be the type of DNS servers available. For example, I wrote a QDnsLookup test that tried to query a record containing multiple RR types. It passed on my machine. But on the CI farm, the DNS server is too nice and sends more information than the DNS request really asked for, causing the test to fail. It's not a CI farm problem. It's a problem with the test I wrote. I don't know what your change caused of problems. But if the tst_QDnsLookup failure happened four times exactly the same way when that change was staged, I'm calling that change the culprit. Maybe your code doesn't have a bug and this is a problem in the server, maybe it does have a bug you haven't thought of, but either way your change causes the test to fail in the farm. You need to modify the test so it doesn't fail. 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? Yes, but it's unlikely to be the case. The only times that tst_QDnsLookup has failed in the past 6 months are when your change was staged. The correlation factor is way too high. Ok, I'll dig in more into this problem. IF only I could replicate it somehow, it'll be that much easier to fix! :/ -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
Re: [Development] CI broken again?
Em qui 06 fev 2014, às 22:39:29, Mandeep Sandhu escreveu: Ok, I'll dig in more into this problem. IF only I could replicate it somehow, it'll be that much easier to fix! :/ If there's more debugging that could help you, you can modify the change to add it to the test and we'll stage it during the night. Then you'll have more info to work with. Richard and I did exactly that for the QSslSocket::setCiphers change that was failing for unknown reasons. And then the change with the debugging integrated, passing the test... -- 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] Build Hotspots in the Qt build process
Hi Thiago, On Feb 5, 2014, at 6:18 PM, Thiago Macieira thiago.macie...@intel.com wrote: Em qua 05 fev 2014, às 11:58:50, Simon Hausmann escreveu: I'm with Simon, this is very interesting stuff! Thank you! :-) I'm wondering if we could make use of your data to figure out what headers we should precompile. This is a fascinating idea actually. We primarily motivate our work based on refactoring, but as you mentioned, some really hot files just cannot be refactored due to architectural concerns. Perhaps precompiling the hot headers is another way these hotspots can be addressed. You said you extract a graph from the build: is there a way to parse that graph to produce a list of headers most commonly included in a given module? Yes, this should be possible. Within our graph, each header file is a node that is connected by an edge to each object file (another node) that needs to be recompiled when the header changes. A simple measure like the sum of all the edges coming out of a header file will tell you how many objects are recompiled when it changes, which is a kind of proxy for the number of files including a header. We've had precompilation support in qmake for a decade, but apparently we use that in exactly 3 modules... Hmm, it could also be interesting to look into these modules to see if having them precompiled is justified by its hotness? Kind regards, -Shane ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Build Hotspots in the Qt build process
Em qui 06 fev 2014, às 18:37:43, Shane McIntosh escreveu: We've had precompilation support in qmake for a decade, but apparently we use that in exactly 3 modules... Hmm, it could also be interesting to look into these modules to see if having them precompiled is justified by its hotness? Well, think of me. I'm the QtCore maintainer. Every time I change qstring.h or qbasicatomic.h, EVERYTHING recompiles. Not even ccache can help me there. So if I can get stuff precompiled, it should be a win. The very least we can do is auto precompilation: for every Qt module, we know which modules it depends on, so we could generate a precompile header that #includes the dependent's master header. But I was hoping for the next step: which headers of the *current* module are most in need of precompilation. For example, almost everything in QtWidgets will #include qwidget.h. -- 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] Windows Online Installer problem(s)
On 05/02/14 20:12, Heikkinen Jani wrote: Hi all, When did you tried that online installation? On the 5th of February (few hours before sending the email). Chris Br, Jani -Original Message- From: development-bounces+jani.heikkinen=digia@qt-project.org [mailto:development-bounces+jani.heikkinen=digia@qt-project.org] On Behalf Of Christian Gagneraud Sent: 5. helmikuuta 2014 4:03 To: development@qt-project.org Subject: [Development] Windows Online Installer problem(s) Hi there, I tried to install Qt with the latest official online installer on a Windows computer [1], and I couldn't install it on the 'D' disk, because the 'C' disk didn't have enough space to store the downloaded data (I guess in the system temp dir, which is likely to be on c:) Another annoying (but non blocking) problem I had was a hash mismatch on one of the Android component, the work around in my case was simply to unselect the 2 android components via the settings dialogue. I tried to re-run the installer 3 times, and 3 times I had a hash mismatch, so the problem seems to be on the server side. I ended up installing Qt using the offline installer. Chris [1] http://download.qt-project.org/official_releases/online_installers/1.5/qt- windows-opensource-1.5.0-x86-online.exe ___ 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] Windows Online Installer problem(s)
On 05/02/14 20:12, Heikkinen Jani wrote: Hi all, When did you tried that online installation? I just checked the Windows computer and this was Qt 5.2.0, not 5.2.1. Chris Br, Jani -Original Message- From: development-bounces+jani.heikkinen=digia@qt-project.org [mailto:development-bounces+jani.heikkinen=digia@qt-project.org] On Behalf Of Christian Gagneraud Sent: 5. helmikuuta 2014 4:03 To: development@qt-project.org Subject: [Development] Windows Online Installer problem(s) Hi there, I tried to install Qt with the latest official online installer on a Windows computer [1], and I couldn't install it on the 'D' disk, because the 'C' disk didn't have enough space to store the downloaded data (I guess in the system temp dir, which is likely to be on c:) Another annoying (but non blocking) problem I had was a hash mismatch on one of the Android component, the work around in my case was simply to unselect the 2 android components via the settings dialogue. I tried to re-run the installer 3 times, and 3 times I had a hash mismatch, so the problem seems to be on the server side. I ended up installing Qt using the offline installer. Chris [1] http://download.qt-project.org/official_releases/online_installers/1.5/qt- windows-opensource-1.5.0-x86-online.exe ___ 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] QtDBus in official Windows and OSX installers
Am 06.02.2014 18:02, schrieb Thiago Macieira: Em qui 06 fev 2014, às 17:28:40, Roland Winklmeier escreveu: But my main question is, is there a chance QtDBus is shipped officially and what needs to be done for that. I guess one point is to run the dbus unit tests, but what else needs to be done to ship it at least in an experimental state? Or is the answer just No, this will never happen? It should already be included in the Mac installers. If it isn't, it's a regression bug and needs to be fixed. For Windows, I don't know. I know configure.exe can enable D-Bus, but I've never even tried, so I don't know what it takes. I haven't checked earlier versions but at least Qt 5.2.1 Mac OSX Clang64 (both online and offline) do not contain any QtDBus modules. I'm wondering how this would be done anyway, should dbus-daemon be shipped with the installer or installed manually? Building for windows is pretty easy. Make sure dbus/dbus.h is in your include path and enable it configure -dbus. Builds and runs fine. --- Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz ist aktiv. http://www.avast.com ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] CI fails because a memory isn't allocated
Hello! I've tried to merge the patch https://codereview.qt-project.org/72692, but CI fails. There is a line in logs: cc1plus.exe: out of memory allocating 408 bytes How may it be fixed? Thank you! ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Build Hotspots in the Qt build process
Shane McIntosh [mcint...@cs.queensu.ca] wrote: Hi Qt developers! My name is Shane. I’m a PhD student at Queen’s University in Canada. I’ve been working on an approach for detecting build hotspots, i.e., files that not only take a long time to rebuild, but also change often. We think that these files are ideal candidates for refactoring that could shave time off of incremental builds that are really impacting software teams. That sounds like a good idea in general. Looking at your list at http://sailhome.cs.queensu.ca/~shane/content/qt_hotspots.txt I wonder a bit how e.g. xmlpatterns can be considered a hotspot that according to your definition changes often. The actual code has not been changed much for a while except for occasional merges and the annual bumps in copyright headers. My gut feeling is that any refactoring there is not worthwhile. I’m happy to provide a more detailed Qt dataset when I return to my lab next week. It would be nice to see some reason (numbers) why files ended up on the list. Best regards, Andre' ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Interest] qmlx11 plugin
I already have 2 functions (which You can use from .qml as ListModel (modelData)) - one that does show all windows - X11support::windowListUnskipped and X11::windowList which checks if the window is _NET_CLIENT_SKIP_TASKBAR so I already do that. The only thing is I can't get the XEvents to work... 2014-02-05 Rutledge Shawn shawn.rutle...@digia.com: On 5 Feb 2014, at 11:16 AM, Damian Ivanov wrote: Hi, I made a c++ QML plugin for X11 functions like windowlist, active window, setting, getting icon of apps, names, id and setting netwm properties. Source code is here https://build.opensuse.org/package/show/home:damianator:qmlx11/qmlx11 Right now you can do all the stuff mentioned already, but the windowList and the window properties are not updated automatically via XEvent's instead hackishly I have a Timer reloading the active window and the windowList every few seconds. Could anyone interested assist me in properly receiving the XEvent's so the qmlx11 plugin properly emits signals according to the received XEvent's (actually that's not the problem, but I couldn't manage to receive the XEvents at all). Personally I wish we had some of that as QPA APIs (at least window list and window icons), but of course it assumes that we can do the same thing on the other platforms. In my experience, the window list is tricky stuff on X11 though, because there are so many windows you don't normally want to show in a task list. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Windows Online Installer problem(s)
Hash mismatch was because qt5.2.1 content was replicating to the mirrors at that time. Br, Jani -Original Message- From: Chris Gagneraud [mailto:chg...@googlemail.com] On Behalf Of Christian Gagneraud Sent: 6. helmikuuta 2014 22:30 To: Heikkinen Jani; development@qt-project.org Subject: Re: [Development] Windows Online Installer problem(s) On 05/02/14 20:12, Heikkinen Jani wrote: Hi all, When did you tried that online installation? I just checked the Windows computer and this was Qt 5.2.0, not 5.2.1. Chris Br, Jani -Original Message- From: development-bounces+jani.heikkinen=digia@qt-project.org [mailto:development-bounces+jani.heikkinen=digia@qt-project.org] On Behalf Of Christian Gagneraud Sent: 5. helmikuuta 2014 4:03 To: development@qt-project.org Subject: [Development] Windows Online Installer problem(s) Hi there, I tried to install Qt with the latest official online installer on a Windows computer [1], and I couldn't install it on the 'D' disk, because the 'C' disk didn't have enough space to store the downloaded data (I guess in the system temp dir, which is likely to be on c:) Another annoying (but non blocking) problem I had was a hash mismatch on one of the Android component, the work around in my case was simply to unselect the 2 android components via the settings dialogue. I tried to re-run the installer 3 times, and 3 times I had a hash mismatch, so the problem seems to be on the server side. I ended up installing Qt using the offline installer. Chris [1] http://download.qt- project.org/official_releases/online_installers/1.5/qt- windows-opensource-1.5.0-x86-online.exe ___ 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] [Interest] qmlx11 plugin
The eventFiler is already re-implemented as bool X11Support::xEventFilter(XEvent * event), the only problem is I want to start receiving the events, I guess it's one line of code that should look like m_instance-xEventFilter(event); where m_instance is an instance of the class. Trying to do so results in x11support.cpp:487: error: no matching function for call to 'X11Support::xEventFilter(unresolved overloaded function type)' m_instance-xEventFilter(event); What am I doing wrong? Help really appreciated. 2014-02-05 Thiago Macieira thiago.macie...@intel.com: Em qua 05 fev 2014, às 19:29:37, Damian Ivanov escreveu: Maybe not a feature for Qt directly, but it is a plug-in and what I want to do with the plugin is actually a task manager :) Sure, that is a welcome thing, thanks for making the effort. I was just reacting to making this part of QPA. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Interest mailing list inter...@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
