-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Expose storage integration helpers as go pkg #3944
Conversation
Codecov ReportBase: 97.68% // Head: 97.13% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #3944 +/- ##
==========================================
- Coverage 97.68% 97.13% -0.56%
==========================================
Files 293 295 +2
Lines 17080 17389 +309
==========================================
+ Hits 16684 16890 +206
- Misses 313 401 +88
- Partials 83 98 +15
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
perhaps we should add The
|
cdef2ab
to
fb036e4
Compare
This commit exposes storage integration test helpers as golang packages so that out of tree grpc storage implementations can import and run tests from their context. Prior to this change out of tree implementations copies these files into their repo[1]. This is not good in terms of keeping fixtures upto date. This commit does the following, - Rename test helper files(integration_test.go => integration.go, trace_compare_test.go => test_compare.go) to expose those as go packages. - Use `go embed` instead of `os.ReadFile` package to read test fixtures, this helps to reuse fixtures - Add a field in StorageIntegration struct to skip tests [1] https://github.com/jaegertracing/jaeger-clickhouse/tree/main/integration Signed-off-by: Arunprasad Rajkumar <[email protected]>
fb036e4
to
584e107
Compare
my bad, |
This commit reuses fixtures from upstream jaeger[1] which is exposed as golang pkg. Though we use non release version v1.38.2-0.20221006002917-5bf8a28fe06d, it doesn't have any other changes except [1] which is safe. [1] jaegertracing/jaeger#3944 Signed-off-by: Arunprasad Rajkumar <[email protected]>
This commit reuses fixtures from upstream jaeger[1] which is exposed as golang pkg. Though we use non release version v1.38.2-0.20221006002917-5bf8a28fe06d, it doesn't have any other changes except [1] which is safe. [1] jaegertracing/jaeger#3944 Signed-off-by: Arunprasad Rajkumar <[email protected]>
This commit reuses fixtures from upstream jaeger[1] which is exposed as golang pkg. Though we use non release version v1.38.2-0.20221006002917-5bf8a28fe06d, it doesn't have any other changes except [1] which is safe. [1] jaegertracing/jaeger#3944 Signed-off-by: Arunprasad Rajkumar <[email protected]>
Thanks @yurishkuro |
This commit reuses fixtures from upstream jaeger[1] which is exposed as golang pkg. Though we use non release version v1.38.2-0.20221006002917-5bf8a28fe06d, it doesn't have any other changes except [1] which is safe. [1] jaegertracing/jaeger#3944 Signed-off-by: Arunprasad Rajkumar <[email protected]>
This commit reuses fixtures from upstream jaeger[1] which is exposed as golang pkg. Though we use non release version v1.38.2-0.20221006002917-5bf8a28fe06d, it doesn't have any other changes except [1] which is safe. [1] jaegertracing/jaeger#3944 Signed-off-by: Arunprasad Rajkumar <[email protected]>
This commit reuses fixtures from upstream jaeger[1] which is exposed as golang pkg. Though we use non release version v1.38.2-0.20221006002917-5bf8a28fe06d, it doesn't have any other changes except [1] which is safe. [1] jaegertracing/jaeger#3944 Signed-off-by: Arunprasad Rajkumar <[email protected]>
This commit reuses fixtures from upstream jaeger[1] which is exposed as golang pkg. Though we use non release version v1.38.2-0.20221006002917-5bf8a28fe06d, it doesn't have any other changes except [1] which is safe. [1] jaegertracing/jaeger#3944 Signed-off-by: Arunprasad Rajkumar <[email protected]>
Which problem is this PR solving?
gRPC storage implementations which lives out of tree has to copy integration test helpers and fixtures.
Short description of the changes
This commit exposes storage integration test helpers as golang packages so that out of tree grpc storage implementations can import and run tests from their context.
Prior to this change out of tree implementations copies these files into their repo[1]. This is not good in terms of keeping fixtures upto date.
This commit does the following,
go embed
instead ofos.ReadFile
package to read test fixtures, this helps to reuse fixtures[1] https://github.com/jaegertracing/jaeger-clickhouse/tree/main/integration
Signed-off-by: Arunprasad Rajkumar [email protected]