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

[Chore] Long running test for TempoStack global retention #1035

Merged
merged 2 commits into from
Sep 27, 2024

Conversation

IshwarKanse
Copy link
Contributor

The PR adds a long running test for TempoStack retention.

--- PASS: chainsaw (0.00s)
    --- PASS: chainsaw/tempostack-retention-global (2860.06s)
PASS
Tests Summary...
- Passed  tests 1
- Failed  tests 0
- Skipped tests 0
Done.

@IshwarKanse IshwarKanse changed the title Long running test for TempoStack global retention [Chore] Long running test for TempoStack global retention Sep 24, 2024
@codecov-commenter
Copy link

codecov-commenter commented Sep 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.10%. Comparing base (0c5313e) to head (bbbff00).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1035   +/-   ##
=======================================
  Coverage   73.10%   73.10%           
=======================================
  Files         106      106           
  Lines        6630     6630           
=======================================
  Hits         4847     4847           
  Misses       1493     1493           
  Partials      290      290           
Flag Coverage Δ
unittests 73.10% <ø> (ø)

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

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

@iblancasa iblancasa merged commit 432cea6 into grafana:main Sep 27, 2024
11 checks passed
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.

3 participants