• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

agama-project / agama / 26586921140
81%

Build:
DEFAULT BRANCH: master
Ran 28 May 2026 04:15PM UTC
Jobs 3
Files 930
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

28 May 2026 04:12PM UTC coverage: 81.411% (+0.007%) from 81.404%
26586921140

push

github

web-flow
Try boot partitions with desired and min sizes (#3559)

## Problem

The logic to calculate boot-related partitions in yast2-storage-ng
defines three sizes for each partition: min, desired and max.

When using that in Agama, desired is ignored and only min and max are
taken into account. That's something we always wanted to re-evaluate
(together with several other aspects related to proposing boot
partitions).

When installing with enough available space (let's say in an empty disk
or allowing the installer to delete partitions) then there is often no
practical difference. The distance between min, desired and max is so
small in comparison with the rest of partitions to create that any
attempt (starting with either min or desired) always produces the same
result. See #3394 for the whole rationale.

But the result is non-optimal when resizing existing partitions just as
much as needed to make space for the new installation. In those case
Agama is creating partitions with min sizes that where intended for
extreme cases, not really as the best practice.

## Solution

This introduces a new approach in which several different sets of
boot-related partitions are calculated and tried. In this case, it makes
a first attempt using the desired sizes as starting point and, if that
fails, a second attempt using the min size as starting point.

This results in more reasonable proposal in most cases, without
introducing the risk of failing in edge cases that used to work when
using the min sizes.

## Testing

- Added a new unit tests

## Note

This is a "resurrection" of #3394, which was archived for the wrong
reasons.

4360 of 6388 branches covered (68.25%)

Branch coverage included in aggregate %.

26 of 26 new or added lines in 2 files covered. (100.0%)

23744 of 28133 relevant lines covered (84.4%)

95.29 hits per line

Subprojects
ID Flag name Job ID Ran Files Coverage
3 service 26586921140.3 28 May 2026 04:15PM UTC 317
92.47
GitHub Action Run
3 web 26572618587.3 28 May 2026 11:47AM UTC 613
77.42
GitHub Action Run
1 rust 19474749743.1 18 Nov 2025 05:18PM UTC 185
22.45
GitHub Action Run
Source Files on build 26586921140
  • Tree
  • List 930
  • Changed 4
  • Source Changed 3
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #26586921140
  • a485ac77 on github
  • Prev Build on master (#26572618587)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc