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

Correct registration of RepeatDateTime serialisation ECFLOW-1992 #137

Merged
merged 1 commit into from
Nov 29, 2024

Conversation

marcosbento
Copy link
Collaborator

No description provided.

@marcosbento marcosbento marked this pull request as ready for review November 29, 2024 09:22
@codecov-commenter
Copy link

Codecov Report

Attention: Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.

Please upload report for BASE (hotfix/5.13.6@66aadf8). Learn more about missing BASE report.

Files with missing lines Patch % Lines
libs/core/src/ecflow/core/Chrono.cpp 0.00% 6 Missing ⚠️
Additional details and impacted files
@@               Coverage Diff                @@
##             hotfix/5.13.6     #137   +/-   ##
================================================
  Coverage                 ?   48.84%           
================================================
  Files                    ?     1184           
  Lines                    ?    98267           
  Branches                 ?    14778           
================================================
  Hits                     ?    47996           
  Misses                   ?    50271           
  Partials                 ?        0           

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

@marcosbento marcosbento merged commit a36bea6 into hotfix/5.13.6 Nov 29, 2024
102 of 103 checks passed
@marcosbento marcosbento deleted the fix/correct_repeatdatetime_serialisation branch November 29, 2024 13:15
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