Draft: Test for peak memory usage in new historgrams test
1 unresolved thread
1 unresolved thread
See #279 (closed)
Merge request reports
Activity
mentioned in issue #279 (closed)
This should be rebased on !1505 (merged) as that fixes the memory usage problem.
Apart from the modified test, there are two other tests that are failing because they use the same algorithm and now are getting unexpected stdout.
Edited by Marco Clemencic
changed milestone to %v38r0
changed milestone to %v38r1
changed milestone to %v38r2
removed milestone %v38r2
Please register or sign in to reply