Victor Martinez

I'll give a go tomorrow morning and let you know the outcome. Thanks rcarz

``` java issue.update().field(Field.ASSIGNEE, Field.valueByName("robin")).execute(); ``` Same error, I'm afraid: ``` 400 Bad Request: {"errorMessages":[],"errors":{"assignee":"data was not an object"}} ``` Let me know if you need further details. Thanks again

Atlassian JIRA Project Management Software Version: (v6.3.14#6345-sha1:47b2bb0)

https://github.com/elastic/apm-pipeline-library/pull/754 provides a higher overview of the aim of this particular flaky reporting in GitHub on a PR basis. Regarding how flaky tests are identified, that's documented in an internal...

> I wonder if it is possible to test these changes on a fork of this repo before pushing them into the main branch on the primary? I tested it...

I already enabled a similar set of actions in `elastic/beats.git` and https://github.com/elastic/beats/pull/32267 and it's the one that contains the example with the traces (github action + test results)

> Where are these traces going to end up? Is it in an internal cluster? Yes, that's one of the cluster we have been using for quite sometime, for tracking...

jenkins run the tests please

> @v1v Do any changes in the above time frame ring a bell for you? I wonder if a recent docker upgrade has happened in the CI workers, I recall...

> Our "TAV Test" stage is the longest. It typically and reliably has been taking slightly over 1h to complete. However, starting some time after Mar 23rd, that time started...