From: Theo Buehler <tb@theobuehler.org>
Subject: Re: lang/go: use TEST_TARGET for MODGO_TEST_CMD
To: Sebastien Marie <semarie@kapouay.eu.org>
Cc: ports@openbsd.org
Date: Sun, 11 Jan 2026 20:17:20 +0100

On Sun, Jan 11, 2026 at 08:00:01PM +0100, Sebastien Marie wrote:
> Hi,
> 
> The following diff chnages MODGO_TEST_CMD to use TEST_TARGET by default
> for choosing which target to test. While here, also pass TEST_ENV (for
> net/crawley).
> 
> The default value is ALL_TARGET (same default as before).
> 
> It permits to unify several ports to avoid reimplementing MODGO_TEST_CMD
> for running tests on a target different that ALL_TARGET:
> 
> - devel/github-cli
> - devel/gopls
> - devel/goreleaser
> - devel/jjui
> - net/crawley
> - net/dnscrypt-proxy
> - net/headscale
> - security/cfssl
> - security/gosec
> - security/osv-scanner
> - sysutils/direnv
> - sysutils/docker-compose
> - sysutils/fzf
> - sysutils/gitlab-cli
> - sysutils/hcloud
> - sysutils/restic
> - textproc/miller
> - www/goat
> 
> Regarding sysutils/restic, do-test is still overrided to permit
> ${MODGO_FLAGS:N-v}, but I removed "${SETENV} ${MAKE_ENV}" as
> ${MODGO_CMD} already contains them.

ok tb