[
https://issues.apache.org/jira/browse/UNOMI-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136003#comment-18136003
]
Serge Huber commented on UNOMI-1027:
------------------------------------
Pull request: https://github.com/apache/unomi/pull/939
Related diagnosis also in UNOMI-959 (match-none from a null condition type).
> GraphQLListIT.testCRUD intermittently fails waiting for a profile in a list
> ---------------------------------------------------------------------------
>
> Key: UNOMI-1027
> URL: https://issues.apache.org/jira/browse/UNOMI-1027
> Project: Apache Unomi
> Issue Type: Test
> Affects Versions: unomi-4.0.0
> Reporter: Serge Huber
> Priority: Major
> Fix For: unomi-4.0.0
>
>
> h3. In short
> A GraphQL integration test fails at random on both search engines, which
> blocks unrelated changes until CI is re-run.
> h3. Details
> * {{GraphQLListIT.testCRUD}} fails at "Failed waiting for profile in list
> query" after {{addProfileToList}} (seen on PR 843 and PR 928, both unrelated;
> passes on re-run).
> * The test already refreshes the indices on every polling attempt, so a stale
> refresh is not the cause; the list membership is sometimes not visible to
> {{findLists}} at all within the wait.
> h3. Fix and test
> Find why the profile's list membership is not visible (asynchronous save, or
> a different index or tenant), fix it in the code or the test, and confirm
> with repeated runs on both engines.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
