-
Notifications
You must be signed in to change notification settings - Fork 21
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
Make test timeout "smart" #21
Comments
k3rn31
added a commit
that referenced
this issue
Jul 22, 2022
Signed-off-by: Davide Petilli <[email protected]>
k3rn31
added a commit
that referenced
this issue
Jul 22, 2022
Signed-off-by: Davide Petilli <[email protected]>
k3rn31
added a commit
that referenced
this issue
Jul 23, 2022
Signed-off-by: Davide Petilli <[email protected]>
k3rn31
added a commit
that referenced
this issue
Jul 23, 2022
Signed-off-by: Davide Petilli <[email protected]>
k3rn31
added a commit
that referenced
this issue
Jul 23, 2022
Signed-off-by: Davide Petilli <[email protected]>
k3rn31
added a commit
that referenced
this issue
Jul 23, 2022
Signed-off-by: Davide Petilli <[email protected]>
k3rn31
added a commit
that referenced
this issue
Jul 23, 2022
Signed-off-by: Davide Petilli <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The timeout of the test command is currently fixed. This should be determined dynamically.
One approach could be determining how much time it takes to run the first run for the coverage and use that as a base for the timeout of all the subsequent test runs.
The text was updated successfully, but these errors were encountered: