aboutsummaryrefslogtreecommitdiff
path: root/internal/postgres/delete_test.go
AgeCommit message (Collapse)Author
2025-04-01internal/postgres: use a more straightforward return valuecuishuang
Change-Id: I954ebf3d4908839e7c7e746b142127887fd936c5 Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/653216 Auto-Submit: Carlos Amedee <carlos@golang.org> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Robert Findley <rfindley@google.com> kokoro-CI: kokoro <noreply+kokoro@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2023-08-23all: remove arbitrary hard-coded timeouts in testsBryan C. Mills
If a test times out, that implies that it got stuck on something. By default, the Go testing package dumps goroutines when its own timeout is passed, which prints a goroutine dump, helping to reveal what was stuck. Adding an arbitrary timeout on top of the testing package's own timeout is, in my experience, almost always counterproductive. If the arbitrary timeout catches a real hang, it causes the test to fail instead of dumping goroutines, making it much harder to see what was stuck. On the other hand, if the timeouts are set aggressively enough to make the test fail early, they are often too aggressive for CI testing, causing flakes that then have to be triaged on an ongoing basis. On balance, the value of saving a minute or two for developers who have introduced a hang is not worth the cost of suppressing debugging information and causing flakes that have to be triaged. Fixes #61556. For #59347. Change-Id: I0263d0d9b18283470f100e5a0155818b87b5312f Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/521837 TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> kokoro-CI: kokoro <noreply+kokoro@google.com> Reviewed-by: Michael Matloob <matloob@golang.org>
2022-03-07internal/database: use generics for Collect functionsJonathan Amsterdam
Reimplement some reflection-based collection functions to use generics. In some cases we still need reflection, but at least we can provide a type-safe wrapper with generics. Change-Id: Id95949a7a22ee687166ecdfc1191150d79568889 Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/389657 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: kokoro <noreply+kokoro@google.com> Reviewed-by: Jamal Carvalho <jamal@golang.org>
2021-08-16internal/postgres: split deleteModuleOrPackagesInModuleFromSearchDocumentsJulie Qiu
deleteModuleOrPackagesInModuleFromSearchDocuments is split into deleteModuleFromSearchDocuments and deletePackagesInModuleFromSearchDocuments to reduce confusion as to which query is being executed. Change-Id: I4559d812f54401857a153aa52166c12f228f6354 Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/342631 Trust: Julie Qiu <julie@golang.org> Reviewed-by: Jonathan Amsterdam <jba@google.com>
2021-08-16internal/{worker,postgres}: remove DeleteOlderVersionFromSearchDocumentsJonathan Amsterdam
Thanks to the recent change to ReconcileSearch to handle the current module version being alternative, this is no longer necessary. Change-Id: I0c1e1fa917de349496c20c4e0bc101c703853490 Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/342171 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: kokoro <noreply+kokoro@google.com> Reviewed-by: Julie Qiu <julie@golang.org>
2021-08-13internl/postgres: move delete functions into delete.goJonathan Amsterdam
Pure code motion. Change-Id: I80055dbb95f2341c72d3716b74e08335bdaa6fd4 Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/341851 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: kokoro <noreply+kokoro@google.com> Reviewed-by: Julie Qiu <julie@golang.org>
2021-04-08internal/postgres,etc: finish MustInsertModule cleanupJonathan Amsterdam
Now that there are no callers of MustInsertModule, rename MustInsertModuleLatest to MustInsertModule. We can also remove MustInsertModuleLMV. Change-Id: Ieb554ee32696c168be4cc0a14ecece9f4c6b91b4 Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/308271 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> Reviewed-by: Jamal Carvalho <jamal@golang.org>
2021-04-07internal/postgres: use MustInsertModuleLatestJonathan Amsterdam
For most internal/postgres tests, update latest-version information when we insert a module. That is more like what actually happens on the worker, and some features now rely on it, so we should do it everywhere. Some tests still use a custom go.mod file, so we can't switch to MustInsertModuleLatest for those, because it uses a minimal go.mod file. Change-Id: Ie5030aee4ed9c837931fddb8757e37bf6373a8c7 Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/307871 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> Reviewed-by: Julie Qiu <julie@golang.org> TryBot-Result: kokoro <noreply+kokoro@google.com>
2021-02-22internal/postgres,worker: schedule fetching of std@masterJulie Qiu
In order to ensure that pkg.go.dev/std@master is always showing the latest version, an endpoint is added which checks for the most recent version of std@master. If the version in our database is not up to date, a fetch request is scheduled. Additionally, since only the most recent pseudoversion of std is ever shown on pkg.go.dev, older versions are deleted. For golang/go#44390 Change-Id: Iad56b8653f378fb5a7d72a1e30505da090de279d Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/294350 Trust: Julie Qiu <julie@golang.org> Run-TryBot: Julie Qiu <julie@golang.org> TryBot-Result: kokoro <noreply+kokoro@google.com> Reviewed-by: Jonathan Amsterdam <jba@google.com>