Andrei Chekun

> Example:  that's funny, since if you click the failed test case there will be a normal link and not just an HTML tag. I'll try to play around...

@mykaul seems this is the limitation of the plugin in Jenkins. https://jenkins.scylladb.com/job/sct-github-PRs-scan/job/scylla-dtest/job/PR-3831/35/testReport/hintedhandoff_additional_test/ dtest have the same issue with this, so I suppose we will live with that. @kbr-scylla @piodul what...

@kbr-scylla seems it was GCed. your run didn't pass because I've changed the job configuration to check another thing. restarted it with the correct config and added a second fail...

@kbr-scylla 1. This information missing since it's printed by pytest itself and not the test. This stack trace is printed on the summary page of the test and it's not...

Changes from the previous commit: 1. Rebase latest master 2. Rename the log files in the failed_directory 3. Add stacktrace 4. Revert several unwanted changes

Fix code review comments. Remove magic log path slicing with Path.stem Rephrase the comment about why we need formatter from root logger Remove FAILED_KEY since we using the whole report...

Split test.py and pytest log in two files

> @xtrey please, resolve conflicts Done.

CI failed with known [issue](https://github.com/scylladb/scylladb/issues/23592)

> I don't get this. Does it mean that I can no longer run `test.py --name=boost/something` and have the test executed? Presumably no, so it means something else. What? You...