Could you please clarify the issue? Which exact numbers were not as expected? Did you get output.xml directly from execution or have you used the Rebot tool to merge, combine or otherwise modify it?

From what I imagine, the start_time, end_time, and elapsed time from the root suite should be the same as the one on the report.html, right?

The report was created using Pabot.

Can you show where the values in output.xml and report.html differ? Notice that your original example only shows start/end times.

Notice that All Tests in log and report statistics only contain information about tests. In that elapsed time the time taken by possible suite setup and teardown is not visible. To see the actual elapsed time of a suite, you need to look at suite information.

Pabot uses the Rebot tool internally to combine results of the individual suites (or tests) that have been executed parallel. How exactly it uses Rebot may affect the results. If you suspect there's a bug in Robot, you need to be able to demonstrate it without Pabot. If you suspect there's a bug in Pabot, you need to submit an issue to its issue tracker.

Okay, so I ran the same tests just with Robot, and the elapsed time from result.suite.elapsed_time was 0:17:18.786542 while the one from the log.html was 00:16:44.

With that, I believe the issue (if there is one) is on Pabot.
But now I have some questions:

1. This ~26 seconds difference is okay because it doesn't track the setups and teardowns, right?
2. How can I get the All Tests elapsed time?
3. For my DbBot/Grafana dashboard, how can I get an accurate start_time, end_time, and elapsed_time using the ExecutionResult ?

What time in the log file is that 00:16:44? If result.suite.elapsed_time is 0:17:18.786542, the elapsed time of the top level suite in the log file should be exactly that rounded to milliseconds. As I already mentioned, All Tests time doesn't contain suite setups and teardowns and is thus typically different.

If there isn't a bug somewhere, it would be better to start a discussion about this on our Slack or Forum. This issue tracker is for bug reports and concrete enhancement requests.

I am closing this here and moving to pabot.

Reopening this issue according to comment in mkorpela/pabot#596

Could you please clarify what the problem is? Please also see my earlier comment.

Quoting @mkorpela in the pabot issue: "the parent suite's endtime is earlier than some child suites' endtimes, which shouldn't be possible in a properly constructed test execution result"
This is causing that the root Suite has a endtime and elapsed time lower than some of their child suites.
I added a zip file there with some more recent reports.

Hope I answered you question Pekka.

No, that doesn't answer my question. I understand your quote, but you need to provide concrete example of such a problem. A concrete example demonstrating the problem would be helpful, but it needs to be as simple as possible.

No new information so closing. Can be reopened if there's an example demonstrating the issue.