Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport 2.11] Don't attempt to parse workflow if it doesn't exist #1362

Merged
merged 1 commit into from
Feb 5, 2024

Conversation

opensearch-trigger-bot[bot]
Copy link
Contributor

Backport 733fd4e from #1346.

Signed-off-by: Chase Engelbrecht <[email protected]>
(cherry picked from commit 733fd4e)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@engechas
Copy link
Collaborator

Multinode are failing with known flaky test discussed in #1363

org.opensearch.alerting.resthandler.WorkflowRestApiIT > test chained alerts and audit alerts for workflows with query level monitor FAILED
    java.lang.AssertionError: expected:<0> but was:<2>
        at __randomizedtesting.SeedInfo.seed([841910152E9FE0B:6043A8CD140A6FC]:0)
        at org.junit.Assert.fail(Assert.java:89)
        at org.junit.Assert.failNotEquals(Assert.java:835)
        at org.junit.Assert.assertEquals(Assert.java:120)
        at org.junit.Assert.assertEquals(Assert.java:146)
        at org.opensearch.alerting.resthandler.WorkflowRestApiIT.test chained alerts and audit alerts for workflows with query level monitor(WorkflowRestApiIT.kt:1126)
REPRODUCE WITH: ./gradlew ':alerting:integTest' --tests "org.opensearch.alerting.resthandler.WorkflowRestApiIT.test chained alerts and audit alerts for workflows with query level monitor" -Dtests.seed=841910152E9FE0B -Dtests.security.manager=false -Dtests.locale=id-ID -Dtests.timezone=SystemV/EST5 -Druntime.java=11

@AWSHurneyt AWSHurneyt merged commit 6172632 into 2.11 Feb 5, 2024
22 of 26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants