Give warning if runpath disk space is close to full on ert startup

[larsevj]

Issue
Resolves #8921

The following is presented if disk is "close" to full:

• PR title captures the intent of the changes, and is fitting for release notes.
• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.
• Make sure unit tests pass locally after every commit (git rebase -i main --exec 'pytest tests/ert/unit_tests -n logical -m "not integration_test"')

When applicable

• When there are user facing changes: Updated documentation
• New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
• Large PR: Prepare changes in small commits for more convenient review
• Bug fix: Add regression test for the bug
• Bug fix: Create Backport PR to latest release

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 95.71429% with 3 lines in your changes missing coverage. Please review.

Project coverage is 91.76%. Comparing base (45a4b7c) to head (9add58e).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
src/ert/gui/simulation/view/disk_space_widget.py	94.44%	2 Missing ⚠️
src/ert/shared/status/utils.py	92.85%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9193      +/-   ##
==========================================
+ Coverage   91.72%   91.76%   +0.03%     
==========================================
  Files         430      431       +1     
  Lines       26639    26707      +68     
==========================================
+ Hits        24435    24508      +73     
+ Misses       2204     2199       -5     

Flag	Coverage Δ
cli-tests	39.43% <27.14%> (-0.04%)	⬇️
everest-models-test	34.20% <27.14%> (-0.01%)	⬇️
gui-tests	71.92% <92.85%> (+0.09%)	⬆️
integration-test	38.32% <27.14%> (+0.02%)	⬆️
performance-tests	51.74% <67.14%> (+0.05%)	⬆️
test	39.61% <27.14%> (+<0.01%)	⬆️
unit-tests	74.05% <95.71%> (+0.06%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[larsevj]

initial attempt. Very open for suggestions regarding the text.

[larsevj]

Second alternative:

[berland]

👍🏻

[eivindjahren]

Should this check be on startup or on experiment start?

[larsevj]

Should this check be on startup or on experiment start?

Might be better to be on experiment startup, seems like a lot of users ignore warnings on startup. Maybe we also should check space left on enspath?

[eivindjahren]

Should this check be on startup or on experiment start?

Might be better to be on experiment startup, seems like a lot of users ignore warnings on startup. Maybe we also should check space left on enspath?

Yes, we should check there also, we have seen a lot of errors from missing capacity in enspath. Also, for enspath we could estimate how much space is necessary, but I suggest we keep that for another PR.

[eivindjahren]

I updated the description of the issue with a new approach to doing this.

[codspeed-hq]

CodSpeed Performance Report

Merging #9193 will not alter performance

_{Comparing larsevj:warn_on_full_disk (9add58e) with main (9e2e32f)}

Summary

✅ 24 untouched benchmarks

[larsevj]

Currently:

[eivindjahren]

This seems ready to squash and merge now?