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
Since ElasticSearch was updated to version 7.10 in #4581 some tests are often failing, but sometimes succeed. I haven't been able to determine a pattern as to when the tests fail.
The tests in question are:
FilterServiceIT.shouldBuildQueryAndFindByProcessServiceByTaskTitle:174 Incorrect amount of processes for title containing 'Open'! expected:<1> but was:<0>
and
SearchResultFormIT.testFilterByTaskAndStatus:152 expected:<1> but was:<0>
The text was updated successfully, but these errors were encountered:
That seems to be a timing problem. So, from the fact that the index command has returned, it cannot yet be concluded that indexing has been completed. For a large number of search engine applications it is okay to work according to the fire-and-forget principle, but we need it differently for the tests. Perhaps there is a parameter for this that you can request that the request remain open until the indexing has been completed. Or we have to incorporate a general delay after indexing?
Since ElasticSearch was updated to version 7.10 in #4581 some tests are often failing, but sometimes succeed. I haven't been able to determine a pattern as to when the tests fail.
The tests in question are:
and
The text was updated successfully, but these errors were encountered: