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

Run everest tests before publishing to pypi #8756

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

frode-aarstad
Copy link
Contributor

Issue
Resolves #8744

Approach
Short description of the approach

(Screenshot of new behavior in GUI if applicable)

  • 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/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

@frode-aarstad frode-aarstad self-assigned this Sep 20, 2024
@frode-aarstad frode-aarstad added the release-notes:skip If there should be no mention of this in release notes label Sep 20, 2024
@frode-aarstad frode-aarstad force-pushed the everest-pypi branch 3 times, most recently from dc48e49 to 5249c3f Compare September 23, 2024 08:05
python-version:
type: string
test-type:
type: string

concurrency:
Copy link
Contributor

Choose a reason for hiding this comment

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

I believe this must be removed. The concurrency inherits from build_and_test.yml from now on.

@@ -141,7 +155,7 @@ jobs:
publish:
name: Publish to PyPI
runs-on: ubuntu-latest
needs: [build-wheels, test-linux, test-mac-for-tags, docs-ert]
needs: [build-wheels, test-linux-ert, test-linux-everest, test-mac-for-tags-ert, docs-ert]
Copy link
Contributor

Choose a reason for hiding this comment

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

Should probably also have test-mac-for-tags-everest ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agree. Will create that aswell

@codecov-commenter
Copy link

codecov-commenter commented Sep 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.39%. Comparing base (f7cadbb) to head (0d3c33d).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8756      +/-   ##
==========================================
- Coverage   91.40%   91.39%   -0.01%     
==========================================
  Files         343      343              
  Lines       21087    21087              
==========================================
- Hits        19274    19273       -1     
- Misses       1813     1814       +1     
Flag Coverage Δ
cli-tests 39.62% <ø> (+<0.01%) ⬆️
gui-tests 73.48% <ø> (ø)
performance-tests 50.17% <ø> (ø)
unit-tests 79.88% <ø> (-0.01%) ⬇️

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.

@frode-aarstad frode-aarstad force-pushed the everest-pypi branch 4 times, most recently from bcf111a to c6388e9 Compare September 25, 2024 13:41
env:
QT_QPA_PLATFORM: 'minimal'
run: |
python -m pytest tests/everest -m "ui_test"

- name: Build Documentation
if: matrix.test_type == 'doc'
if: inputs.test-type == 'doc'
Copy link
Contributor

@larsevj larsevj Sep 27, 2024

Choose a reason for hiding this comment

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

I would suggest maybe combining this and the test doc entry points, and making it a separate step in the build and test workflow, so that it can be run only once for one python version to reduce the number of total workflows run? Similar to how we test the building of the ert docs.
But this can probably be done later in another pr.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added so docs are only build for py312

Copy link
Contributor

@larsevj larsevj left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@frode-aarstad frode-aarstad force-pushed the everest-pypi branch 10 times, most recently from 567cb20 to 8c72c36 Compare October 3, 2024 06:01
@frode-aarstad frode-aarstad merged commit 4bba695 into equinor:main Oct 3, 2024
56 checks passed
@frode-aarstad frode-aarstad deleted the everest-pypi branch October 3, 2024 06:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes:skip If there should be no mention of this in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Require everest tests to pass before being able to publish to pypi
3 participants