| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Added new setting -Ygen-javap, which takes a directory as an argument
and generates javap output for every generated classfile. There is still
a lot of noise in a diff: still todo is postprocessing the output to
remove diff-noise-generating numbers and such. No review.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
I chased a lot of ghosts before finding the real culprit for why partest
failures have been unfailing.
Process(Seq("bash", "-c", "exit 42")) ! // 42 Process(Seq("bash",
"-c", "exit 42")) #> logFile ! // 0
That behavior is not yet fixed, but I altered partest not to use #> and
fixed the test which should have been failing but wasn't. Closes #4227,
no review.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
partest --grep has never worked quite right (at least not in the
"sideported" version.) Now it looks harder for matching tests: the check
file or any java or scala source file can match. And directory based
tests will be properly included. Try it out:
test/partest --grep java
No review.
|
| | |
|
| |
|
|
|
| |
things which used it to use sys.process. No review.
|
| |
|
|
|
| |
Made partest update a checkfile even if it doesn't exist. No review.
|
| | |
|
| | |
|
| |
|
|
|
| |
multiple-reporting-of-failures bug. No review.
|
| | |
|
| |
|
|
|
|
| |
One element of the partest situation: Reporting and recovering correctly
when the compiler crashes. No review.
|
| |
|
|
|
|
|
|
| |
Added specialized test to ant build, and ported old specialized 'run'
tests to check the number of boxings.
No review.
|
| |
|
|
|
|
|
|
|
|
| |
Added a new test group - specialized.
Modified partest to add a jar with instrumented classes to classpath when compiling and running tests.
Added a primary version of the instrumented BoxesRuntime, and a script to produce a jar for it.
Added the 'speclib' folder to partest files, which contains the jar with the instrumented classes.
Review by dragos.
|
| |
|
|
|
|
|
|
| |
prejudice and puts the new process code to work instead. There are still
a couple bugs on my short term partest list. If this commit causes some
weird issue which only arises on virtualized windows you can expect to
hear from me next by postcard from st. lucia. No review.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Imported sbt.Process into trunk, in the guise of package
scala.sys.process. It is largely indistinguishable from the version in
sbt, at least from the outside.
Also, I renamed package system to sys. I wanted to do that from the
beginning and the desire has only grown since then. Sometimes a short
identifier is just critical to usability: with a function like error("")
called from hundreds of places, the difference between system.error and
sys.error is too big. sys.error and sys.exit have good vibes (at least
as good as the vibes can be for functions which error and exit.)
Note: this is just the first cut. I need to check this in to finish
fixing partest. I will be going over it with a comb and writing
documentation which will leave you enchanted, as well as removing other
bits which are now redundant or inferior. No review.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
StreamAppender is the leader among suspicious things which look like
they freeze things, so I started ripping it out. Again. No review.
|
| |
|
|
|
|
|
|
|
|
| |
down the long and freezy road once again. With this patch you can send a
SIGHUP to partest and it will spew a bunch of internal state. It is also
possible I fixed the underlying issue by cleaning up the super fragile
dependence on counters never getting the least bit off track. If fixed,
it'll still be fun to send signals. If not, this will be coming in handy
reeeeeal soon. No review.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mopping up after the deprecation of exit and error. It is decidedly
non-trivial (at least for the IDE-impaired) to be completely sure of
which error function was being called when there were about twenty with
the same signature in trunk and they are being variously inherited,
imported, shadowed, etc. So although I was careful, the possibility
exists that something is now calling a different "error" function than
before. Caveat programmer.
(And let's all make it our policy not to name anything "error" or "exit"
from here on out....) No review.
|
| |
|
|
|
|
|
| |
You shall not pass the testing stage when abort crashes the resident
compiler. previously it succeeded even though the error message was
printed. Review by phaller
|
| |
|
|
|
|
| |
(apparently) the bug which has had me chasing concurrency ghosts
throughout the haunted castle. No review.
|
| |
|
|
|
|
| |
partest sets javaccmd system property when running tests. Review by
dragos.
|
| | |
|
| |
|
|
|
|
|
|
| |
Ported --update-check from partest-alternative to partest actual. Once
again all can daily demonstrate their amazing resolve by not mass
updating checkfiles by the hundreds with whatever the current output
happens to be. No review.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Some exception handling fixes in parallel collections. Fixed some
regressions. Fixed some tests.
No review.
|
| |
|
|
|
|
| |
One more partest fix where output was redirected using a global
variable, causing errors with multiple actors. Review by plocinic
|
| |
|
|
|
|
|
|
|
| |
Log file is printed now right away if:
- test fails due to an exception thrown in the a test
- test fails due to a ScalaCheck test fail
- test fails due to compiler errors in ScalaCheck tests
Review by extempore.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Solved issues with fork join pool creators, and the issue with
scalacheck output.
Done by Philipp and me.
Review by phaller.
|
| |
|
|
|
|
|
| |
Fixed a scalacheck test group "test entire subdirectory" problem. It's
now possible to add scalacheck tests consisting of multiple files. No
review.
|
| | |
|
| |
|
|
|
|
| |
Fixes the way results of Scalatest are checked by Partest. Contributed
by Kato Kazuyoshi. Review by phaller.
|
| |
|
|
|
|
| |
Enabled partest to run entire directories for scalacheck test group.
Review by extempore.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Couldn't bear to see sbt seemingly so close but still unable to run
tests. Made some progress but bogged down in scalacheck when I realized
things were farther from working than I'd thought. Please forgive this
brief expression of frustration, because the despair is palpable:
the weeks of work I did on partest was apparently of no interest,
and now I'm in here having to fix the same partest bugs again, in a
more virulent form. They've evolved into some kind of ant-partest-sbt
artificial creature, more fearsome than any one of them could be under
its own power.
Did we not know we have a whole directory full of pretty code like this?
List(
"Scala compiler classes in: " + testBuildDir,
"Scala version is: " + nsc.Properties.versionMsg,
"Scalac options are: " + universe.scalacOpts,
"Java binaries in: " + javaBin,
"Java runtime is: " + javaInfoString,
"Java runtime options: " + (Process.javaVmArguments mkString " "),
"Javac options are: " + universe.javacOpts,
"Java options are: " + universe.javaOpts,
"Source directory is: " + src,
"Selected categories: " + (selectedCategories mkString " "),
""
) mkString "\n"
It's src/partest-alternative in case anyone wants to consider any of it.
At the very least there are individual files or functions which could be
cherry picked.
-- This patch contains: --
Readability efforts. Twelve parameter functions whose last six
parameters are "true,true,failedOnly,true,false,log" are pretty
challenging to work with.
Changes to the environment variables sbt was setting to look a bit more
like what partest expects and will crash without.
Sets partest.debug=true if the sbt logger level is at Debug.
On my machine all test groups except scalacheck appear to run to
completion.
Review by moix. (Hello, moix! I am available for assistance if you are
in the market for it. You have brought us long suffering ant-ers to the
brink of sbt goodness: and now, we enter the fray!)
|
| |
|
|
|
|
| |
Unbroke the command line ~/test/partest tool, which was displeased at
being unable to find scalacheck.jar. No review.
|
| |
|
|
|
|
|
| |
Partest changes - partest now uses scalacheck.jar from the build/pack dir.
Review by phaller.
|
| |
|
|
|
| |
Review by phaller (not urgent).
|
| |
|
|
|
|
| |
Partest support for sbt (with failed only and specific files only
options) Support for triggered execution
|
| |
|
|
|
|
| |
Partest task will go into verbose debug mode when ant's debug flag is
set.
|
| | |
|
| |
|
|
|
|
|
|
| |
Changed the script runner mechanism to alchemize from AST atoms rather
than generating wrapper source, and fixed script position reporting.
This patch does not include a discussed change to mark some positions as
synthetic. Closes #3119, #3121. Review by milessabin.
|
| |
|
|
|
| |
Removed more than 3400 svn '$Id' keywords and related junk.
|
| |
|
|
|
|
|
|
| |
Remove the sourcepath prefix from the logs and only then do dos2unix
paths changing (otherwise #3054 fails). It is a bit ugly but it is only
done for buildmanager (paul was doing it anyway in his reverted partes).
That should really fix the windows build. No review.
|
| | |
|
| |
|
|
|
|
|
|
| |
changes necessary to plug it back in while preserving everything which
has happened since then in tests and such, but we should be the lookout
for overreversion. Review by phaller (but as a formality, I don't think
it requires direct review.)
|
| |
|
|
|
|
| |
Rolled back a subset of partest to use StreamAppender and avoid
io.Process. No review.
|
| |
|
|
|
|
|
| |
Reverted change that made partest fail with 'bin/javac: no such file'
when JAVA_HOME was not set (instead of using the javac on the PATH).
Reviewed by extempore, so no review.
|
