test: use the same measurement in test#240
Merged
Merged
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #240 +/- ##
=======================================
Coverage 90.14% 90.14%
=======================================
Files 19 19
Lines 1126 1126
Branches 177 177
=======================================
Hits 1015 1015
Misses 41 41
Partials 70 70 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
karel-rehor
approved these changes
May 29, 2025
Contributor
karel-rehor
left a comment
karel-rehor
left a comment
There was a problem hiding this comment.
Repeated runs of tests pass locally. Changes make sense. 🚴 🏁
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Use the same measurement name in the integration test, so it does not create new measurement on influxdb server on every test run.
Many test runs in CircleCI caused quota limit error on InfluxDB Cloud Serverless:
as each new measurement created a new table in influxdb: