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.88%. Comparing base (7f3c011) to head (48c6bdc).

Additional details and impacted files

@@            Coverage Diff            @@
##             master    #2174   +/-   ##
=========================================
  Coverage     81.88%   81.88%           
+ Complexity     4728     4727    -1     
=========================================
  Files           463      463           
  Lines         14771    14771           
  Branches       1871     1871           
=========================================
  Hits          12095    12095           
  Misses         1988     1988           
  Partials        688      688           

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

🚀 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.