Imported From: https://issues.scala-lang.org/browse/SI-7198?orig=1
Reporter: @huitseeker
Affected Versions: 2.10.1-RC2, 2.10.1

@huitseeker said (edited on Mar 6, 2013 6:10:36 PM UTC):
One fix Idea from Martin : could partest accept a filter file, or a regular expression filter as a configuration parameter ?

That way it would remove lines that match that particular filter from the program's output before comparing it to the .check output. This also solves the issue of not being able to predict all possible VM routine warnings (and it would probably allow us to remove some garbage in tests' check files).

@som-snytt said:
This is related to the problem (which I haven't solved) of system-dependent file paths in output. Paul patched that by normalizing backslashes, but that affects other output like \u0022.

I have an experimental "modeline"-style feature for configs. It was motivated by scalacheck options, e.g.:

/*
 * scalac: -deprecation
 * scalacheck: -workers 1 -minSize 0 -maxSize 4000 -minSuccessfulTests 5
 */

For config specific to a test, it avoids extra files; my other idea was to process "enclosing" .flags files, e.g., presentation.flags.

Either in a .flags or header, filter: Java HotSpot or similar as a line-oriented filter.

Or map: _ replaceAll ('\\','/') or similar would be fun.

The other thing I noticed it that we compare stdout + stderr. It would be nice to be able to diff only stdout. I see my code uses a ProcessLogger (I forget that Process API as soon as I use it).

@som-snytt said:
scala/scala#2591

The commit uses a filters file for all tests, or all of a kind.

The other use case would be to turn off the inliner warning for everything; right now, a handful of tests specify that filter in a source header.

@som-snytt said:
The commit includes a global filters file; it's not obvious that it's desirable as a default configuration.