Pytest-retry

Bug Fixes
* use verbosity count for trace limit rather than unlimited trace depth in verbose mode str0zzapreti in https://github.com/str0zzapreti/pytest-retry/pull/41
* Code snippets are now highlighted in the readme for supported editors (thanks Borda)

**Full Changelog**: https://github.com/str0zzapreti/pytest-retry/compare/1.6.2...1.6.3

Bug Fixes
* fixed Item instantiation error in Pytest 8 by str0zzapreti in https://github.com/str0zzapreti/pytest-retry/pull/35


**Full Changelog**: https://github.com/str0zzapreti/pytest-retry/compare/1.6.1...1.6.2

Bug Fixes
- Fixed an OSError exception which could occur due to a socket port assignment conflict when running multiple instances of pytest-retry with pytest-xdist n > 1 simultaneously on the same machine

New Features
- Retry reports will now be displayed when using pytest-xdist with n > 1
- Retry reports now log if a retried test passed on a subsequent attempt. Previously, only failures were logged


Fixes
- Additional test coverage to validate xdist compatability for retry reports
- Additional test coverage to prevent regressions with fixture resets during retries
- Cleaned up some internal naming for clarity and consistency


**Full Changelog**: https://github.com/str0zzapreti/pytest-retry/compare/1.5.0...1.6.0

New Features
- Global retries can now be configured using .ini files as an alternative to using command line options. This also adds pyproject.toml support for free. See the updated readme for details.


Bug Fixes
- Cumulative timing mode only summed first and final attempt durations when retries > 1.
- Empty flaky mark would default to 0 retries, but still retry once (task failed successfully)

Bug fixes
* Fix for issue 20: Unexpected strict xfail exception