Thanks Ravi, I think the warning is a red herring though, it just
happens to print stdout/stderr only on failure. Those warnings are also
here on success run
Doing some local testing in an autopkgtest and printing the output "out
= self.get_monitor_output()" in test_media_player(()
in a success
Drive connected: 'Linux scsi_debug'
Drive(0): Linux scsi_debug
Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
ids:
unix-device: '/dev/sda'
themed icons: [drive-harddisk-solidstate] [drive-harddisk] [drive]
[drive-harddisk-solidstate-symbolic] [drive-harddisk-symbolic]
[drive-symbolic]
symbolic themed icons: [drive-harddisk-solidstate-symbolic]
[drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-solidstate]
[drive-harddisk] [drive]
is_removable=0
is_media_removable=0
has_media=1
is_media_check_automatic=1
can_poll_for_media=0
can_eject=0
can_start=0
can_stop=0
start_stop_type=shutdown
sort_key=01hotplug/1759397355041609
Volume(0): bogus-cd
Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
ids:
class: 'device'
unix-device: '/dev/sda'
uuid: '2013-01-10-07-29-25-00'
label: 'bogus-cd'
uuid=2013-01-10-07-29-25-00
themed icons: [drive-harddisk-solidstate] [drive-harddisk] [drive]
[drive-harddisk-solidstate-symbolic] [drive-harddisk-symbolic]
[drive-symbolic]
symbolic themed icons: [drive-harddisk-solidstate-symbolic]
[drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-solidstate]
[drive-harddisk] [drive]
can_mount=1
can_eject=0
should_automount=0
sort_key=gvfs.time_detected_usec.1759397355112198
Volume added: 'bogus-cd'
Volume(0): bogus-cd
Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
ids:
class: 'device'
unix-device: '/dev/sda'
uuid: '2013-01-10-07-29-25-00'
label: 'bogus-cd'
uuid=2013-01-10-07-29-25-00
themed icons: [drive-harddisk-solidstate] [drive-harddisk] [drive]
[drive-harddisk-solidstate-symbolic] [drive-harddisk-symbolic]
[drive-symbolic]
symbolic themed icons: [drive-harddisk-solidstate-symbolic]
[drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-solidstate]
[drive-harddisk] [drive]
can_mount=1
can_eject=0
should_automount=0
sort_key=gvfs.time_detected_usec.1759397355112198
but when failing
drive mount: media player ... --------------------------------------------------
Volume changed: 'bogus-cd'
Volume(0): bogus-cd
Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
ids:
class: 'device'
unix-device: '/dev/sda'
uuid: '2013-01-10-07-29-25-00'
label: 'bogus-cd'
uuid=2013-01-10-07-29-25-00
themed icons: [drive-harddisk-solidstate] [drive-harddisk] [drive]
[drive-harddisk-solidstate-symbolic] [drive-harddisk-symbolic]
[drive-symbolic]
symbolic themed icons: [drive-harddisk-solidstate-symbolic]
[drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-solidstate]
[drive-harddisk] [drive]
can_mount=1
can_eject=0
should_automount=0
sort_key=gvfs.time_detected_usec.1759397388885963
Drive disconnected: 'Linux scsi_debug'
Drive(0): Linux scsi_debug
Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
ids:
unix-device: '/dev/sda'
themed icons: [drive-harddisk-solidstate] [drive-harddisk] [drive]
[drive-harddisk-solidstate-symbolic] [drive-harddisk-symbolic]
[drive-symbolic]
symbolic themed icons: [drive-harddisk-solidstate-symbolic]
[drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-solidstate]
[drive-harddisk] [drive]
is_removable=0
is_media_removable=0
has_media=1
is_media_check_automatic=1
can_poll_for_media=0
can_eject=0
can_start=0
can_stop=0
start_stop_type=shutdown
sort_key=01hotplug/1759397388678091
Volume(0): bogus-cd
Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
ids:
class: 'device'
unix-device: '/dev/sda'
uuid: '2013-01-10-07-29-25-00'
label: 'bogus-cd'
uuid=2013-01-10-07-29-25-00
themed icons: [drive-harddisk-solidstate] [drive-harddisk] [drive]
[drive-harddisk-solidstate-symbolic] [drive-harddisk-symbolic]
[drive-symbolic]
symbolic themed icons: [drive-harddisk-solidstate-symbolic]
[drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-solidstate]
[drive-harddisk] [drive]
can_mount=1
can_eject=0
should_automount=0
sort_key=gvfs.time_detected_usec.1759397388885963
the same device is first set up in test_cdrom_api() so it looks like
sometime the volume is removed between the previous test and this one
and sometime not, which then leads to a "changed" event rather than an
"added" one.
A real fix would be to ensure that volume is removed/unsure why it is
sometime and sometime not. Adding a sleep() before "dev =
self.create_host(PTYPE_DISK)" doesn't workaround it.
A potential workaround could be to use a different device name/image for
the cdrom and media cases avoiding relying on the volume to go away in
between tests?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2126596
Title:
gvfs 1.57.2-2ubuntu5 autopkgtests failing with SyntaxWarning
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2126596/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
