Repository navigation
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…-timestamp AIENG-379: emit per-suite start timestamp for robot runner
…-suite-timestamp-main # Conflicts: # smart_tests/test_runners/robot.py
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Forward-port of #1418 (v1) to main.
Why
The robot runner's elapsed/parallelization numbers can't be computed because robot test cases land with no real start time — they fall back to ingest time (all cases in a run cluster within a few milliseconds). Root cause is in this plugin: Robot's
output.xmlrecords a per-suitestarttime, butparse_funcread it only to derive each case's duration and then discarded it, emitting a single flat<testsuite name="robot">with notimestamp. Downstream, the suite timestamp is what the server resolves and stamps onto every case in the suite, so with none emitted, robot timing was lost.What changed
<testsuite>per leaf suite, each tagged with its own starttimestamp, instead of one flatrobotsuite — so each case inherits its real suite start.starttime(20210319 11:34:50.085) is reshaped viastrptime(...).isoformat(); RF 7.0+'s already-ISOstartpasses through untouched. Timezone resolution stays server-side.None(server falls back as before) rather than failing the upload.classname, not the suite element), so existing record/subset goldens still match. Added aparse_functest asserting per-suite timestamps.