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

Guard some smoke tests behind CI flag? #2058

Closed
anuraaga opened this issue Jan 15, 2021 · 2 comments · Fixed by #2385
Closed

Guard some smoke tests behind CI flag? #2058

anuraaga opened this issue Jan 15, 2021 · 2 comments · Fixed by #2385
Labels
area:build Issues about build infra, both local and central area:tests enhancement New feature or request

Comments

@anuraaga
Copy link
Contributor

When developing, especially for infrastructure work like updating dependencies, it's nice to run ./gradlew check to make sure everything is fine. But currently smoke tests take 15+min on Mac (presumably Docker is much slower on Mac than on CI), and actually fail with a timeout for me. I guess many of the tests are sort of "for good measure", I'm thinking the many app servers. Does it make sense to slice them out to only run on CI?

@anuraaga anuraaga added the enhancement New feature or request label Jan 15, 2021
@trask
Copy link
Member

trask commented Jan 15, 2021

Makes sense to me, maybe all smoke tests, just to make it easy to doc/explain, instead of slicing out only some of them.

I don't think it's too surprising to have to opt in to running smoke tests.

@anuraaga
Copy link
Contributor Author

Yeah SpringBootSmokeTest used to be my standard to make sure the actual agent works properly. Now that normal tests do that, indeed just disabling default smoke tests entirely is probably fine too.

@iNikem iNikem added area:build Issues about build infra, both local and central area:tests labels Jan 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:build Issues about build infra, both local and central area:tests enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants