Commit 71b38d5
committed
fix: Parse timing markers from console output for JavaScript benchmarking
The _parse_timing_from_jest_output() function was defined but never called,
causing benchmarking tests to report runtime=0. This integrates console timing
marker parsing into parse_test_results() to extract accurate performance data
from capturePerf() calls.
Fixes the "summed benchmark runtime of the original function is 0" error
when timing data exists in console output but JUnit XML reports 0.1 parent 017bde1 commit 71b38d5
1 file changed
Lines changed: 27 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1533 | 1533 | | |
1534 | 1534 | | |
1535 | 1535 | | |
| 1536 | + | |
| 1537 | + | |
| 1538 | + | |
| 1539 | + | |
| 1540 | + | |
1536 | 1541 | | |
1537 | 1542 | | |
1538 | 1543 | | |
| |||
1542 | 1547 | | |
1543 | 1548 | | |
1544 | 1549 | | |
1545 | | - | |
| 1550 | + | |
1546 | 1551 | | |
1547 | | - | |
| 1552 | + | |
1548 | 1553 | | |
1549 | | - | |
| 1554 | + | |
| 1555 | + | |
| 1556 | + | |
| 1557 | + | |
| 1558 | + | |
| 1559 | + | |
| 1560 | + | |
| 1561 | + | |
| 1562 | + | |
| 1563 | + | |
| 1564 | + | |
| 1565 | + | |
| 1566 | + | |
| 1567 | + | |
| 1568 | + | |
| 1569 | + | |
| 1570 | + | |
| 1571 | + | |
| 1572 | + | |
| 1573 | + | |
1550 | 1574 | | |
1551 | 1575 | | |
1552 | 1576 | | |
| |||
0 commit comments