Sebastien Ponce authored 1 year ago and Marco Clemencic committed 1 year ago

More precisely, json data come from the JSONSink and this produces a list of non ordered items, one may call it a set.
Unfortunately JSON does not have such a concept so an ordered list is produced and the validator was naturally checking that the order was correct

See merge request !1499

The Doxygen ZIP files are still deployed for tags.

See merge request !1482

Sebastien Ponce authored 1 year ago and Marco Clemencic committed 1 year ago

The problem was due to the use of deque, extremely slow for deleting when getting big.
The code was written that way supposing we would get ~100 entities (aka some human readable quantity), but we seem to reach > 100000...
So deque has been replaced by a map with entity's memory address as a key, and now the deletion is fast

Note: this is an old and backward compatible version of !1477

See merge request !1469

Closes #262

See merge request !1467

See merge request !1466

See merge request !1465

See merge request !1464

See merge request !1461

See merge request !1460

See merge request !1462

If `QMTEST_DISABLE_FIXTURES_REQUIRED` is truthy, a failing prerequisite
test will not cause the test depending on it to be skipped.

Workaround for #216

the additions of decltype checks in Gaudi::Property are needed to avoid
that fmtlib confuses Gaudi::Property for a range.

And added a test checking new behavior.
Basically integer arithmetic was broken as the index computation was optimized by precomputing the bin width. This lead to 0 bin width when < 1. Now fixed.

Essentially to be able to inspect the configuration of histograms, e.g. nb bins, min/max value, etc
These methods were so far protected for unknown reasons

See merge request !1459

See merge request !1456

Closes #266

See merge request !1455

See merge request !1457

See merge request !1452

See merge request !1454