Skip to content

Conversation

@bsyrowik
Copy link
Contributor

Motivation

The original timeout worked well when the test machines were not too busy. More time is needed for the smoke tests when the test machines are very busy.

Technical Details

Test Plan

Test Result

Submission Checklist

    When the test machines are busy this can take a lot longer.
@bsyrowik
Copy link
Contributor Author

# If we need something even faster we can use "/smoke" here.
test_subdir = "/regression"
timeout = "300"
timeout = "900"
Copy link
Member

Choose a reason for hiding this comment

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

This PR has conflicts to resolve now, fyi.

d4fd7cb increased the timeout to 720. Do we still want 900?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I suspect the 12min timeout will be sufficient. Once the refs are bumped in rocm-libraries we should have a better idea. I'll keep this open until we know it's not necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: TODO

Development

Successfully merging this pull request may close these issues.

4 participants