I just checked that I can reproduce that in the test suite, which uses a clean and zeroed-out device, so it's not the usual "gets confused about two different signatures on the device".
$ sudo tests/run FS.test_vfat
Testing binaries from local build tree
daemon path: src/udisks-daemon
mdadm: array /dev/md125 started.
fs: FAT ... [cli]FAIL
======================================================================
FAIL: fs: FAT
----------------------------------------------------------------------
Traceback (most recent call last):
File "tests/run", line 412, in test_vfat
self._do_fs_check('vfat')
File "tests/run", line 443, in _do_fs_check
self._do_mkfs_check(type)
File "tests/run", line 473, in _do_mkfs_check
self.failIf ('partition_scheme' in i)
AssertionError
I just checked that I can reproduce that in the test suite, which uses a clean and zeroed-out device, so it's not the usual "gets confused about two different signatures on the device".
http:// cgit.freedeskto p.org/udisks/ commit/ ?id=47ac2676ca6 d209705f9f814cd ed2daf19f24e76
Now the test suite properly fails:
$ sudo tests/run FS.test_vfat
Testing binaries from local build tree
daemon path: src/udisks-daemon
mdadm: array /dev/md125 started.
fs: FAT ... [cli]FAIL
======= ======= ======= ======= ======= ======= ======= ======= ======= ======= ------- ------- ------- ------- ------- ------- ------- ------- ------- _do_fs_ check(' vfat') _do_mkfs_ check(type)
FAIL: fs: FAT
-------
Traceback (most recent call last):
File "tests/run", line 412, in test_vfat
self.
File "tests/run", line 443, in _do_fs_check
self.
File "tests/run", line 473, in _do_mkfs_check
self.failIf ('partition_scheme' in i)
AssertionError