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]Test TempoStack global and per-component resources allocation #994

Merged
merged 3 commits into from
Aug 2, 2024

Conversation

IshwarKanse
Copy link
Contributor

The test will help us to detect regression in setting the resources for the components.

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

@IshwarKanse IshwarKanse changed the title Test TempoStack global and per-component resources allocation [Chore]Test TempoStack global and per-component resources allocation Jul 26, 2024
@codecov-commenter
Copy link

codecov-commenter commented Jul 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.16%. Comparing base (8008b1f) to head (fb08665).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #994   +/-   ##
=======================================
  Coverage   73.16%   73.16%           
=======================================
  Files         106      106           
  Lines        6606     6606           
=======================================
  Hits         4833     4833           
  Misses       1480     1480           
  Partials      293      293           
Flag Coverage Δ
unittests 73.16% <ø> (ø)

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.

@IshwarKanse
Copy link
Contributor Author

cc @rubenvp8510

@andreasgerstmayr andreasgerstmayr merged commit 4fb083e into grafana:main Aug 2, 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.

5 participants