Describe the bug
When using the median-run aggregation method I'd expect that assertions are done against the run, that has the property of isRepresentativeRun in the manifest.json. This does not appear to be the case.
@b3nk3 Sorry Ben.. It's unlikely we'll be able to dig into this anytime soon. Very happy to review PRs, though. Apologies we can't investigate ourselves.
Describe the bug When using the
median-run
aggregation method I'd expect that assertions are done against the run, that has the property ofisRepresentativeRun
in themanifest.json
. This does not appear to be the case.Manifest:
However, when correlating this with the
assertion-resutls.json
it is apparent, that a different run was used for assertion.To Reproduce Steps to reproduce the behavior: Use run LHCI with filesystem target, using the following assertion:
Expected behavior
Assertion should be done against the run with the
isRepresentativeRun
property in themanifest.json
As per the description of
median-run
in the Aggregation methods section of the config documentation:Environment (please complete the following information):
@lhci/cli@0.14.x