CodeSampleX

Recordsgolanggithub.com/stretchr/testify

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Package versionv1.8.4 Package managergo
Filter Runtimego 1.26 Architecturex64 Execution contextgo Clear filters
OS × Symbol
32026-09-16

The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".

How to read the grid

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

  • no sample at this coordinate yet
  • there is a sample here, and nothing of ours has run it at this coordinate yet
  • there is a sample here, and our run of it at this coordinate came back clean
  • there is a sample here, and our run of it at this coordinate failed
  • there is a sample here, and this coordinate records both a passing and a failing run of it
  • nothing recorded — unknown, never "works" and never "broken"
  • there is a level below this cell — click to open it

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 0

First observed break

v1.8.4

linux · go@1.26

1 FAIL · stage: PROJECT_RESOLVE · fingerprint: sha256:0d0008e28623e9034188952536d3dfc4117413e9d6072aa156fa747fc5f58385

Library Version Health Measured there Projects
github.com/davecgh/go-spew v1.1.1 CANDIDATE Correlated change; unproven combination contract passed 30 project-days
github.com/pmezard/go-difflib v1.0.0 CANDIDATE Correlated change; unproven combination contract passed 30 project-days
github.com/stretchr/objx v0.5.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
github.com/stretchr/objx v0.5.2 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
github.com/stretchr/objx v0.5.3 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
gopkg.in/yaml.v3 v3.0.1 CANDIDATE Correlated change; unproven combination contract passed 30 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: 5 · unchanged at every release: 1

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.