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

openSUSE / agama / 8230343178
72%

Build:
DEFAULT BRANCH: master
Ran 11 Mar 2024 09:19AM UTC
Jobs 3
Files 697
Run time 1min
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

11 Mar 2024 09:16AM UTC coverage: 74.145% (-0.02%) from 74.167%
8230343178

push

github

web-flow
Description for adjust_by_ram (#1081)

## Problem

In Agama a volume can have automatic sizes based on one or several of
the following reasons:

- Snapshots
- Fallbacks from other volumes (eg. "/" max size can exist or not based
on the existence of "/home")
- Size of the RAM

The three are already implemented and working. But the third one lacks
the corresponding explanations.

| No information icon in the "auto" label | Incomplete sentence in the
form |
|-|-|
|
![by_ram](https://github.com/openSUSE/agama/assets/3638289/a6a2aedd-b630-4346-8d16-6c2cc2fa6d85)
|
![enlarge](https://github.com/openSUSE/agama/assets/3638289/2f0443ae-a732-40af-a858-f8314d48ad19)
|

## Solution

This pull request introduces the missing messages, so now the proper
information is displayed both in the table of volumes and in the form.

| The "auto" label | The form |
|-|-|
|
![ram-table](https://github.com/openSUSE/agama/assets/3638289/ec742117-6859-462c-8a9c-460c1509bf43)
|
![ram-form](https://github.com/openSUSE/agama/assets/3638289/3fd74029-196c-4b4f-9da5-74e5efbe52e0)
|

The message is "as good as it gets" for the time being. The plan is to
add the size of the RAM to it, but for that we need to improve the Agama
API as reflected at

https://trello.com/c/suiA6MzZ/354-agama-api-for-system-information-like-ram-size

Additionally, this pull request enables `adjust_by_ram` for swap at the
Tumbleweed product, to raise awareness and get feedback.

### About the approach

We can already foresee people asking "where is my 'Enlarge to RAM Size
for Suspend' checkbox"? So let's explain how the approach has changed.
That approach, not only for swap but for so-called volumes in general,
is explained in the section "[Automatic Size
Limits](https://github.com/openSUSE/agama/blob/master/doc/storage_ui.md#automatic-size-limits)"
of the document describing the storage UI.

In the traditional YaST storage proposal users has no direct way to... (continued)

1496 of 2279 branches covered (65.64%)

Branch coverage included in aggregate %.

2 of 4 new or added lines in 2 files covered. (50.0%)

50 existing lines in 3 files now uncovered.

16932 of 22575 relevant lines covered (75.0%)

22.89 hits per line

New Missed Lines in Diff

Lines Coverage ∆ File
2
82.44
-1.64% web/src/components/storage/VolumeForm.jsx

Uncovered Existing Lines

Lines Coverage ∆ File
6
92.31
0.0% web/web/src/components/storage/ProposalVolumes.jsx
9
86.08
-1.67% web/web/src/components/storage/VolumeForm.jsx
35
87.46
0.0% web/web/src/client/storage.js
Subprojects
ID Flag name Job ID Ran Files Coverage
1 web 8230343178.1 11 Mar 2024 09:19AM UTC 301
73.65
GitHub Action Run
1 rust 8187148015.1 07 Mar 2024 11:16AM UTC 80
42.49
GitHub Action Run
1 service 7975321865.1 20 Feb 2024 02:48PM UTC 316
85.22
GitHub Action Run
Source Files on build 8230343178
  • Tree
  • List 697
  • Changed 25
  • Source Changed 4
  • Coverage Changed 7
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #8230343178
  • 704b693c on github
  • Prev Build on master (#8203901726)
  • Next Build on master (#8293548031)
  • 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