We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Running the test suite on Windows amd64 for both Go 1.15 and 1.14:
--- FAIL: TestLastValueMerge (0.00s) --- FAIL: TestLastValueMerge/Int64Kind (0.00s) lastvalue_test.go:116: Error Trace: lastvalue_test.go:116 test.go:75 Error: Should be true Test: TestLastValueMerge/Int64Kind --- FAIL: TestLastValueMerge/Float64Kind (0.00s) lastvalue_test.go:116: Error Trace: lastvalue_test.go:116 test.go:75 Error: Should be true Test: TestLastValueMerge/Float64Kind FAIL FAIL go.opentelemetry.io/otel/sdk/metric/aggregator/lastvalue 0.030s
Looking at the code
opentelemetry-go/sdk/metric/aggregator/lastvalue/lastvalue_test.go
Lines 93 to 125 in 4a163be
Again this looks like we need to add an artificial delay to ensure the checkpoint doesn't happen with the same timestamp.
The text was updated successfully, but these errors were encountered:
MrAlias
Successfully merging a pull request may close this issue.
Running the test suite on Windows amd64 for both Go 1.15 and 1.14:
Looking at the code
opentelemetry-go/sdk/metric/aggregator/lastvalue/lastvalue_test.go
Lines 93 to 125 in 4a163be
Again this looks like we need to add an artificial delay to ensure the checkpoint doesn't happen with the same timestamp.
The text was updated successfully, but these errors were encountered: