-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
[test failure] :x-pack:plugin:watcher:test can fail with java.lang.IllegalArgumentException: Both text and attachments cannot be null. #31948
Comments
Pinging @elastic/es-core-infra |
I've muted the test in dadf96a |
on it. I already backported the other test this morning tho before seeing this. Should i push a mute to that test too? |
A new commit was merged that does not allow a null attachement && text. This is valid for the slack API, as it does not allow this, but our unit tests did. This commit fixes the broken unit test. Closes elastic#31948
I have a fix for this in #31968 |
A new commit was merged that does not allow a null attachement && text. This is valid for the slack API, as it does not allow this, but our unit tests did. This commit fixes the broken unit test. Closes #31948
A new commit was merged that does not allow a null attachement && text. This is valid for the slack API, as it does not allow this, but our unit tests did. This commit fixes the broken unit test. Closes #31948
@hub-cap This error is still occuring: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+multijob-unix-compatibility/os=sles/1176/ First I thought the last good commit was not up to date, but it seems to use a commit after you pushed the fix.
|
+1 this is still failing for me locally with
|
This still fails reproducibly on master: REPRODUCE WITH:
|
Also muted 6.x with where the same reproduction worked with fb6cce0 |
Thanks, ill verify. I thought there could be some funkyness with this change and the random behavior. Ill get on it, sorry for the noise. |
There was still a case with a null text that allowed for 0 attachments to be created. This commit ensures that greater than zero are created if the text is null. Otherwise, it uses the same logic to create 0 to 3 random attachments. Closes #31948
fixed and backported and tested with |
I ran into this on an unrelated PR on the
master
branch, and can reliably reproduce.Reproduce:
Recent relevant change: 8ec33b7#diff-b5bf09a9e8e2ab5019c940fe22bd8b25R34
Full text:
cc: @hub-cap
The text was updated successfully, but these errors were encountered: