[Xen-changelog] As hotplug events are asynchronous by its nature, the remove event seems

[Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User root@kct
# Node ID 970cf1fff5f2b55f4f646950f5c7a747a6db92f9
# Parent  8af1199488d3636135f3adf3f7302d4a04e9004e
As hotplug events are asynchronous by its nature, the remove event seems
to be missed in some environments. This patch adds a sleep (with the same
amount of time of the one after xm block-detach) between attach and
detach operations, giving attach enough time to complete, making test 06
suceed.

Signed-off-by: Glauber de Oliveira Costa <glommer@xxxxxxxxxx>

diff -r 8af1199488d3 -r 970cf1fff5f2 
tools/xm-test/tests/block-destroy/06_block-destroy_check_list_pos.py
--- a/tools/xm-test/tests/block-destroy/06_block-destroy_check_list_pos.py      
Mon Jan  9 11:22:17 2006
+++ b/tools/xm-test/tests/block-destroy/06_block-destroy_check_list_pos.py      
Mon Jan  9 11:24:02 2006
@@ -46,6 +46,8 @@
 if not checkXmLongList(domain):
     FAIL("xm long list does not show that hda1 was attached")
 
+time.sleep(2)
+
 s, o = traceCommand("xm block-detach %s hda1" % domain.getName())
 if s != 0:
     FAIL("block-detach failed")

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog