You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added something that works, although I'm not too happy about it because it indeed doesn't run in parallel – this used to be possible but gradle somewhere lost the ability to run intra-project tasks in parallel... Strange.
The 'beast' task essentially duplicates test task's configuration multiple times over. You should pass '--tests' filter to restrict each run to the test (or suite) you're interested in. The 'tests' option is identical as in the regular 'test' task. Example:
Filed a pull request with a simple 'beast' mode. This is pretty much an equivalent of what @rmuir suggested from within a shell script: it just re-runs the same test task sequentially over and over. The benefits may be that it reuses the same syntax for test filtering (--tests ...) and it "understands" when the randomization seed if fixed to one value vs. random in each test run.
This isn't ideal (no parallel execution) but works. To get parallelism with gradle's worker is a much more ambitious endeavor.
I allowed myself to add it in since there's been no feedback. I think it's better than nothing and it is nicely decoupled from anything else. If somebody has an idea for improving parallelism (maybe ask gradle folks) then it'd be great to know how to achieve it (pass an entire task to a gradle worker API).
Migrated from LUCENE-9465 by Dawid Weiss (@dweiss), resolved Aug 18 2020
Attachments: LUCENE-9465.patch
Linked issues:
Pull requests: apache/lucene-solr#1757
The text was updated successfully, but these errors were encountered: