diff options
| author |   pmikus <peter.mikus@protonmail.ch> | 2022-11-24 13:27:53 +0000 |
|---|---|---|
| committer | Peter Mikus <peter.mikus@protonmail.ch> | 2022-12-06 07:03:47 +0000 |
| commit | bfbdfaedb044b7643b81f47e76285baedfee9e25 (patch) | |
| tree | 2b37abee55771074daea09a7f3f973352cc2ce48 /docs/model/current/top.rst | |
| parent | c0cbaf897aa00152c4ce21987b6eb2ec371be6b0 (diff) | |
feat(model): Cleanup and introduce telemetry
- Due to divergence from original design path the RAW was never
consumed. It adds too much code complexity and requires processing
on both storage and compute. Removing entirely to make modeling
efficient.
- log (apparently SSH) section will never be consumed in the way it is
coded in model. This section is also not part of model schema itself
due to the point above.
- Introducing telemetry section that is going to carry telemetry
items required for CDash.
Signed-off-by: pmikus <peter.mikus@protonmail.ch>
Change-Id: I7e0256c6c9715de8ee559eed29dce96329aac97d
Diffstat (limited to 'docs/model/current/top.rst')
| -rw-r--r-- | docs/model/current/top.rst | 12 |
1 files changed, 2 insertions, 10 deletions
diff --git a/docs/model/current/top.rst b/docs/model/current/top.rst index ee33a29cd3..e824225698 100644 --- a/docs/model/current/top.rst +++ b/docs/model/current/top.rst @@ -22,7 +22,7 @@ especially the export side (UTI), not import side (PAL). Version ~~~~~~~ -This document is valid for CSIT model version 1.0.1. +This document is valid for CSIT model version 1.1.0. It is recommended to use semantic versioning: https://semver.org/ That means, if the new model misses a field present in the old model, @@ -54,15 +54,7 @@ If the suite name contains spaces (Robot converts underscores to spaces), they are replaced with underscores. The filesystem tree is rooted under tests/ (as suites in git are there), -and for each component (test case, suite setup, suite teardown) -two files are generated. -The "raw" variant is suitable for debugging (can contain lower level logging), -while the "info" variant is suitable for processing by PAL -(can contain derivative values so PAL does not need to compute them -on every download). -Their structure and content is mostly identical, model definition mentions -if a particular subschema is not identical in the two variants. -It is possible to convert from raw to info, but not the other way. +and for each component (test case, suite setup, suite teardown). Although we expect only ASCII text in the exported files, we manipulate files using UTF-8 encoding, |