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

Debug intermittent testing failures #26

Merged
merged 30 commits into from
May 16, 2024
Merged

Debug intermittent testing failures #26

merged 30 commits into from
May 16, 2024

Conversation

nfahlgren
Copy link
Member

Describe your changes
Changes aimed at debugging the cause of intermittent test failures where pytest exits with null code.

Type of update
Is this a: Work in progress

For the reviewer
See this page for instructions on how to review the pull request.

  • PR functionality reviewed in a Jupyter Notebook
  • All tests pass
  • Test coverage remains 100%
  • Documentation tested
  • New documentation pages added to plantcv/mkdocs.yml
  • Changes to function input/output signatures added to updating.md
  • Code reviewed
  • PR approved

@nfahlgren nfahlgren added the work in progress Mark work in progress label May 8, 2024
Copy link

deepsource-io bot commented May 8, 2024

Here's the code health analysis summary for commits 142bf93..19129c4. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource Python LogoPython✅ SuccessView Check ↗
DeepSource Test coverage LogoTest coverage✅ SuccessView Check ↗

Code Coverage Report

MetricAggregatePython
Branch Coverage100%100%
Composite Coverage100%100%
Line Coverage100%100%
New Branch Coverage100%100%
New Composite Coverage100%100%
New Line Coverage100%100%

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

nfahlgren and others added 26 commits May 10, 2024 11:20
saw something about specifically using python 3.10.12
seeing if the problem is consistently with 3.10
3.10 isn't the problem. getting same error on 3.11.
omg I broke github actions....
testing to see if there is a specific test breaking github actions.
testing viewer close on napari classes
add viewer.close() to napari.open
added napari join labels tests with viewer close
@maliagehan maliagehan removed the work in progress Mark work in progress label May 15, 2024
@maliagehan maliagehan added the ready to review Ready for code review label May 15, 2024
@maliagehan
Copy link
Member

maliagehan commented May 15, 2024

added tests back one by one and found that the napari functions need to have viewer.close() after each test (even though the showviewer=false) for tests to run right on github actions, even though they consistently work locally.

remove some line returns for consistency.
remove verbose and delay
Copy link
Member

@maliagehan maliagehan left a comment

Choose a reason for hiding this comment

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

repo continuous integration changed to decrease image size. Also found that we needed to add viewer.close() to tests even though viewer does close locally with no error consistently. Additional small changes were also made that were probably originally unnecessary when we were trying to troubleshoot building the repo. Actions now consistently run. Huzzah

@maliagehan maliagehan merged commit d0faaee into main May 16, 2024
5 checks passed
@nfahlgren nfahlgren deleted the diagnose-test-issues branch May 16, 2024 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready to review Ready for code review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants