Final output file is showing wrong start_time, end_time and elapsed.

[joseajunior]

The image below shows the information from the final output using the ExecutionResult.
You can notice that the start time, end time, and elapsed look exactly like the one for the first lowest suite.

And in red we can see suites where the end time is longer than the one from the root suite.
Also, this "Statistics elapsed" at the bottom is the value from here in seconds:

This is using versions:
pabot: 2.17.0
robotframework: 7.0

[mkorpela]

Thank you for reporting this detailed timing issue. From the timing data and screenshots you've shared, this appears to be related to how Robot Framework 7.0 handles suite timing calculations rather than an issue in Pabot's result merging.

Here's why:

1. Looking at your ExecutionResult output, the parent suite's endtime is earlier than some child suites' endtimes, which shouldn't be possible in a properly constructed test execution result
2. The timing inconsistency exists in the original output.xml before Pabot's result merging process
3. Pabot's result merger actually tries to handle timing correctly by taking:
   • The earliest starttime across merged suites
   • The latest endtime across merged suites

I recommend:

1. Could you re-open an issue in the Robot Framework repository with your timing data - or ensure that it is fixed?
2. For debugging, it would be helpful to get the original output.xml files before merging (from pabot_results)
3. In the meantime, you could try running the same tests with Robot Framework 7.1.1 to see if the timing calculations have been fixed in the newer version

[joseajunior]

robot-logs.zip
Here are some latest logs that are still showing the values wrong.