review: Fix failing builds because of the usage of random in CompilationUnit comparison #1954
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR intends to fix the failing build created after the merge of #1938
Apparently we got lucky with the random when it was first executed: the usage of some random number could lead to the trigger of the following exception
IllegalArgumentException:Comparison method violates its general contract!
This happens during the sort algorithm because as we use a random answer for sorting, the result is not transitive.
To avoid this problem I decided to completely remove the concept of seed and to just sort or shuffle the CU list, based on a switch value in the environment.
Before merging the PR I need to uncoment the lines of the shell script to make it only available on master commits: here I uncommented them only to check if travis is fixed.