util: genElapsedTime parses the timing line wherever it sits on the line

[oharboe]

What

genElapsedTime.py writes the per-stage summary row: elapsed time, peak memory and the sha1sum of the stage's results, the one place ORFS reports a hash of a stage's result. It parsed the timing line positionally, so a timing line with any prefix is "not understood" and the whole row is dropped silently: no "No elapsed time found" warning (the line was found), exit status 0. A RUN_CMD wrapper that stamps log lines ([ 123.45] Elapsed time: ...) is enough to trigger it.

Fix

Match the timing line with a regex anchored on its format, hours optional as run_command.py only emits them past an hour. An unprefixed line gives exactly the number it did before (fraction of a second dropped as before), and an unparseable line still reaches "Elapsed time not understood".

Test

flow/test/test_run_command.py:

• test_genElapsedTime_parses_output asserted only that the stage name appeared, which it does even when the row is dropped; it now asserts the elapsed and memory columns.
• New: a prefixed timing line (fails before this change) and the hours form.

flow/test/*.py all pass; black clean.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request refactors the elapsed time parsing logic in genElapsedTime.py to use a regular expression, allowing it to robustly parse timing lines that contain prefixes or optional hour fields. Additionally, corresponding unit tests have been added in test_run_command.py to verify these parsing capabilities. There are no review comments, and I have no feedback to provide.

[openroad-ci]

🔍 QoR check

Metrics reflect the PR merge build — i.e. what will land on the target branch.

Commit ae12237 · Jenkins build #3 · Baseline: build · View build on dashboard

62 design(s) checked — 0 with regression(s), 0 without a comparable baseline.