Various PLANS & TORVVCP updates
See merge request eng/das/cov/gnatcoverage-qualification!45
This MR updates the PLANS and TORVVCP documents in various ways:
* Relax restrictions on the allowed values for `--dump-trigger` and `--dump-channel` ;
* Allow use of `--insturment-block` in the `instrument` command, provided that no exceptions are handled and no exceptions occur at runtime;
* Remove erroneous description of the tool operating principle, and corresponding reference documents. These were leftovers from the binary traces qualification kit;
(cherry picked from commit 9a1878fdd2d5af73ee3c6691f7e86e36286c7ed0)
Address QA comments
See merge request eng/das/cov/gnatcoverage-qualification!40
This MR contains multiple commits addressing various comments raised during the first round of QA on the generated kit.
(cherry picked from commit 93fff75cecddb504ec2a1ce1dab3848e50ea7c4c)
Various qualkit updates
See merge request eng/das/cov/gnatcoverage-qualification!36
The modifications include:
* TOR: Refinements over the expected execution environment
* TOR: remove index entry definitions
* PLANS: Remove duplicate revision history section
(cherry picked from commit 772afba72ae4014b866562d04b6f3fd8c5f8d5dd)
genbundle.py: Defer settings loading until after work dir has been setup
See merge request eng/das/cov/gnatcoverage-qualification!35
(cherry picked from commit 6b7a34d411eadf998cdcabcac0da8bd1baaa1e49)
Qualkit: Add document id in the filename for each of the documents
See merge request eng/das/cov/gnatcoverage-qualification!33
(cherry picked from commit 337879aca842aa309033986bf51366b63546f997)
This involves moving large chuncks of the sources to more deeply nested directories, as there
are some assumptions as to where some config files are located.
When working on a qualrun result that was produced in a Windows
environment, then zipped and unpacked in a linux environment, all
executable permissions are removed. To work around this, invoke
mkrest.sh through a sh invocation.
Part of W426-013 (gnatcov qualkit 999-W426-013)
At the same spot where we currently have doc identifiers, so we
think of updating them at the same time.
Stick intended values for the current project there. Later on, we'll
want these instantiated from the environment but that's a more involved
change, not for the current cycle.
