mirror of
https://github.com/featurebasedb/featurebase.git
synced 2026-10-07 11:27:50 +00:00
da4fb4ab4e
This gets complicated. For coverage output, sonarcloud supports wildcards. For test output, it doesn't. So we weren't getting meaningful results, just weird error messages. I fixed that, and got thousands of lines of other error messages because it wasn't finding the test source files. That looked like this: WARN: Failed to find test file for package github.com/molecula/featurebase/v3 and test TestTranslation_Primary But we don't actually need the test reports sent to SonarCloud, because "which parts of your test suite are being run" is sort of inherently "basically all of them" with go test. So rather than continuing to do that, we drop it. Since we're dropping that, we don't need the JSON output from go test anymore, so we drop that too, and the tee commands, and the "artifacts" from the tee commands, and now our test output is human-readable and slightly faster. We also bump SonarCloud to 4.7. We also fix the tests to use GOVERSION sometimes and GOFUTURE other times, and bump from 1.19.2 to 1.19.3. Also a couple of minor cleanup (adding explanatory comments, combining adjacent grep commands, etc.)
28 lines
742 B
YAML
28 lines
742 B
YAML
run go tests batch:
|
|
variables:
|
|
PROJECT: batch_${CI_CONCURRENT_ID}
|
|
# this test relies on stuff that happens after build-lattice, which
|
|
# makes it pause the entire CI run waiting for this. we accept the
|
|
# small risk of wasting a build against the near certainty of spending
|
|
# five minutes running only one job.
|
|
stage: nonblocking
|
|
retry: 1
|
|
script:
|
|
- echo "Running test-all"
|
|
- cd ./batch/
|
|
- echo $PROJECT
|
|
- make build-featurebase
|
|
- make test-all
|
|
after_script:
|
|
- cd ./batch/
|
|
- make save-featurebase-logs
|
|
- make shutdown
|
|
artifacts:
|
|
paths:
|
|
- ./batch/testdata/*_coverage.out
|
|
- ./batch/testdata/*_logs.txt
|
|
tags:
|
|
- shell
|
|
- aws
|
|
needs:
|
|
- job: build amd container fb
|