You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make index_name thread save to support parallel-test feature from rails
It looks like setting the index_name per test can lead to cross pollination of the index_name, leading to situation where
the index changes during test, because another elasticsearch test just started.
Are we sure, current implementation even can (and want) support highly concurrent test scenarios with different indexes?
Can you thin of another way of speedin gup tests?
I checked #342 but don't think naming will solve everything
The text was updated successfully, but these errors were encountered:
parallelize_setupdo |worker|
Chewy.settings[:prefix]="chewy-test-parallel-#{worker}"SearchIndex.purge!endteardowndo# Loop until the document count is zeroloopdoSearchIndex.purgesleep1# Sleep for 1 second before checking againdocument_count=SearchIndex.client.count(index: SearchIndex.index_name)['count']puts"Waiting for deletion... Current document count: #{document_count}"breakifdocument_count == 0rescueElasticsearch::Transport::Transport::Errors::ServiceUnavailableputs'Waiting for sever available'sleep3endend
Make index_name thread save to support parallel-test feature from rails
It looks like setting the index_name per test can lead to cross pollination of the index_name, leading to situation where
the index changes during test, because another elasticsearch test just started.
I checked #342 but don't think naming will solve everything
The text was updated successfully, but these errors were encountered: