opened
v1v
username_0
```

{
age: 1,
duration: 0,
errorDetails: "Failed",
errorStackTrace: " client_integration_test.go:58: for testing the flaky test reporting for an existing flaky test",
id: "io.jenkins.blueocean.service.embedded.rest.junit.BlueJUnitTestResult:elasticsearch%3Ajunit%2F(root)%2Felasticsearch%2FBuild_Test___libbeat_build___TestClientPublishEventKerberosAware",
name: "Build&Test / libbeat-build / TestClientPublishEventKerberosAware â€“ elasticsearch",
status: "FAILED"
}

```

![image](https://user-images.githubusercontent.com/2871786/96929154-a0888300-14b1-11eb-9a2d-de1edd26994c.png)

![image](https://user-images.githubusercontent.com/2871786/96929196-aed69f00-14b1-11eb-9ef6-e1de219199da.png)
[flaky] normalisation in the flaky does not happen with the tests-errors.json
issue
created
v1v
username_0
It seems the issue is not related to the encoding since it was something in my browser, but worked like a charm in the CLI:

![image](https://user-images.githubusercontent.com/2871786/97028119-95862f00-1553-11eb-85d0-db7253aaaa7d.png)



It seems the issue is related with the number of reported flaky tests, since it reports only the ones from August 2020 while there already some others

![image](https://user-images.githubusercontent.com/2871786/97028025-75567000-1553-11eb-933d-357ce9dd856e.png)
comment
created
v1v
username_0
![image](https://user-images.githubusercontent.com/2871786/97155920-ea04f680-176d-11eb-8d3b-c13bd28a827d.png)

```
GET /reporter-beats-beats-master/_search?size=1000
{
  "timeout": "2s",
  "sort" : [
    { "timestamp" : "desc" },
    { "test_score" : "desc" }
  ],
  "query" : {
    "range" : {
      "test_score" : {
        "gt" : 0.0
      }
    }
  }
}
```
comment
closed
v1v
username_0
issue