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

Fixed failing test_save in master #756

Merged
merged 4 commits into from
May 14, 2024
Merged

Conversation

jesper-friis
Copy link
Collaborator

@jesper-friis jesper-friis commented May 1, 2024

Description

Simplifying paths in test_save_emmo_domain_ontology() in test_save.py to make it much easier to debug.

After simplifying paths in test_save_emmo_domain_ontology() in
test_save.py to make it possible to debug, the test works again :-)
Copy link

codecov bot commented May 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.11%. Comparing base (a09e0ed) to head (d15187a).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #756      +/-   ##
==========================================
- Coverage   72.14%   72.11%   -0.03%     
==========================================
  Files          17       17              
  Lines        3486     3486              
==========================================
- Hits         2515     2514       -1     
- Misses        971      972       +1     

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

francescalb added a commit that referenced this pull request May 2, 2024
# Description
Minor fixes for ontoconvert option help. 

Also included `emmo:comment` to the set of annotations included in the
`--copy-emmo-annotations` option.

**Note**: Builds on top of PR
#756. Merge that PR first!

## Type of change
- [x] Bug fix.
- [ ] New feature.
- [ ] Documentation update.
- [ ] Test update.

## Checklist
<!-- Put an `x` in the boxes that apply. You can also fill these out
after creating the PR. -->

This checklist can be used as a help for the reviewer.

- [ ] Is the code easy to read and understand?
- [ ] Are comments for humans to read, not computers to disregard?
- [ ] Does a new feature has an accompanying new test (in the CI or unit
testing schemes)?
- [ ] Has the documentation been updated as necessary?
- [ ] Does this close the issue?
- [ ] Is the change limited to the issue?
- [ ] Are errors handled for all outcomes?
- [ ] Does the new feature provide new restrictions on dependencies, and
if so is this documented?

## Comments
<!-- Additional comments here, including clarifications on checklist if
applicable. -->

---------

Co-authored-by: Francesca L. Bleken <48128015+francescalb@users.noreply.github.com>
Copy link
Collaborator

@francescalb francescalb left a comment

Choose a reason for hiding this comment

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

There is no bug in the current master. I passes without problem.

@jesper-friis
Copy link
Collaborator Author

There is no bug in the current master. I passes without problem.

This PR is just a simplification without any behavioral changes, so it shouldn't change whether the tests fails or not. Still it made test_save.py succeed locally for me. Merging it into PR #742, also helped that PR succeeding on github.

Copy link
Collaborator

@francescalb francescalb left a comment

Choose a reason for hiding this comment

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

OK, since you insist. But please rewrite this to a change because of your preference as there is no bug here.

francescalb added a commit that referenced this pull request May 8, 2024
# Description
Minor fixes for ontoconvert option help. 

Also included `emmo:comment` to the set of annotations included in the
`--copy-emmo-annotations` option.

**Note**: Builds on top of PR
#756. Merge that PR first!

## Type of change
- [x] Bug fix.
- [ ] New feature.
- [ ] Documentation update.
- [ ] Test update.

## Checklist
<!-- Put an `x` in the boxes that apply. You can also fill these out
after creating the PR. -->

This checklist can be used as a help for the reviewer.

- [ ] Is the code easy to read and understand?
- [ ] Are comments for humans to read, not computers to disregard?
- [ ] Does a new feature has an accompanying new test (in the CI or unit
testing schemes)?
- [ ] Has the documentation been updated as necessary?
- [ ] Does this close the issue?
- [ ] Is the change limited to the issue?
- [ ] Are errors handled for all outcomes?
- [ ] Does the new feature provide new restrictions on dependencies, and
if so is this documented?

## Comments
<!-- Additional comments here, including clarifications on checklist if
applicable. -->

---------

Co-authored-by: Francesca L. Bleken <48128015+francescalb@users.noreply.github.com>
@jesper-friis jesper-friis merged commit 60dda59 into master May 14, 2024
11 of 12 checks passed
@jesper-friis jesper-friis deleted the fix-test-save-in-master branch May 14, 2024 14:30
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.

2 participants