diff options
| author | Seth Tisue <seth@tisue.net> | 2016-10-05 12:11:07 -0500 |
|---|---|---|
| committer | Seth Tisue <seth@tisue.net> | 2016-10-06 00:49:40 -0500 |
| commit | 5b04e9cd70e413307cbaee6b3562dfd91579abfe (patch) | |
| tree | d25bf5cdc54ae2c07f281d30dddba9daaa067c41 /test/files/run/t7406.check | |
| parent | 1f6006d0d4f8edf4db04915702f8b7e3c8ca1f5e (diff) | |
| download | scala-5b04e9cd70e413307cbaee6b3562dfd91579abfe.tar.gz scala-5b04e9cd70e413307cbaee6b3562dfd91579abfe.tar.bz2 scala-5b04e9cd70e413307cbaee6b3562dfd91579abfe.zip | |
SI-5293 delete flaky collection performance tests
timing-based tests like these are way too sensitive to how many tests
are running in parallel, random disturbances in the AWS force (?),
and so forth.
the result being recurring intermittent failures such as
java.lang.AssertionError: assertion failed: scalaparset: 491535200 vs. javaset: 59864300
from
https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-windows/361/consoleFull
Rex and Adriaan both suggested simply deleting the tests, rather than
putting them in "pending" purgatory ("benchmarks do not belong in the
partest suite", period)
Diffstat (limited to 'test/files/run/t7406.check')
0 files changed, 0 insertions, 0 deletions