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

Renamed to "flaky" test. #4912

Merged
merged 1 commit into from
Oct 26, 2022
Merged

Conversation

dblock
Copy link
Member

@dblock dblock commented Oct 25, 2022

Signed-off-by: Daniel (dB.) Doubrovkine dblock@amazon.com

Description

After a bit of googling, I believe the correct definition is "flaky". Will rename labels as well.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@dblock dblock requested review from a team and reta as code owners October 25, 2022 16:45
@dblock dblock force-pushed the flaky-tests branch 2 times, most recently from d593b12 to 1927e63 Compare October 25, 2022 16:47
@github-actions
Copy link
Contributor

Gradle Check (Jenkins) Run Completed with:

@github-actions
Copy link
Contributor

Gradle Check (Jenkins) Run Completed with:

@andrross
Copy link
Member

Ha! I did the same googling and came to the conclusion that "flakey" was an accepted, albeit less common spelling. I wanted to comment on your last PR but decided I wouldn't be an annoying pedant. The numbers don't lie though...

@github-actions
Copy link
Contributor

Gradle Check (Jenkins) Run Completed with:

@dblock
Copy link
Member Author

dblock commented Oct 25, 2022

REPRODUCE WITH: ./gradlew ':server:internalClusterTest' --tests "org.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT.testDecommissionStatusUpdatePublishedToAllNodes" -Dtests.seed=89E5053F9731D0F1 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=pt -Dtests.timezone=America/Recife -Druntime.java=17

org.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT > testDecommissionStatusUpdatePublishedToAllNodes FAILED
    java.lang.AssertionError: expected:<SUCCESSFUL> but was:<DRAINING>
        at __randomizedtesting.SeedInfo.seed([89E5053F9731D0F1:5708DEFD71320B65]: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.cluster.coordination.AwarenessAttributeDecommissionIT.testDecommissionStatusUpdatePublishedToAllNodes(AwarenessAttributeDecommissionIT.java:144)

#4824

@github-actions
Copy link
Contributor

Gradle Check (Jenkins) Run Completed with:

@github-actions
Copy link
Contributor

Gradle Check (Jenkins) Run Completed with:

Copy link
Member

@dreamer-89 dreamer-89 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dblock for the change.

How are you planning to change existing flakey label. I did not find option of renaming existing labels.
https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels

@dblock
Copy link
Member Author

dblock commented Oct 26, 2022

@dreamer-89 you can edit labels

Screen Shot 2022-10-26 at 8 23 51 AM

Signed-off-by: Daniel (dB.) Doubrovkine <dblock@amazon.com>
@github-actions
Copy link
Contributor

Gradle Check (Jenkins) Run Completed with:

@dblock dblock merged commit d96da50 into opensearch-project:main Oct 26, 2022
@dblock dblock deleted the flaky-tests branch October 26, 2022 13:14
@dblock dblock added the backport 2.x Backport to 2.x branch label Oct 26, 2022
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-4912-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d96da5026468eb3dabbd12d4763d40a52b980440
# Push it to GitHub
git push --set-upstream origin backport/backport-4912-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-4912-to-2.x.

dblock added a commit to dblock/OpenSearch that referenced this pull request Oct 26, 2022
Signed-off-by: Daniel (dB.) Doubrovkine <dblock@amazon.com>
dblock added a commit to dblock/OpenSearch that referenced this pull request Oct 26, 2022
Signed-off-by: Daniel (dB.) Doubrovkine <dblock@amazon.com>
dblock added a commit to dblock/OpenSearch that referenced this pull request Oct 26, 2022
Signed-off-by: Daniel (dB.) Doubrovkine <dblock@amazon.com>
dblock added a commit that referenced this pull request Oct 26, 2022
Signed-off-by: Daniel (dB.) Doubrovkine <dblock@amazon.com>

Signed-off-by: Daniel (dB.) Doubrovkine <dblock@amazon.com>
ashking94 pushed a commit to ashking94/OpenSearch that referenced this pull request Nov 7, 2022
Signed-off-by: Daniel (dB.) Doubrovkine <dblock@amazon.com>

Signed-off-by: Daniel (dB.) Doubrovkine <dblock@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.x Backport to 2.x branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants