-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
KCIDB-ng is currently in a state where you can spin a test server up, create tokens, and submit samples that the server will accept (which might just accept any json blob at the moment).
According to https://github.com/kernelci/kcidb-ng/blob/ea9f4750d520afd34bdf149efed1e75eb06491aa/SUBMITTERS.md?plain=1#L20 , the 5_03 schema is currently planned for use in kcidb.
- Prepare your data: Ensure you have all the necessary information ready, including kernel configuration, build environment details, test results, and logs. You can see details about the required fields in the KCIDB-NG schema.
(this is still a moving target as kcidb-ng is still new and in development)
Examples of me submitting something:
> curl -X POST \
-H "Authorization: Bearer $BEARER_TOKEN" \
-H "Content-Type: application/json" \
-k -d @submission.json \
https://localhost:443/submit
{"id":"fJgX16iPkJ5jnbaJWf7tGki3TuNFqkb4","status":"ok","message":"Received submission fJgX16iPkJ5jnbaJWf7tGki3TuNFqkb4 with size 1732 bytes"}I'm thinking as a good step 1 to the overall epic of integrating with their new system, we could prepare example snippets that conform to their newer specs, and then begin development on a new script for creating the submission data from the metadata that GKCI gathers.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels