jschoubben
175b2cd791
mesh-build-node kept the first fifteen lines of node --test's output, so a passing line of the first file stood for the failure. Both build modules now parse through the SDK (go test -json, node --test's TAP report written to a file, the type-check and go vet as console failures), name themselves in the result, and run the SDK's captured cases; the catalogue check failurekit refuses a node-build-* module with a test step whose tests do not run the kit.
32 lines
2.7 KiB
Plaintext
32 lines
2.7 KiB
Plaintext
Each file is the standard output of `GOTOOLCHAIN=go1.27.1 GOFLAGS=-mod=mod go test -count=1 -json ./...` (go1.27.1)
|
|
run in the fixture module of the same name under ../repos, captured on 2026-10-20 for issue 1290. The unit
|
|
tests feed them to the parser through a fake runner, so no test here runs `go test`. twofailing.json was captured the
|
|
same way on 2026-10-24 for issue 1921: two packages with a failing test each, and a passing test beside one of them.
|
|
|
|
golist-external.json is `GOTOOLCHAIN=go1.27.1 GOFLAGS=-mod=mod go list -json=ImportPath,Standard,DepOnly,Module
|
|
git.novox.be/novox/mesh-sdk/go/buildstep` run in this module (go1.27.1, 2026-10-20 for issue 1291): a package of a module
|
|
outside the tree as go list describes it.
|
|
|
|
toolchain-go-entry.txt is lines 155-191 of mesh-control's internal/builder/toolchain.go at origin/main 073ccc29 (fetched
|
|
2026-10-20): the Go entry of today's build agent's recipe, which the build step's flags are compared with.
|
|
|
|
repos/archive is a module tree (modules/demo, an archive artifact "files" from `files`, with an executable and a nested
|
|
file). Its digest, sha256:9503d3f9...6443, is what mesh-controller's `pack` (internal/builder/builder.go, the function
|
|
build-agent packs every archive with) answers for modules/demo/files: captured on 2026-10-21 for issue 1589 by a
|
|
throwaway test beside `pack` in a detached worktree of origin/main c8539bf3 that called `pack` on that directory and
|
|
printed the sha256 of its bytes (not kept).
|
|
upstream-release.tar.gz is a tar made with `tar --sort=name --mtime=@0 --owner=0 --group=0 -czf` of release/app/x.txt and
|
|
release/app/bin/tool (mode 755). Its pinned sha256 is 2c9e5753...7e95 (`sha256sum`). The digests of the archive packed from
|
|
it are what build-agent's `unpackUpstream(file, dir, "release/app")` followed by `pack(dir)` answers (9bacf4aa...790f),
|
|
and what `pack` answers for a directory holding the file as `tool.bin` (`file: tool.bin`; 0d605adb...716b), captured the
|
|
same way and the same day.
|
|
|
|
The tar streams (the archives gunzipped) of the three archives above, captured the same way (build-agent's `pack`, then
|
|
gunzip and sha256) at origin/main 0205b8f7 on 2026-10-21: directory f8af1d94...d1b6, within 294e2bec...07fb, file
|
|
055cffc2...428e. The digests above hold the gzip bytes of go1.27.1. The first try of issue 1589 on the merge check's build node answered
|
|
other digests; the tests therefore compare the stream always and the digest only under go1.27.1.
|
|
|
|
The go-test-json-*.jsonl captures of issue 1901 (2026-10-23 and 2026-10-25) moved to mesh-sdk's conformance kit
|
|
(go/buildstep/conformance/captured/go, with their description) on 2026-10-26, with the reader they test: the build module
|
|
reads go test -json through buildstep.ReadGoTest and runs the kit (kit_test.go).
|