sumdb/tlog: use recorded responses in TestCertificateTransparency The test fetched proofs from the Google Argon 2020 log over the network. The log is being turned down, and in the meantime requests from the builders are intermittently rejected with an "automated queries" page. The log is frozen, so record its get-sth, get-entries, get-proof-by-hash, and get-sth-consistency responses in testdata and check the proofs against those. The test no longer needs the network, so it also runs in -short mode. Fixes golang/go#60852 Change-Id: I6ef48082c008aac26f485400244bbbd36a6a6964 Reviewed-on: https://go-review.googlesource.com/c/mod/+/848125 LUCI-TryBot-Result: golang-scoped@luci-project-accounts.iam.gserviceaccount.com <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Damien Neil <dneil@google.com> Auto-Submit: Filippo Valsorda <filippo@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
This repository holds packages for writing tools that work directly with Go module mechanics. That is, it is for direct manipulation of Go modules themselves.
It is NOT about supporting general development tools that need to do things like load packages in module mode. That use case, where modules are incidental rather than the focus, should remain in x/tools, specifically x/tools/go/packages.
The specific case of loading packages should still be done by invoking the go command, which remains the single point of truth for package loading algorithms.