curtin-dev team mailing list archive
-
curtin-dev team
-
Mailing list archive
-
Message #01919
Re: [Merge] ~dbungert/curtin:udi-513 into curtin:master
I'm not here today but is there any scope for moving curtin to a model of
not relying on lsblk output? I.e. get the information it needs from sysfs
or udev or whatever more directly?
On Thu, 18 Nov 2021, 07:42 Server Team CI bot, <mp+412027@xxxxxxxxxxxxxxxxxx>
wrote:
> Review: Approve continuous-integration
>
> PASSED: Continuous integration,
> rev:37945f5ddee4f4ea8258e6a7f99d3c686fb4fbea
> https://jenkins.ubuntu.com/server/job/curtin-ci/200/
> Executed test runs:
> SUCCESS:
> https://jenkins.ubuntu.com/server/job/curtin-ci/nodes=metal-amd64/200/
> SUCCESS:
> https://jenkins.ubuntu.com/server/job/curtin-ci/nodes=metal-arm64/200/
> SUCCESS:
> https://jenkins.ubuntu.com/server/job/curtin-ci/nodes=metal-ppc64el/200/
> SUCCESS:
> https://jenkins.ubuntu.com/server/job/curtin-ci/nodes=metal-s390x/200/
>
>
> Click here to trigger a rebuild:
> https://jenkins.ubuntu.com/server/job/curtin-ci/200//rebuild
> --
> https://code.launchpad.net/~dbungert/curtin/+git/curtin/+merge/412027
> You are subscribed to branch curtin:master.
>
>
--
https://code.launchpad.net/~dbungert/curtin/+git/curtin/+merge/412027
Your team curtin developers is requested to review the proposed merge of ~dbungert/curtin:udi-513 into curtin:master.
References