testutil: fixed compose files #3397
Merged
Conversation
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
KaloyanTanev
approved these changes
Dec 3, 2024
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3397 +/- ##
==========================================
- Coverage 57.35% 57.28% -0.07%
==========================================
Files 217 217
Lines 31977 31977
==========================================
- Hits 18340 18319 -21
- Misses 11745 11765 +20
- Partials 1892 1893 +1 ☔ View full report in Codecov by Sentry. |
pinebit
added
the
merge when ready
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The problem was that our compose tool could not start a cluster:
compose new && compose auto.Our compose tool used
latestselector in docker compose and this made the provided config files incompatible. I copied loki config from CDVN and set explicit Grafana stack versions from CDVN as well.This seems fixed the problem.
category: bug
ticket: none