Recordsgolanggo.opentelemetry.io/otel/sdkv1.36.0go.opentelemetry.io/otel/sdk/trace/tracetest.InMemoryExporter
Change the conditions
Current conditions
go.opentelemetry.io/otel/sdk/trace/tracetest.InMemoryExporter @v1.36.0ubuntu glibc · x64 · go 1.26 · go 1
0 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 2 / 2
- Contract verifications
- 0 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-10
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.36.0
linux · go@1.26
5 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:c2ae6d87252c4f443f14d40584c4012a25213fbf0bb7b5e35604e6d35d608229
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/go-logr/logr | v1.4.2 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| github.com/go-logr/logr | v1.4.4 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/google/go-cmp | v0.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/stretchr/testify | v1.10.0 | CANDIDATE Correlated change; unproven combination | builds observed | 3 project-days |
| go.opentelemetry.io/otel | v1.36.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| go.opentelemetry.io/otel/trace | v1.36.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/sys | v0.33.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/sys | v0.48.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/google/uuid | v1.6.0 | PASS All observations passed | contract passed | 3 project-days |
| go.uber.org/goleak | v1.3.0 | PASS All observations passed | contract passed | 3 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
Moved: 8 · unchanged at every release: 2
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Recent failure clusters
-
observed PROJECT_COMPILE exit 1 Evidence gap ×5 v1.36.0 → v1.43.0 → v1.46.0 os=linux · runtime=go@1.26 sha256:c2ae6d87252c…go/compiler · build-aggregate · outer go test · gap diagnostic-missingEvidence quality: partial · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-10-10Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×3 v1.36.0 → v1.46.0 os=linux · runtime=go@1.26 go.opentelemetry.io/otel/sdk/trace/tracetest.InMemoryExporter sha256:52ffb5863abb…FAIL: expected span name <str>, got <str> · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-10-10Diagnostic re-verification candidate