On Wed, 7 Jun 2023 at 10:39, Vladimir Sementsov-Ogievskiy
wrote:
>
> On 06.06.23 19:25, Richard Henderson wrote:
> > This test consistently fails on Azure cloud build hosts in
> > a way that suggests a timing problem in the test itself:
> >
> > --- .../194.out
> > +++ .../194.out.bad
> > @@ -14,7
On 06.06.23 19:25, Richard Henderson wrote:
This test consistently fails on Azure cloud build hosts in
a way that suggests a timing problem in the test itself:
--- .../194.out
+++ .../194.out.bad
@@ -14,7 +14,6 @@
{"return": {}}
{"data": {"status": "setup"}, "event": "MIGRATION", "timestamp"
On 07.06.23 15:44, Stefan Hajnoczi wrote:
The line of output that has changed was originally added by the
following commit:
commit ae00aa2398476824f0eca80461da215e7cdc1c3b
Author: Vladimir Sementsov-Ogievskiy
Date: Fri May 22 01:06:46 2020 +0300
iotests: 194: test also migration of dirt
The line of output that has changed was originally added by the
following commit:
commit ae00aa2398476824f0eca80461da215e7cdc1c3b
Author: Vladimir Sementsov-Ogievskiy
Date: Fri May 22 01:06:46 2020 +0300
iotests: 194: test also migration of dirty bitmap
Vladimir: Any idea why the postcopy
On 6/6/23 12:24, Philippe Mathieu-Daudé wrote:
On 6/6/23 18:25, Richard Henderson wrote:
This test consistently fails on Azure cloud build hosts in
a way that suggests a timing problem in the test itself:
--- .../194.out
+++ .../194.out.bad
@@ -14,7 +14,6 @@
{"return": {}}
{"data": {"status
On 6/6/23 18:25, Richard Henderson wrote:
This test consistently fails on Azure cloud build hosts in
a way that suggests a timing problem in the test itself:
--- .../194.out
+++ .../194.out.bad
@@ -14,7 +14,6 @@
{"return": {}}
{"data": {"status": "setup"}, "event": "MIGRATION", "timestamp":
On 06/06/2023 18.25, Richard Henderson wrote:
This test consistently fails on Azure cloud build hosts in
a way that suggests a timing problem in the test itself:
--- .../194.out
+++ .../194.out.bad
@@ -14,7 +14,6 @@
{"return": {}}
{"data": {"status": "setup"}, "event": "MIGRATION", "timestam
This test consistently fails on Azure cloud build hosts in
a way that suggests a timing problem in the test itself:
--- .../194.out
+++ .../194.out.bad
@@ -14,7 +14,6 @@
{"return": {}}
{"data": {"status": "setup"}, "event": "MIGRATION", "timestamp":
{"microseconds": "USECS", "seconds": "SECS"}}
