Hi, Tony,
Could you let us know when this issue will be fixed? At least the CI hasn't
work well since 5pm yesterday.
http://lists.qt-project.org/pipermail/ci-reports/2013-May/
Regards,
Liang
From: Sarajärvi Tony
Sent: Tuesday, May 21, 2013 12:06 PM
To:
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
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
On Tuesday, May 21, 2013 11:38:41 Thiago Macieira wrote:
On terça-feira, 21 de maio de 2013 20.27.41, Stephen Kelly wrote:
For a Qt patch, I need to know at compile-time whether std::find can be
used with it, ie, whether the value_type of the container can be
equality-compared.
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
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:
just in case you wonder where the stage button has gone ...
due to several circumstances coming together, all integrations to
qtbase/dev will currently fail. therefore, staging has been temporarily
disabled.
fix should arrive within one day, barring ongoing CI trouble.
On Tuesday, May 21, 2013 08:53:35 Sarajärvi Tony wrote:
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.
I'd suggest not changing the meaning of 'building'. If you mean
I grant you that we are always releasing something, but in this instance I was
referring to the fact that 5.1 beta is already out, with the final due in just
a few weeks and time is running short because of the timing of that then it
might be best to hold off on doing some upgrades until a
On Tuesday, May 21, 2013 07:19:40 you wrote:
Hi
I finally have some time to give you a proper answer :)
Thanks for all your responses!
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
Hi,
We are working on a very strange issues occurring in the QThreadPool and
suspect the below is related:
https://bugreports.qt-project.org/browse/QTBUG-3786
Just recently there was a comment that this bug still occurs in 4.8.4.
It would be more than very helpful if somebody will review the
On quarta-feira, 22 de maio de 2013 11.07.44, Stephen Kelly wrote:
QSpiRelationArray::value_type is QSpiRelationArrayEntry which, being a
QPair, does have a operator==(), so the decltype gives the result that the
std::find should work.
In other words, QPair has an operator==, but it can't be
On quarta-feira, 22 de maio de 2013 12.56.53, Vladimir Minenko wrote:
Hi,
We are working on a very strange issues occurring in the QThreadPool and
suspect the below is related:
https://bugreports.qt-project.org/browse/QTBUG-3786
Just recently there was a comment that this bug still
On Wednesday, May 22, 2013 07:41:12 Thiago Macieira wrote:
On quarta-feira, 22 de maio de 2013 11.07.44, Stephen Kelly wrote:
QSpiRelationArray::value_type is QSpiRelationArrayEntry which, being a
QPair, does have a operator==(), so the decltype gives the result that
the
std::find should
On quarta-feira, 22 de maio de 2013 17.04.21, Stephen Kelly wrote:
In other words, QPair has an operator==, but it can't be used because it
won't compile. Your code detects that it exists, but can't be sure that it
works?
Correct. The compiler sees that operator==() exists, but it doesn't
Hi,
4) Windows 8’s cmd.exe problem – NOT FIXED
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.
Just thinking aloud, sharing what I found when I also ran into this
problem when toying with
On Wednesday, May 22, 2013 08:15:59 Thiago Macieira wrote:
On quarta-feira, 22 de maio de 2013 17.04.21, Stephen Kelly wrote:
In other words, QPair has an operator==, but it can't be used because it
won't compile. Your code detects that it exists, but can't be sure that
it
works?
On quarta-feira, 22 de maio de 2013 19.34.49, Stephen Kelly wrote:
The operator exists and there's nothing preventing it from existing. The
problem is that the operator exists but can't be used.
Yes.
It does. You need to make sure that there's an enable_if in the function
you're
Hi,
I have added a moment. It is happening again...
I'm trying to compile 64 bit ,windows 7 , vs 2012 update 2.
https://bugreports.qt-project.org/browse/QTBUG-31004#comment-203448
Thanks,
Francisco R. Ortega
Ph.D. Candidate in Computer Science
Florida International University
19 matches
Mail list logo
