CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/sdk/log/logtestv0.19.0go.opentelemetry.io/otel/sdk/log/logtest.RecordFactory

Change the conditions
Fixed
Symbolgo.opentelemetry.io/otel/sdk/log/logtest.RecordFactory Package managergo
Filter OSdebian glibc Runtimego 1.26 Package versionv0.19.0 Architecturex64 Execution contextgo libcglibc Clear filters

Current conditions

go.opentelemetry.io/otel/sdk/log/logtest.RecordFactory @v0.19.0debian glibc · x64 · go 1.26 · go · go

1 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 came back clean (1)

Project observations
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 0

First observed break

v0.19.0

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:9d1b94a42bba09c94873c84f78fd1d2c71f292524a851c51abfc9b4e558e5ac0

View exact conditions View failure cluster
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.

Libraryv0.22.0v0.19.0
github.com/stretchr/testify v1.12.1 v1.11.1
go.opentelemetry.io/otel v1.46.0 v1.43.0
go.opentelemetry.io/otel/log v0.22.0 v0.19.0
go.opentelemetry.io/otel/sdk v1.46.0 v1.43.0
go.opentelemetry.io/otel/sdk/log v0.22.0 v0.19.0
go.opentelemetry.io/otel/trace v1.46.0 v1.43.0

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.

Recent failure clusters