Recordsgolanggithub.com/sirupsen/logrusfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
assertion 5 failed: expected <str> field in output, got: map[error:contract failure simulation level:panic msg:error test entry time:<timestamp>] …
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-19 · Last seen: 2026-09-19
sha256:9ba0691efd15…
github.com/sirupsen/logrus.Entry github.com/sirupsen/logrus.ErrorLevel github.com/sirupsen/logrus.FieldKeyLevel github.com/sirupsen/logrus.FieldKeyLogrusError github.com/sirupsen/logrus.FieldKeyMsg github.com/sirupsen/logrus.FieldKeyTime github.com/sirupsen/logrus.FieldMap github.com/sirupsen/logrus.Fields github.com/sirupsen/logrus.InfoLevel github.com/sirupsen/logrus.JSONFormatter github.com/sirupsen/logrus.New github.com/sirupsen/logrus.TextFormatter github.com/sirupsen/logrus.WarnLevel
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-19 → 2026-09-19
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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 | v1.9.3 | v1.8.1 | v1.6.0 | v1.4.2 |
|---|---|---|---|---|
| github.com/konsorten/go-windows-terminal-sequences | — | — | v1.0.3 | v1.0.1 |
| github.com/stretchr/testify | v1.7.0 | — | v1.2.2 | v1.4.0 |
| golang.org/x/sys | v0.31.0 | — | v0.47.0 | v0.18.0 |
Moved: 3 · 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.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/sirupsen/logrus v1.4.2: ErrorLevel This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/sirupsen/logrus.ErrorLevelgo 1.26.6 MIT-0 · 2026-10-09
- github.com/sirupsen/logrus v1.4.2: WithFields This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/sirupsen/logrus.WithFields MIT-0 · 2026-09-17
- github.com/sirupsen/logrus v1.4.2: WarnLevel This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/sirupsen/logrus.WarnLevel MIT-0 · 2026-09-17