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

Increase timeout for integration tests #12203

Merged
merged 1 commit into from
Jul 11, 2022
Merged

Conversation

dmitryax
Copy link
Member

@dmitryax dmitryax commented Jul 9, 2022

Recently introduced TestOracleDBIntegration integration test runs just on the edge on 5 minutes. This change increases the timeout to give it enough time to pass.

Fixes #12202

Recently introduced `TestOracleDBIntegration` integration test runs just on the edge on 5 minutes. This change increases the timeout to give it enough time to pass.
@dmitryax dmitryax requested a review from a team as a code owner July 9, 2022 04:38
@dmitryax dmitryax requested a review from mx-psi July 9, 2022 04:38
@dmitryax dmitryax added the Skip Changelog PRs that do not require a CHANGELOG.md entry label Jul 9, 2022
@@ -4,7 +4,7 @@ SRC_ROOT := $(realpath $(dir $(lastword $(MAKEFILE_LIST))))
# build tags required by any component should be defined as an independent variables and later added to GO_BUILD_TAGS below
GO_BUILD_TAGS=""
GOTEST_OPT?= -race -v -timeout 300s --tags=$(GO_BUILD_TAGS)
GOTEST_INTEGRATION_OPT?= -race -timeout 300s
GOTEST_INTEGRATION_OPT?= -race -timeout 360s
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I worry that increasing this would just encourage others to keep extending what their system does for timeouts.

Is there a way we can add in the ability for a virtual clock or something of that effect if we are testing time based functionality?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see what you're saying but I'm less worried about this than I am with CI stability. Please open an issue with a proposal if you have an idea how this could be implemented.

@@ -4,7 +4,7 @@ SRC_ROOT := $(realpath $(dir $(lastword $(MAKEFILE_LIST))))
# build tags required by any component should be defined as an independent variables and later added to GO_BUILD_TAGS below
GO_BUILD_TAGS=""
GOTEST_OPT?= -race -v -timeout 300s --tags=$(GO_BUILD_TAGS)
GOTEST_INTEGRATION_OPT?= -race -timeout 300s
GOTEST_INTEGRATION_OPT?= -race -timeout 360s
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see what you're saying but I'm less worried about this than I am with CI stability. Please open an issue with a proposal if you have an idea how this could be implemented.

@djaglowski djaglowski merged commit 8c42dea into main Jul 11, 2022
@djaglowski djaglowski deleted the timeout-integration-tests branch July 11, 2022 14:03
atoulme pushed a commit to atoulme/opentelemetry-collector-contrib that referenced this pull request Jul 16, 2022
Recently introduced `TestOracleDBIntegration` integration test runs just on the edge on 5 minutes. This change increases the timeout to give it enough time to pass.
ag-ramachandran referenced this pull request in ag-ramachandran/opentelemetry-collector-contrib Sep 15, 2022
Recently introduced `TestOracleDBIntegration` integration test runs just on the edge on 5 minutes. This change increases the timeout to give it enough time to pass.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Skip Changelog PRs that do not require a CHANGELOG.md entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[receiver/sqlquery] Flaky Test - TestOracleDBIntegration
4 participants