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

Rest assured timeouts are way too big #11769

Closed
galderz opened this issue Sep 1, 2020 · 0 comments · Fixed by #12127
Closed

Rest assured timeouts are way too big #11769

galderz opened this issue Sep 1, 2020 · 0 comments · Fixed by #12127
Labels
kind/bug Something isn't working
Milestone

Comments

@galderz
Copy link
Member

galderz commented Sep 1, 2020

All quarkus tests should timeout way before 30 minutes (see example). Test, or Rest Assured, should be globally configured to be much smaller (1 minute?).

This issue originates in #11768.

In this particular case, I used the following code to generate Rest Assured configuration (valid in 4.3) that would time out before:

static RestAssuredConfig shortTimeoutConfig()
{
    return RestAssured.config().httpClient(
        httpClientConfig()
            .setParam(ClientPNames.CONN_MANAGER_TIMEOUT, 30_000L)
            .setParam(CoreConnectionPNames.CONNECTION_TIMEOUT, 30_000)
            .setParam(CoreConnectionPNames.SO_TIMEOUT, 30_000)
    );
}

Then, I'd do:

RestAssured
    .given()
    .config(shortTimeoutConfig())
    .filter(cookies)
    ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants