8 Commits

Include renames

Author	SHA1	Message	Date
Timothy Messier	e4fbc0281a	chore(ci): Update and pin actions steps	2023-03-29 18:39:01 +00:00
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.	2023-03-20 13:02:40 -04:00
claire labryandSarah Thompson	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>	2023-03-17 11:53:12 -05:00
Michael Li	2169bf7443	chore: Add "fail-on-cache-miss" setting to more jobs (#3072)	2023-03-10 12:17:29 -05:00
Michael Li	e0b50af7c3	chore(enos): Use cache for tparse (#3057)	2023-03-08 10:03:11 -05:00
Timothy Messier	236d7ca872	ci: Additional githubaction configuration (#3034) ... - Pin action versions - Dependabot to notify about action updates - Update codeowners	2023-03-01 08:00:46 -05:00
Timothy Messier	5e0957eb24	ci(test): Use docker mirror (#3018)	2023-02-24 14:49:16 -05:00
3 people	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>	2023-02-23 14:58:40 -05:00