tree 922986215a4426863350746d144a10e4a169f45b
parent e0a080d00ea013446fcd3579760d70236690ebe4
author Roman Lebedev <lebedev.ri@gmail.com> 1622646405 +0300
committer GitHub <noreply@github.com> 1622646405 +0300
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgt56FCRBK7hj4Ov3rIwAA7lEIAH53wIYSazksXT7rrWiIUdtz
 3EEP1JjSpP2x+/HitZHjIJdNLsZc+Fk4YMQXy34ugYjP75dMUeNtAik/shQxtIQR
 0ZZb+jWfw85d+yBFRpWlJDScdGCFrV/vXcknnEXEYh02XrCXxZ5tiTlmN3uupvMg
 /jhtVVTr4ncw1mF7OfiVvIHPWgkChWZvWSeO2DDajjuvhN6E7rjYes7nFBlQ0o6x
 dbDgM1LS5cMDZ3Z02DWRwMAM20MsXrxqD4YssQk21JWq+CcAdgYfUY5jGpR3j8pG
 vshy7hsdf0s6kEfwYnZdEU4/swgVC6mFaZTOht9nRy0ofLEloYFbz6ppEH901ds=
 =0Lsz
 -----END PGP SIGNATURE-----
 

Introduce "family index" field into JSON output (#1164)

It may be useful for those wishing to further post-process JSON results,
but it is mainly geared towards better support for run interleaving,
where results from the same family may not be close-by in the JSON.

While we won't be able to do much about that for outputs,
the tools can and perhaps should reorder the results to that
at least in their output they are in proper order, not run order.

Note that this only counts the families that were filtered-in,
so if e.g. there were three families, and we filtered-out
the second one, the two families (which were first and third)
will have family indexes 0 and 1.