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

Handle potential xtriage failures during html report generation #2180

Merged
merged 9 commits into from
Jul 29, 2022

Conversation

jbeilstenedmands
Copy link
Contributor

Can occur for very minimal data, as shown by xia2 tests...

@jbeilstenedmands jbeilstenedmands enabled auto-merge (squash) July 26, 2022 15:19
@codecov
Copy link

codecov bot commented Jul 26, 2022

Codecov Report

Merging #2180 (2e75360) into main (58c33d2) will decrease coverage by 0.05%.
The diff coverage is 84.21%.

❗ Current head 2e75360 differs from pull request most recent head 99d2542. Consider uploading reports for the commit 99d2542 to get more accurate results

@@            Coverage Diff             @@
##             main    #2180      +/-   ##
==========================================
- Coverage   80.67%   80.61%   -0.06%     
==========================================
  Files         588      588              
  Lines       66574    66581       +7     
  Branches     9381     9384       +3     
==========================================
- Hits        53709    53677      -32     
- Misses      10791    10830      +39     
  Partials     2074     2074              

@jbeilstenedmands jbeilstenedmands enabled auto-merge (squash) July 29, 2022 12:54
@jbeilstenedmands jbeilstenedmands merged commit 3543e58 into main Jul 29, 2022
@jbeilstenedmands jbeilstenedmands deleted the merge_xtriage_fail branch July 29, 2022 13:22
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.

None yet

2 participants