Do not timeout tests locally

[Vampire]

No description provided.

[Vampire]

• Do not timeout tests locally #2077 👈 (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.87%. Comparing base (8017fc3) to head (7fdbddf).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##             master    #2077   +/-   ##
=========================================
  Coverage     81.87%   81.87%           
- Complexity     4686     4689    +3     
=========================================
  Files           452      452           
  Lines         14656    14656           
  Branches       1845     1845           
=========================================
  Hits          12000    12000           
  Misses         1976     1976           
  Partials        680      680           

[leonard84]

We should probably add debug detection to the timeout extension instead.

https://github.com/junit-team/junit5/blob/ee52c64336ad3a079d598bd1c3884bafbc285047/junit-platform-commons/src/main/java/org/junit/platform/commons/util/RuntimeUtils.java#L42

[Vampire]

I used debug detections in the past and they only work semi-reliably from my experience.

But I also think it is not the right way, but like I did.

My box was occupied with other stuff and at the same time doing a full check on Spock and the 15 minutes were busted even without debugging. I don't see any reason to have that limit locally, you can at any time abort the build manually easily if you see it hangs.