Em quinta-feira, 16 de março de 2017, às 16:26:20 PDT, André Pönitz escreveu:
> On Thu, Mar 16, 2017 at 01:23:55PM -0400, Matthew Woehlke wrote:
> > On 2017-03-14 13:33, André Pönitz wrote:
> > > In general, I am not overly sold on ABI compatibility promises. I
> > > personally could live without a
On Thu, Mar 16, 2017 at 01:23:55PM -0400, Matthew Woehlke wrote:
> On 2017-03-14 13:33, André Pönitz wrote:
> > In general, I am not overly sold on ABI compatibility promises. I personally
> > could live without and find SC of more practical value. The most important
> > "feature" of ABI compatibil
On 2017-03-14 13:33, André Pönitz wrote:
> In general, I am not overly sold on ABI compatibility promises. I personally
> could live without and find SC of more practical value. The most important
> "feature" of ABI compatibility guarantee for me is that it limits people from
> doing overly excessi
Hi
1. We don't know to be frank. The VMs aren't live migrated, the SAN hasn't been
proved to be down or even the bottleneck, at least for standard hardware. Apple
hardware is another issue, and here SAN seems to either slow down or possibly
even break up sometimes. Some Macs slow down to the po
On Thursday 16 March 2017 10:00:55 Marc Mutz wrote:
> Latest example:
> http://testresults.qt.io/coin/integration/qt/qtbase/tasks/1489618366
Since this new seems to fail consistently across all branches, and didn't
before, I suspect something went wrong with some new OS image?
--
Marc Mutz |
Em quinta-feira, 16 de março de 2017, às 02:00:55 PDT, Marc Mutz escreveu:
> 2. What should we choose as timeouts? I understand that tests which are
> stuck are killed after some time (how long?). Maybe timeouts should be set
> to the same value?
Just wondering here: is there any way to run the ma
Hi,
(1) We don't know where the slowdowns come from. There is no VM migration
involved in the CI (the license does not include this feature). There is a SAN
under every single virtual machine disk (something we are getting rid of in the
not-for-qt-5.8.1 time).
(2) I don't know what the corre
On Donnerstag, 16. März 2017 10:00:55 CET Marc Mutz wrote:
> Hi,
>
> We repeatedly have the problem that timeouts that developers think are ample
> (because they exceed typical runtime by, say, two orders of magnitude) are
> found to be insufficient on the CI.
>
> Latest example:
> http://testres
Hi,
We repeatedly have the problem that timeouts that developers think are ample
(because they exceed typical runtime by, say, two orders of magnitude) are
found to be insufficient on the CI.
Latest example:
http://testresults.qt.io/coin/integration/qt/qtbase/tasks/1489618366
The timeout to r
