Details
-
Bug
-
Resolution: Fixed
-
P3: Somewhat important
-
6.6
-
None
-
5
-
95f02adf7 (dev), 7ab145a9e (6.9), f54b4793e (6.8), 466d79319 (tqtc/lts-6.5)
-
Foundation Sprint 121, Foundation Sprint 122
Description
When combining a global data driven test (cf. initTestCase_data / QFETCH_GLOBAL) with a data driven test (myBenchmark / QFETCH) and QBENCHMARK: the BenchmarkResult is not distinguishable between the different global data driven tags: only the local data tag is included:
... <!-- Firstglobal:FirstLocal --> <BenchmarkResult metric="WalltimeMilliseconds" tag="FirstLocal" value="100" iterations="1"/> ... <!-- Firstglobal:SecondLocal --> <BenchmarkResult metric="WalltimeMilliseconds" tag="SecondLocal" value="101" iterations="1"/> ... <!-- SecondGlobal:FirstLocal --> <BenchmarkResult metric="WalltimeMilliseconds" tag="FirstLocal" value="112" iterations="1"/> ... <!-- Firstglobal:SecondLocal --> <BenchmarkResult metric="WalltimeMilliseconds" tag="SecondLocal" value="111" iterations="1"/>
See attached the resulting XML.
This leads to QtCreator to categorise the benchmark results in the wrong test (see screenshot).
One way to solve this is to use the same globalTag:localTag in the BenchmarkResult, similar to how the Incident/DataTag does it.
Attachments
For Gerrit Dashboard: QTBUG-127522 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
611118,4 | Output both global and local data tags in benchmark result header | dev | qt/qtbase | Status: MERGED | +2 | 0 |
611637,2 | Output both global and local data tags in benchmark result header | 6.9 | qt/qtbase | Status: MERGED | +2 | 0 |
611680,2 | Output both global and local data tags in benchmark result header | 6.8 | qt/qtbase | Status: MERGED | +2 | 0 |
611752,2 | Output both global and local data tags in benchmark result header | tqtc/lts-6.5 | qt/tqtc-qtbase | Status: MERGED | +2 | 0 |