Gilles Peskine 082eadef4e Separate code and data of outcome analysis
Place the code of outcome analysis (auxiliary functions, tasks, command line
entry point) into a separate module, which will be moved to the
version-independent framework repository so that it can be shared between
maintained branches. Keep the branch-specific list of driver components and
ignore lists in the per-repository script.

We keep the executable script at `tests/scripts/analyze_outcomes.py`. It's
simpler that way, because that path is hard-coded in CI scripts.

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2024-10-03 18:42:37 +02:00
..
2024-03-12 13:33:09 +00:00
2023-11-02 19:47:20 +00:00
2024-07-10 08:10:40 +02:00
2023-11-02 19:47:20 +00:00
2024-07-25 11:00:07 +02:00
2023-11-02 19:47:20 +00:00
2023-11-02 19:47:20 +00:00
2023-11-02 19:47:20 +00:00
2023-11-02 19:47:20 +00:00
2023-11-02 19:47:20 +00:00
2023-11-02 19:47:20 +00:00
2023-11-09 10:10:33 +08:00
2023-11-02 19:47:20 +00:00
2023-11-02 19:47:20 +00:00
2023-11-02 19:47:20 +00:00
2023-07-25 19:40:35 +02:00
2023-11-15 16:56:26 +01:00
2024-09-11 16:07:09 +02:00
2023-11-02 19:47:20 +00:00
2023-11-02 19:47:20 +00:00
2023-11-02 19:47:20 +00:00
2023-11-02 19:47:20 +00:00
2023-11-02 19:47:20 +00:00
2023-11-02 19:47:20 +00:00