Re: KCIDB: Support non-binary test outputs

On 8/8/24 10:47 PM, Mark Brown wrote:
> On Thu, Aug 08, 2024 at 09:05:20PM +0300, Nikolai Kondrashov wrote:
>> On 8/6/24 10:20 PM, Mark Brown wrote:
> 
>>> TBH as a submitter getting specific stuff back immediately (or at least
>>> the option for it) is really helpful.
> 
>> Do you mean that you would like to know if you submitted something wrong
>> immediately?
> 
>> Could you elaborate a bit here?
> 
> The whole workflow where you push data in and then check to see if it
> appeared in the dashboard can be a bit obscure if you're trying to get
> things right.

Makes sense. How would you prefer it to work? Throw an exception with details
of the problem when submitting using the Python API, and abort the
kcidb-submit with an error message when using command-line tools?

Do you validate your data before sending? We can add something on top of the
schema there.

I think there would always be "soft failures" of one nature or another, that
shouldn't prevent the data getting in, but would warrant eventual resolution.
Would you like to receive them as e.g. a daily digest, via email?

>>> Putting the exponent in as a number does seem like it'd be much more
>>> helpful for machine processing.
> 
>> It's helpful for normalizing to a single exponent, so data can be compared,
>> but that's not something that a database can do fast. So, not helpful in the
>> end.
> 
> It might be helpful on the read side though (ie, doing it as part of
> rendering rather than in the database itself)?  Not so good for queries
> but useful for UIs.

OK, I'll send a new version of the schema with units and exponent added, and
we'll just see how it goes.

Thanks for all the comments!
Nick