Open littleskew opened 1 month ago
hey, sorry for the delay. yeah Ginkgo won't filter out the packages when run with tags
. It simply passes tags
to the go compiler. In the case wehre a package is entirely ruled out by the tag rules this will result in a non-existent package and Ginkgo will fail. I don't have a great answer for you other than to use -tags
in tandem with -skip-package
Hello!
It seems to me that there is a problem with running test packages with specific build tags.
I have ginkgo specs in one of my packages and I'm trying to run tests in packages with specific build tags. When I'm doing it with
go test -tags=my_tag ./...
then only tests of underlying packages with the tag//go:build my_tag
are run. But when I useginkgo -v -tags=my_tag ./...
orginkgo build -tags=my_tag ./...
then somewhy Ginkgo is trying to compile all packages with different build tags and fails with the error:Is it expected and I am doing something wrong or is it an existing issue?
This also happens if running ginkgo without
tags
flag but on./...
packages and some of the underlying packages have build tags.Thanks in advance!