Bug #5893
closed
failures in s3 tests but teuthology task still passes
Added by Anonymous over 10 years ago.
Updated over 10 years ago.
Description
In a dev branch, I had the read tests for s3 fail but the overall teuthology task passed. This seems like a pretty big issue and I"m looking into it but I wanted to open a ticket in case others were seeing similar behavior.
I've attached archive contents from a run that displays this behavior.
Files
So the error I'm seeing is when the s3readwrite test goes to read an object and doesn't find it (due to a YAML issue I think).
Exceptions in the reader() method in s3-tests/s3tests/readwrite.py are being turned into objects in the queue and printed out (via yaml.safe_dump_all) but the s3readwrite task itself is not raising an exception, so the calling method doesn't know about the failures. I created the s3-tests branch 'wip-buck-all-exceptions' that only populates the queue with error objects. This branch can be used with the next branch and the s3readwrite test to get a passing teuthology run (highlighting the issue).
I've made some changes to my wip-buck-next-2 that iterates through the elements in and raises an exception if any of the objects have an 'error' key in them. I'm enlisting help to make sure the changes are properly 'pythonic'.
Commit 9799858e90d9055f387f7c991cfcbf50f48cf42d in ceph/s3-tests allows s3tests to propagate exceptions up to the calling task.
- Status changed from New to Resolved
Also available in: Atom
PDF