boundary

Commit Graph

Author	SHA1	Message	Date
Timothy Messier	7f7a5ac9c3	ci(test): Remove matrix for running tests per package (#3200 ) The original motivation for the matrix was to mitigate an issue some tests failing that used a vault docker container. When the tests ran in a single step, these tests would almost always fail. By splitting the tests per package, the failure rate of these tests was around 20%. GitHub was able to identify the cause. There was an issue with localhost resolution that causes requests to the vault containers to sometimes fail, resulting in the kinds of failures that were seen. Note that the same issue was not seen when accessing the test postgres database that was running in a container, since the test code connects via 127.0.0.1, while the vault container used localhost. This commit includes the recommended fix so that localhost name resolution works as expected on the GitHub hosted runners. It also removes the test matrix since it is no longer needed as a work around. In addition it seems advisable to remove the matrix given the recent discovery that some tests were not running with the matrix. While this was fixed, removing the matrix reduces the risk of any future mistakes from the test splitting. This also seems to result in a faster pipeline execution time. The overhead to determine the matrix values, wait for a runner to be available, and restore from the cache seems to add up to a longer overall execution time. Eliminating the matrix can also help with another type of failure seen. Sometimes restoring from the cache fails. By eliminating the test matrix, it will greatly reduce the number of cache restoring done by the workflow, which will reduce the chances of an issue restoring from cache. The only remaining benefit from the matrix, was that if there was a transient test failure, a re-run of only the failed jobs would be relatively quick (depending on which package had the failure), while without the matrix the entire test suite will need to be re-run. See: https://github.com/hashicorp/boundary/pull/3199 Refs: `86214a85e1` `e04438b7f8`	3 years ago
hashicorp-tsccr[bot]	cc94accc4f	SEC-090: Automated trusted workflow pinning (2023-04-27) (#3187 ) * Result of tsccr-helper -pin-all-workflows . * chore: Disable cache from setup-go --------- Co-authored-by: hashicorp-tsccr[bot] <hashicorp-tsccr[bot]@users.noreply.github.com> Co-authored-by: Michael Li <michael.li@hashicorp.com>	3 years ago
dependabot[bot]	8c265bf7c1	chore(deps): bump actions/cache from 3.2.6 to 3.3.1 (#3131 ) Bumps [actions/cache](https://github.com/actions/cache) from 3.2.6 to 3.3.1. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](`69d9d449ac...88522ab9f3`) --- updated-dependencies: - dependency-name: actions/cache dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	3 years ago
Timothy Messier	e4fbc0281a	chore(ci): Update and pin actions steps	3 years ago
Michael Li	87c80f99dc	chore: Remove extraneous fail-on-cache-miss attribute (#3104 ) Since this step is a setup step, there shouldn't be an expectation that the cache is present. Removing this attribute gets rid of that requirement.	3 years ago
claire labry	bf955b60d4	Try retries on test failures (#3099 ) * try-retries-on-test-failures * remove extra step * fix spacing * Pin retry action and fix merge conflict * Update test.yml * Uses before name * hopefully this works --------- Co-authored-by: Sarah Thompson <sthompson@hashicorp.com>	3 years ago
Michael Li	2169bf7443	chore: Add "fail-on-cache-miss" setting to more jobs (#3072 )	3 years ago
Michael Li	e0b50af7c3	chore(enos): Use cache for tparse (#3057 )	3 years ago
Timothy Messier	236d7ca872	ci: Additional githubaction configuration (#3034 ) - Pin action versions - Dependabot to notify about action updates - Update codeowners	3 years ago
Timothy Messier	5e0957eb24	ci(test): Use docker mirror (#3018 )	3 years ago
Timothy Messier	86214a85e1	ci: Run go tests in github action (#2997 ) This runs the make targets: - make test - make test-api - make test-sdk The go tests in the main module are split by package and run in parallel in a matrix build with GOMAXPROCS=1. This is done primarily to work around an issue that is only seen on the github runners. When running at a higher GOMAXPROCS tests that use vault instances in docker containers start to intermitently fail with errors from vault, usually either a 400, 403, or TLS error. It is not clear what the cause of this is, since the same tests run fine on self hosted runners and on CircleCI. Co-authored-by: Sarah Thompson <sthompson@hashicorp.com> Co-authored-by: Daniel Kimsey <daniel.kimsey@hashicorp.com>	3 years ago

11 Commits (ace2def49dce2971ce37db44d94faac0e2289bb7)