-
Notifications
You must be signed in to change notification settings - Fork 309
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
DAOS-16845 test: update tests to use check_free_space #15553
base: master
Are you sure you want to change the base?
Conversation
Ticket title is 'nvme/enospace.py:NvmeEnospace.test_enospace_time_with_fg - ior MPI_Abort No space left on device' |
Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15553/1/execution/node/936/log |
5e01c20
to
df36132
Compare
Test stage Functional Hardware Medium completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-15553/2/testReport/ |
6cb9368
to
95c74d7
Compare
Test stage Functional Hardware Medium completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-15553/5/testReport/ |
6d8f4b9
to
1969be3
Compare
Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15553/8/execution/node/926/log |
1969be3
to
3f8fef7
Compare
ab53a47
to
d946766
Compare
Test stage Functional Hardware Medium completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-15553/11/testReport/ |
14a40d4
to
03103ab
Compare
Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15553/13/execution/node/926/log |
03103ab
to
b011e05
Compare
Test stage Functional Hardware Medium completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-15553/14/testReport/ |
6940434
to
72c2f37
Compare
Update tests to use pool.check_free_space to dynamicall wait for pool aggregation. Test-tag: test_enospace_time_with_fg DfuseSpaceCheck MultipleContainerDelete Test-repeat: 3 Skip-unit-tests: true Skip-fault-injection-test: true Signed-off-by: Dalton Bohning <[email protected]>
72c2f37
to
a520737
Compare
aggregation: | ||
scm_threshold_percent: 99 # percent of scm expected to be reclaimed after aggregation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be standard for other tests too. E.g.
daos/src/tests/ftest/erasurecode/restart.yaml
Lines 56 to 57 in 6246853
aggregation: | |
threshold: "70%" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have locally tested as I was afraid that dmg pool query
was not providing the "real" available size.
At the end, it seems to be trustful :-)
However, it would also a good thing to also change the other time.sleep(60)
from line 588 of the file enospace.py
Test-tag: test_enospace_time_with_fg DfuseSpaceCheck MultipleContainerDelete test_enospace_lazy_with_fg Test-repeat: 3 Skip-unit-tests: true Skip-fault-injection-test: true Signed-off-by: Dalton Bohning <[email protected]>
46591f9
Gah I overlooked that one. Updated. Testing now |
Need to resolve conflicts now |
Test-tag: test_enospace_time_with_fg DfuseSpaceCheck MultipleContainerDelete test_enospace_lazy_with_fg Test-repeat: 1 Skip-unit-tests: true Skip-fault-injection-test: true Signed-off-by: Dalton Bohning <[email protected]>
860b76e
Update tests to use pool.check_free_space to dynamically wait for pool aggregation.
Test-tag: test_enospace_time_with_fg DfuseSpaceCheck MultipleContainerDelete
Skip-unit-tests: true
Skip-fault-injection-test: true
Signed-off-by: Dalton Bohning [email protected]
Before requesting gatekeeper:
Features:
(orTest-tag*
) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.Gatekeeper: