Bug #46257
closed
FAIL: s3tests_boto3.functional.test_s3select
Added by Casey Bodley almost 4 years ago.
Updated over 2 years ago.
Description
======================================================================
FAIL: s3tests_boto3.functional.test_s3select.test_csv_definition
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/ubuntu/cephtest/s3-tests/virtualenv/lib/python3.6/site-packages/nose/case.py", line 198, in runTest
self.test(*self.arg)
File "/home/ubuntu/cephtest/s3-tests/s3tests_boto3/functional/test_s3select.py", line 382, in test_csv_definition
nose.tools.assert_equal( number_of_rows, int(res))
AssertionError: 10000 != 10030
-------------------- >> begin captured logging << --------------------
logs: http://qa-proxy.ceph.com/teuthology/teuthology-2020-06-29_03:05:03-rgw-master-distro-basic-smithi/5187727/teuthology.log
- Assignee set to Gal Salomon
- the issue easily reproduce (single OSD/RGW , 2 clients)
- it seems to relate to spirit parser, should be check for its thread safety (not sure BOOST_SPIRIT_THREADSAFE is enougth).
- this issue by itself cause random failure
- Status changed from New to In Progress
- the syntax-parser is currently NOT thread-safe
- per parser-rule been accepted, a bind-function-object in which builds the AST (abstract syntax tree), is executed.
- that function-object responsible for using the correct s3select-request-context.
- each s3select-requests has different heap allocation per its AST.
- that heap-allocation(structure contains a s3select-context) is override by other s3select-request, resulting a failure.
- the test_s3select , should use unique names per objects. on parallel run it may cause failure.
- s3select-engine should maintain per-thread-context
- Subject changed from FAIL: s3tests_boto3.functional.test_s3select.test_csv_definition to FAIL: s3tests_boto3.functional.test_s3select
- Pull request ID set to 12
it looks like we'll need a ceph PR that updates the s3select submodule, and reenables the s3select testing
- Status changed from In Progress to Resolved
- Status changed from Resolved to In Progress
- Status changed from In Progress to Resolved
Also available in: Atom
PDF