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

Special status for not running container #377

Merged
merged 1 commit into from
Apr 13, 2021

Conversation

romasku
Copy link
Contributor

@romasku romasku commented Apr 12, 2021

No description provided.

@romasku romasku force-pushed the rs/special-status-for-not-running-container branch from 456c20f to dc7312c Compare April 12, 2021 20:58
@codecov
Copy link

codecov bot commented Apr 12, 2021

Codecov Report

Merging #377 (dc7312c) into master (867b84f) will decrease coverage by 0.29%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #377      +/-   ##
==========================================
- Coverage   90.36%   90.07%   -0.30%     
==========================================
  Files          11       11              
  Lines        1516     1522       +6     
  Branches      169      170       +1     
==========================================
+ Hits         1370     1371       +1     
- Misses        112      115       +3     
- Partials       34       36       +2     
Flag Coverage Δ
integration 83.96% <100.00%> (-0.27%) ⬇️
unit 51.83% <50.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
platform_monitoring/api.py 78.83% <100.00%> (-0.47%) ⬇️
platform_monitoring/jobs_service.py 96.85% <100.00%> (-1.03%) ⬇️

@romasku romasku merged commit 05ff0c9 into master Apr 13, 2021
@romasku romasku deleted the rs/special-status-for-not-running-container branch April 13, 2021 06:53
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