Recordsgolanggo.opentelemetry.io/otel/sdk/log/logtest
Change the conditions
Current conditions
go.opentelemetry.io/otel/sdk/log/logtest @v0.19.0debian glibc · x64 · go 1.26 · go · go
2 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (2)
- Project observations
- 4 / 4
- Contract verifications
- 2 / 2
- Usage records
- 5
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
2 of 2 passed
Verified — this network ran a contract at this coordinate.
-
go.opentelemetry.io/otel/sdk/log/logtest.RecordFactory
1 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.19.0
linux · go@1.26
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:9d1b94a42bba09c94873c84f78fd1d2c71f292524a851c51abfc9b4e558e5ac0
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.11.1 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| go.opentelemetry.io/otel | v1.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| go.opentelemetry.io/otel/log | v0.19.0 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| go.opentelemetry.io/otel/sdk | v1.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| go.opentelemetry.io/otel/sdk/log | v0.19.0 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| go.opentelemetry.io/otel/trace | v1.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 11 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.