irtualized vmxnet3 driver that
> we've been using before.
>
>
>
> Simon
>
>
> From: Development
> on behalf of Sean Harmer Sent: Monday, August 21,
> 2017 11:12:15 AM
> To: development@qt-project.org
> Subject: Re: [Development] Random CI Fail
x27;re using an emulated e1000, but I'm trying to switch over
the "other" paravirtualized vmxnet3 driver that we've been using before.
Simon
From: Development on
behalf of Sean Harmer
Sent: Monday, August 21, 2017 11:12:15 AM
To: developm
And again today on:
https://codereview.qt-project.org/#/c/194936/
Same configuration type, win8-mingw. Can we remove this from the active set of
configurations for qt3d until this is resolved please?
Thanks,
Sean
On Saturday, 19 August 2017 19:56:57 BST Sean Harmer wrote:
> On Saturday, 19 Au
On Saturday, 19 August 2017 12:57:18 BST Sean Harmer wrote:
> Hi Simon,
>
> On 19/08/2017 11:59, Simon Hausmann wrote:
> > Hi,
> >
> > We've had file system corruption in our base Windows images for the past
> > weeks. Yesterday late afternoon I finally managed to get hold of it and
> > fix it. T
Hi Simon,
On 19/08/2017 11:59, Simon Hausmann wrote:
Hi,
We've had file system corruption in our base Windows images for the past weeks.
Yesterday late afternoon I finally managed to get hold of it and fix it. This
may have been the cause of your trouble. Did you still see failures yesterday
Hi,
We've had file system corruption in our base Windows images for the past weeks.
Yesterday late afternoon I finally managed to get hold of it and fix it. This
may have been the cause of your trouble. Did you still see failures yesterday
evening and today?
Simon
> On 19. Aug 2017, at 11:19,
Hi,
we seem to be getting a large number of random CI failures when trying
to integrate Qt 3D changes for the last week or so. It manifests itelf
as the win8-mingw node failing but no log file is recorded. On the odd
occasion we get a log file it's like the node just stopped, there's no
erro
