Describe the new feature:
We have found it incredibly useful to have the results CSV file when running bisect in --auto-sqlite-run mode. Why not generate these CSV files when running individual bisect runs?
Suggested change:
Within each bisect directory, create a results.csv file (e.g., bisect-01/results.csv). Give it the same structure as the CSV file generated from --auto-sqlite-run mode.
Alternative approaches:
In the top-level, have a bisect-results.csv file created from any bisect run, including the --auto-sqlite-run mode. For any further bisect runs, append to this file.
Create an SQLite file instead of a CSV. This may be more natural anyway since the structure of the CSV file is trying to mimic how you would manage with multiple tables. However, it will require more SQL ability from users. This could be created on a per-bisect case, or one top-level one that gets appended with each bisect run.
Modify flit mport to import the CSV results (from the suggested change or alternative approach 1) to import the bisect results into the FLiT results SQLite file, so we have both the CSV and the database.
Feature Request
Describe the new feature: We have found it incredibly useful to have the results CSV file when running bisect in
--auto-sqlite-runmode. Why not generate these CSV files when running individual bisect runs?Suggested change: Within each bisect directory, create a
results.csvfile (e.g.,bisect-01/results.csv). Give it the same structure as the CSV file generated from--auto-sqlite-runmode.Alternative approaches:
bisect-results.csvfile created from any bisect run, including the--auto-sqlite-runmode. For any further bisect runs, append to this file.flit mportto import the CSV results (from the suggested change or alternative approach 1) to import the bisect results into the FLiT results SQLite file, so we have both the CSV and the database.