Recordsgolanggo.opentelemetry.io/otel/sdk/log/logtest
Change the conditions
Current conditions
go.opentelemetry.io/otel/sdk/log/logtest @v0.22.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 (1)
- Project observations
- 2 / 2
- Contract verifications
- 0 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-16
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 1 passed
Verified — this network ran a contract at this coordinate.
-
go.opentelemetry.io/otel/sdk/log/logtest.RecordFactory
0 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.22.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:48fecfc1a6e73b9fe0097938a1ae54b515c6df64cfb965b80821c81fb35c9de6
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.12.1 | CANDIDATE Correlated change; unproven combination | builds observed | 5 project-days |
| go.opentelemetry.io/otel | v1.46.0 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| go.opentelemetry.io/otel/log | v0.22.0 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| go.opentelemetry.io/otel/sdk | v1.46.0 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| go.opentelemetry.io/otel/sdk/log | v0.22.0 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| go.opentelemetry.io/otel/trace | v1.46.0 | CANDIDATE Correlated change; unproven combination | contract passed | 5 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: 6 · unchanged at every release: 0
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.