Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor usage of EverestConfig in everest server functionality #9181

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

DanSava
Copy link
Contributor

@DanSava DanSava commented Nov 12, 2024

Issue
Resolves #9182

  • 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

@DanSava DanSava self-assigned this Nov 12, 2024
@codecov-commenter
Copy link

codecov-commenter commented Nov 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.75%. Comparing base (5b96e8a) to head (c0cfb68).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #9181      +/-   ##
==========================================
- Coverage   90.78%   90.75%   -0.03%     
==========================================
  Files         352      352              
  Lines       21935    21935              
==========================================
- Hits        19913    19908       -5     
- Misses       2022     2027       +5     
Flag Coverage Δ
cli-tests 39.24% <ø> (-0.01%) ⬇️
gui-tests 71.75% <ø> (-0.03%) ⬇️
performance-tests 49.36% <ø> (-0.03%) ⬇️
unit-tests 79.66% <ø> (-0.02%) ⬇️

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.

@DanSava DanSava force-pushed the everest-server-refactor-usafe-of-everest-config branch 8 times, most recently from 24340b4 to 09c0e89 Compare November 14, 2024 10:50
@DanSava DanSava force-pushed the everest-server-refactor-usafe-of-everest-config branch from 09c0e89 to ab2c26b Compare November 15, 2024 08:32
file_path=os.path.join(log_dir, "simulations.log"),
log_level=logging.INFO,
)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these logs now in everserver? or is everest_server.log removed

@@ -225,24 +193,16 @@ def server_is_running(url: str, cert: bool, auth: Tuple[str, str]):
return True


def get_optimization_status(config: EverestConfig):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this function not used?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Limit the use of EverestConfig in the Server related function signatures
3 participants