Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Run benchmarks only after linter check using jobs #209

Merged
merged 1 commit into from
Feb 14, 2022

Conversation

shahzadlone
Copy link
Member

@shahzadlone shahzadlone commented Feb 14, 2022

  • Combine the Lint and Benchmark workflows so that the benchmark job depends on the lint job in one workflow.

  • The GOPATH and HOME directory on the custom GitHub runner was not being set be default. Which was giving me: error: missing $GOPATH which is a go bug. You can replicate the same bug on your machine by HOME='' GOPATH='' go test ./..

  • Set HOME for GO stuff to parent directory where our runner checks out our code. i.e. /actions-runner/_work

@source-devs source-devs added area/testing Related to any test or testing suite ci/build This is issue is about the build or CI system, and the administration of it. labels Feb 14, 2022
@source-devs source-devs added this to the DefraDB v0.2.1 milestone Feb 14, 2022
@shahzadlone shahzadlone force-pushed the lone/ci/benchmarks-to-run-after-linter branch from e428956 to 779e9ad Compare February 14, 2022 17:23
@shahzadlone shahzadlone merged commit b93bafe into develop Feb 14, 2022
@shahzadlone shahzadlone deleted the lone/ci/benchmarks-to-run-after-linter branch February 14, 2022 17:40
shahzadlone added a commit to shahzadlone/defradb that referenced this pull request Feb 23, 2024
…b depends on the lint job in one workflow (sourcenetwork#209)

DESCRIPTION:

- Combine the Lint and Benchmark workflows so that the benchmark job depends on the lint job in one workflow.

- The `GOPATH` and `HOME` directory on the custom GitHub runner was not being set be default. Which was giving me: `error: missing $GOPATH` which is a go bug. You can replicate the same bug on your machine by `HOME='' GOPATH='' go test ./..`

- Set HOME for GO stuff to parent directory where our runner checks out our code. i.e. `/actions-runner/_work`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing Related to any test or testing suite ci/build This is issue is about the build or CI system, and the administration of it.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants