[PATCH 0/1] [autotest] sfdisk: do not hardcode starting sector

[Po-Hsu Lin]

Hi Paolo,
the buglink here seems irrelevant, do you have the correct bug report for this?
Thanks
Sam

On Mon, Apr 6, 2020 at 6:22 PM Paolo Pisati <paolo.pisati at canonical.com> wrote:
>
> BugLink: https://bugs.launchpad.net/bugs/1864642
>
> Every selftest unit test instantiating a virtual_partition class:
>
> $ git grep virtual_partition
> ubuntu_xfstests_btrfs/control:vp = partition.virtual_partition(file_img=file_img, file_size=1024*1024)
> ubuntu_xfstests_ext4/control:vp = partition.virtual_partition(file_img=file_img, file_size=1024*1024)
> ubuntu_xfstests_xfs/control:vp = partition.virtual_partition(file_img=file_img, file_size=1024*1024)
> xfstests/control:vp = partition.virtual_partition(file_img=file_img, file_size=1024*1024)
>
> will fail during _init_ with:
>
> >>> Created a new DOS disklabel with disk identifier 0x9b4a9cf7.
> /dev/loop1p1: Start sector 0 out of range.
> Failed to add #1 partition: Numerical result out of range
> Leaving.
>
> because we hardcoded 0 as the starting sector: fix it by letting sfdisk pick
> the first available sector.
>
> Paolo Pisati (1):
>   UBUNTU: SAUCE: sfdisk: let sfdisk decide the first available
>     sector
>
>  client/partition.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> --
> 2.25.1
>
>
> --
> kernel-team mailing list
> kernel-team at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kernel-team