Join GitHub today
Command line debugging tests fail to run on Appveyor and cruise-control #1176
Refer to Issue #882 to see changes made for command line debugging. (Seetestbed/test/cruise.compiler.CompilerErrorOutputTests and testbed/test/cruise.compiler.RuntimeErrorOutputTests)
The tests built for the command line debugging fix are not running on Appveyor and cruise-control machines. The majority of tests run fine on all other machines (including Travis), but all fail to find the text files used to verify the results in the other two machines.
The likely cause behind this is the use of relative paths in CompilerErrorUtil.java and RuntimeErrorUtil.java. These two utility functions expect the execution environment to be one directory deep from the root, and attempts to find the correct files relative to that position. Appveyor and cruise-control likely have a different execution environment and thus get an invalid path when opening the expected .txt files.
referenced this issue
Dec 8, 2017
In Appveyor, if I activate the error output tests, then 6 of 9 tests fail:
This is done in branch Java11AndIssue1176
What we need to do is to see why the
method at RuntimeErrorUtil.java
is failing in these 6 specific cases. I suspect it might be line-end
Total time: 0 seconds