Clarify version usage in test tool exclusion docs (#10858)

CHANGELOG_BEGIN
CHANGELOG_END
This commit is contained in:
Hubert Slojewski 2021-09-13 13:30:00 +02:00 committed by GitHub
parent c113954a35
commit d9178d2ac2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -14,8 +14,11 @@ load("//:versions.bzl", "latest_stable_version")
# is again described by `start` and `end` as well as the actual list of --exclude flags that
# should be passed to the ledger API test tool.
# Start and end are always inclusive and can be omitted if you only need an upper or lower bound.
# Usually, you'll want to set the latest release from the `LATEST` file to one of the boundaries
# and use the next version in another one. For example, `1.17.0-snapshot.20210910.7786.0.976ca400`
# could be the end, while `1.17.0-snapshot.20210910.7786.1` would be the next version.
# Note that 0.0.0, i.e., current HEAD is considered to come after all other versions.
# Note that before 1.3 the granularity for disabling tests
# Also, note that before 1.3 the granularity for disabling tests
# was sadly quite coarse. See
# https://discuss.daml.com/t/can-i-disable-individual-tests-in-the-ledger-api-test-tool/226
# for details.