Recordsgolanggolang.org/x/lint
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
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
First observed break
v0.0.0-20190930215403-16217165b5de
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:cc6da42c69d5a8040f6a9dbda27d7d8e0daef42f5c34d1da8e73713061384c8d
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/tools | v0.0.0-20190311212946-11955173bddd | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/tools | v0.0.0-20191029041327-9cc4af7d6b2c | CANDIDATE Correlated change; unproven combination | builds observed | 1 project-day |
| golang.org/x/tools | v0.0.0-20191029190741-b9c20aec41a5 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| golang.org/x/tools | v0.0.0-20200103221440-774c71fcf114 | CANDIDATE Correlated change; unproven combination | builds observed | 6 project-days |
| golang.org/x/tools | v0.6.0 | CANDIDATE Correlated change; unproven combination | contract passed | 10 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.
| Library | v0.0.0-20200302205851-738671d3881b | v0.0.0-20190930215403-16217165b5de | v0.0.0-20190227174305-5b3e6a55c961 |
|---|---|---|---|
| golang.org/x/tools | v0.1.12 | v0.0.0-20191029041327-9cc4af7d6b2c | v0.31.0 |
Moved: 1 · 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.