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

rgw: Fix the run-s3tests.sh run in build dir #18966

Closed
wants to merge 1 commit into from

Conversation

inevity
Copy link

@inevity inevity commented Nov 16, 2017

Fixes http://tracker.ceph.com/issues/22141
When run ../qa/workunits/rgw/run-s3tests.sh in ceph build dir,
s3tests.fuzz.test.test_fuzzer.test_load_grap need open
file request_decision_graph.yml,but cannot found as
"1623 graph_file = open('request_decision_graph.yml', 'r')
1624 IOError: [Errno 2] No such file or directory:
'request_decision_graph.yml'"

When run ../qa/workunits/rgw/run-s3tests.sh in ceph build dir, if
terminate the running script,leave the tmp s3-test dir exist.
Now if we again run this script,nosetests will find too many
testcase in previous tmp s3-test dir, and will have relative
import module error such as 'Failure: ImportError
(cannot import name realistic) ... ERROR'

Signed-off-by: baul roidinev@gmail.com

Fixes http://tracker.ceph.com/issues/22141
When run ../qa/workunits/rgw/run-s3tests.sh in ceph build dir,
s3tests.fuzz.test.test_fuzzer.test_load_grap need open
file request_decision_graph.yml,but cannot found as
"1623     graph_file = open('request_decision_graph.yml', 'r')
 1624 IOError: [Errno 2] No such file or directory:
 'request_decision_graph.yml'"

When run ../qa/workunits/rgw/run-s3tests.sh in ceph build dir, if
terminate the running script,leave the tmp s3-test dir exist.
Now if we again run this script,nosetests will find too many
testcase in previous tmp s3-test dir, and will have relative
import module error such as 'Failure: ImportError
(cannot import name realistic) ... ERROR'

Signed-off-by: baul <roidinev@gmail.com>
@inevity
Copy link
Author

inevity commented Nov 16, 2017

@cbodley please help review!

@theanalyst
Copy link
Member

jenkins test this please

@stale
Copy link

stale bot commented Oct 18, 2018

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you are a maintainer or core committer, please follow-up on this issue to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

@stale stale bot added the stale label Oct 18, 2018
@stale
Copy link

stale bot commented Apr 22, 2019

This pull request has been automatically closed because there has been no activity for 90 days. Please feel free to reopen this pull request (or open a new one) if the proposed change is still appropriate. Thank you for your contribution!

@stale stale bot closed this Apr 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants