Limit a timeout in testing robustness validation

[serathius]

As part of #15598 I was working on re-implementing the history patching to avoid too much space explosion. One thing I noticed that it's not easy to reproduce linearization timeout if patching is totally disabled.

To ensure that patching is working and helping reduce the runtime, I have generated and added a case to TestValidation that is expected to run over 5 minutes without any patching

Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.

[serathius]

cc @ahrtr

[serathius]

ping @ahrtr

[ahrtr]

a quick question before I take a closer look, why add so many json files into the repo?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.

[serathius]

Sorry for forgetting about this PR and your question.

a quick question before I take a closer look, why add so many json files into the repo?

Those are report files from robustness tests, that I added to the repo for testing. They are used to ensure there is no breaking change nor performance regression on robustness testing.

There is a testdata directory that you can just add a robustness report from CI and a test will run robustness validation on it. It's pretty useful to allow reproduction of bugs in robustness test framework.

[serathius]

ping @ahrtr

[ahrtr]

lgtm

Please rebase this PR before merging. Previously I ran into a couple of cases which github did not identify the conflict.

[serathius]

Done

[serathius]

/retest

[serathius]

It will be more tricky than anticipated :(

[serathius]

/retest

[serathius]

Ok, I run into a problem with creating a cpu bound test that will execute in CI in a predictable time.
Locally on my machine the test runs 2s, while in CI it times out after 60s.

Will remove adding the scenario for now.