mirror of
https://github.com/minio/minio.git
synced 2024-12-26 23:25:54 -05:00
5c61c3ccdc
On occasion this test fails: ``` 2022-09-12T17:22:44.6562737Z === RUN TestGetObjectWithOutdatedDisks 2022-09-12T17:22:44.6563751Z erasure-object_test.go:1214: Test 2: Expected data to have md5sum = `c946b71bb69c07daf25470742c967e7c`, found `7d16d23f07072af1a809707ba101ae07` 2 ``` Theory: Both objects are written with the same timestamp due to lower timer resolution on Windows. This results in secondary resolution, which is deterministic, but random. Solution: Instead of hacking in a wait we request the specific version we want. Should still keep the test relevant. Bonus: Remote action dependency for vulncheck
27 lines
605 B
YAML
27 lines
605 B
YAML
name: VulnCheck
|
|
on:
|
|
pull_request:
|
|
branches:
|
|
- master
|
|
push:
|
|
branches:
|
|
- master
|
|
jobs:
|
|
vulncheck:
|
|
name: Analysis
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Check out code into the Go module directory
|
|
uses: actions/checkout@v3
|
|
- name: Set up Go
|
|
uses: actions/setup-go@v3
|
|
with:
|
|
go-version: 1.19.x
|
|
check-latest: true
|
|
- name: Get official govulncheck
|
|
run: go install golang.org/x/vuln/cmd/govulncheck@latest
|
|
shell: bash
|
|
- name: Run govulncheck
|
|
run: govulncheck ./...
|
|
shell: bash
|