Re: KCIDB: Support non-binary test outputs

On Mon, Aug 05, 2024 at 02:28:24PM +0300, Nikolai Kondrashov wrote:

> Here is the (abbreviated) schema for the new field:

>     "value": {
>         "type": "object",
>         "properties": {
>             "integer": {"type": "integer"},
>             "number": {"type": "number"},
>             "string": {"type": "string"},
>             "boolean": {"type": "boolean"},
>         },
>         "minProperties": 1,
>         "additionalProperties": False
>     },

> The meaning of the value itself depends on the particular test, that is the
> "path" field value. Each property inside the value corresponds to a data type.

Might it be useful to directly specify units for use with "number" to
help with normalising data between different CI systems or hardware -
for example with boot times both seconds and miliseconds seem like
reasonable units to use?  It might also be useful for UIs, though we
could also do that with a separate table for the tests that they can
query.  Perhaps I'm just worrying too much about specialist cases where
it's likely that CI systems won't just be picking up an off the shelf
suite that has standard units.

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmawxo8ACgkQJNaLcl1U
h9Da4Qf8CRPTeq88Q3MFdGXr1LaUxD0exje6U9HA3UOFB+CRtSfxn0yk0zDw5HQu
25JnCUl6ZhZ83nHOSfZ82amz1UI5PBer4iXUcXXzU+88W9V1ul9eel6F30J9HCNC
VduzUSYkMobBxKLPnqFrSu0ux3fIZeJ0fBdmKiMfaUAjdnn4jWdfrnWsKpdZ1sLi
K199JutioCb0YtPGTKe7wE6OXPk7rCXzf9Yc7kBGlmMSrh7EW1ZRaemN5o87VXe5
DCcW+I2ToVPtMwzRi4d58cXvG/mTKWk5nHo4wc2ZF1/LA6amTwn7PXedUzWcZvu8
RCv47Np3fe7QAbiRsoErXCgccMlnWw==
=JZpm
-----END PGP SIGNATURE-----