fixes for WFLY-1318 and WFLY-1329 #4515
Conversation
|
Triggering build using a merge of a748a23 on branch master: |
|
Build 7112 is now running using a merge of a748a23 on branch master: |
|
Build 7112 outcome was FAILURE using a merge of a748a23 on branch master: |
|
That's an odd failure. |
|
yeah, it's odd - however seems unrelated, more like an environment issues!? I don't see that in my local test runs so maybe we should retest this first and see if it's an intermittent failure. |
|
retest this please. |
|
Triggering build using a merge of a748a23 on branch master: |
|
Build 7112 outcome was FAILURE using a merge of a748a23 on branch master: |
|
retest this please. |
|
Triggering build using a merge of a748a23 on branch master: |
|
Build 7121 outcome was SUCCESS using a merge of a748a23 on branch master: |
|
Not sure how PRs are getting tested atm, but i doubt it can be tested within 5 minutes. The first 2 failures point to the same run and the last one finished within 5 minutes from getting the notifications. Looks like there is something wrong with that? |
|
The builds do match up to this PR. I think the build must have already been executed for some reason. Perhaps it was sent in twice |
|
The outcome notifications seem off though. The 2nd time it was just reposting the link to the first run. The 3rd notification looks like the outcome for the 2nd run. Most likely there is another run which just finished or is about to finish. |
|
I have a theory that what is happening is that the jenkins API is returning that a particular build has completed, while the outter API still shows it in progress |
|
Merged. |
https://issues.jboss.org/browse/WFLY-1318 executing a :reload using the http interface fails
https://issues.jboss.org/browse/WFLY-1329 'whoami' operation unexpectedly requires the domain wide configuration lock