Merge lp:~psivaa/uci-engine/swift-failure-exposure into lp:uci-engine
Status: | Merged |
---|---|
Approved by: | Para Siva |
Approved revision: | 915 |
Merged at revision: | 914 |
Proposed branch: | lp:~psivaa/uci-engine/swift-failure-exposure |
Merge into: | lp:uci-engine |
Diff against target: |
98 lines (+64/-0) 2 files modified
test_runner/tstrun/run_worker.py (+4/-0) test_runner/tstrun/tests/test_worker.py (+60/-0) |
To merge this branch: | bzr merge lp:~psivaa/uci-engine/swift-failure-exposure |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Vincent Ladeuil (community) | Approve | ||
Joe Talbott (community) | Approve | ||
Review via email: mp+245745@code.launchpad.net |
Commit message
To ensure that we do not swallow the swiftclient related exceptions in the test runner worker
Description of the change
To ensure that we do not swallow the swiftclient related exceptions in the test runner worker. Any client error response in swiftclient during file uploads (save_artefact) is raised in data_store as an exception and this MP disables catching that exception in test runner.
The failure analysis, in http://
1. PUT can fail with 401 (tested with this MP)
2. ail to upload because we can't reset content (this should also raise client exception and therefore will be tested with the same test)
3. Failure due to connecting to keystone (this is being handled by some other tasks)
This looks good to me.