-
Notifications
You must be signed in to change notification settings - Fork 124
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
Override test duration from plan #1843
Comments
Outcome of the discussion on the hacking session: Create new attribute which will allow to change the duration: either to set explicit value or mathematical operation on existing value ( +1s, +1m, +1h, *1.2 ) Attribute could be used in |
Use case we should cover: One arch is slower than the others so:
|
Lets' aim for next release. |
Has the essential part of the use case been covered by #1972? Currently duration allows to provide multiple values:
So it's possible to use context |
Unfortunatelly we are still missing way how to modify duration from the PLAN, which is necessary when
|
Ah, I see, the plan part is here essential. |
@lukaszachy is this issue going to land in 1.29? I'd propose postponing once more to 1.30. |
Started #2430 |
Status comment:
Not sure if 1.33 is feasible as the third point will require fmf release to happen first. |
As a tester, I may need to modify some libraries that the test uses.
Those instrumentations can significantly change the test duration and I need to be able to run those tests in that scenario without requesting changes in the test fmf file.
A possible solution could be to override the duration using a mathematical operation.
example: duration: *3
example: duration: +1h
The text was updated successfully, but these errors were encountered: