Fix the @Retry documentation

[Vampire]

No description provided.

[Vampire]

• Fix the @Retry documentation #2174 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.93%. Comparing base (52ad7b1) to head (801f260).

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #2174      +/-   ##
============================================
+ Coverage     81.90%   81.93%   +0.03%     
- Complexity     4732     4734       +2     
============================================
  Files           463      463              
  Lines         14767    14767              
  Branches       1869     1869              
============================================
+ Hits          12095    12100       +5     
+ Misses         1981     1977       -4     
+ Partials        691      690       -1     

Files with missing lines	Coverage Δ
spock-core/src/main/java/spock/lang/Retry.java	100.00% <ø> (ø)

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Vampire]

@leonard84 is this actually the intended and expected behavior?
That only expected failures in the feature method trigger a retry I mean.
I do some UI tests using Geb with Marathon driver and it happens sometimes on GHA that the application cannot be started and thus the driver throws an exception.

This is done in an iteration interceptor before calling proceed, the iteration interceptor is within the retry iteration interceptor due to using global retry extension. But as the error happens there and not during feature method invocation, it does not cause a retry.