test(per table hints): Added a test for per table hints

[Lakshmipathi]

Test per table hints expected_data_size_in_gb option with GrowShrinkNemesis

Testing

• [x ] https://argus.scylladb.com/tests/scylla-cluster-tests/73d82c0b-0591-4497-8f5f-a6ca7a88347c (after disabling oversized_allocation error)

PR pre-checks (self review)

• [x ] I added the relevant backport labels
• [ x] I didn't leave commented-out/debugging code

Reminders

• Add New configuration option and document them (in sdcm/sct_config.py)
• Add unit tests to cover my changes (under unit-test/ folder)
• Update the Readme/doc folder relevant to this change (if needed)

[Lakshmipathi]

Running tests once its completed it update job url

[github-actions]

identified changes in generated code

diff found by running:
bash ./docker/env/hydra.sh update-conf-docs:

 docs/configuration_options.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

[pehala]

How is the test evaluated? Manually from grafana?

[Lakshmipathi]

How is the test evaluated? Manually from grafana?

Yes, manually from grafana keyspace charts. If this job runs against non per-tablet hints branch, job will fail with syntax error.

[pehala]

Yes, manually from grafana keyspace charts. If this job runs against non per-tablet hints branch, job will fail with syntax error.

Please mention it in the docstring for both config and pipeline so it is clear for anyone

EDIT: Also please add correct backport labels

[Lakshmipathi]

Jenkins job status with 2025.2.0~rc1:
https://argus.scylladb.com/tests/scylla-cluster-tests/6057b3c9-196c-4769-8805-92357d646ef5 hits scylladb/scylladb#24156
https://argus.scylladb.com/tests/scylla-cluster-tests/0bf46a66-341f-4112-9ea8-efd7e323e294 hits scylladb/scylladb#24115

[pehala]

@scylladb/qa-maintainers please review and merge

[soyacz]

shouldn't this pipeline/test config go under features dir?

[soyacz]

need instructions what to evaluate
if instructions are provided - can it be automated?

[pehala]

Agree on the instructions, but given what we are trying to do and how uncertain the feature is (they are hints, so not 100% accurate) I think it is not worth the effort to automate it.

[vponomaryov]

We have prometheus with metrics and if we expect some specific value ranges we can verify it.
Or if not verify then, at least, report to Argus to the "results" section.