Take the Go package artifacts out of the delivery parts for now, so the running builder builds them (issue 1966)
The running builder predates Go package artifacts ("refused kind: package of language go ... no build module
builds it"), so it can build neither the new builder, the grants module, the Go build module nor the checker:
each new part is needed before the others can be built or delivered. For the bootstrap of the registry
delivery, at the operator's word (19:4x, "do the temporary change"), the package artifacts leave the manifests of
the parts that run; the contracts and SDK modules, which run on no node, keep theirs. They come back in one change
once the new builder runs. Quick vs thorough: quick; the thorough fix is 47/G's tier order (issue 1921 note 80).
Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
This commit is contained in:
@@ -29,10 +29,6 @@ func TestTheReadingsLayoutIsAPublishedPackageOfThisModule(t *testing.T) {
|
||||
if !slices.Contains(m.Reads, engineDataRead) {
|
||||
t.Errorf("reads %v do not name %s", m.Reads, engineDataRead)
|
||||
}
|
||||
for _, a := range m.Build.Artifacts {
|
||||
if a.Name == "diskreadings" && a.Kind == "package" && a.Series == "0.1" && len(a.Paths) == 1 && a.Paths[0] == "diskreadings" {
|
||||
return
|
||||
}
|
||||
}
|
||||
t.Errorf("no package artifact diskreadings of series 0.1 in %s", raw)
|
||||
// Issue 1966's bootstrap: the package artifact diskreadings is out of the manifest until the new builder runs; the follow-up
|
||||
// puts this check back.
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user