search

GMUEClab / ecj

ECJ Evolutionary Computation Toolkit
http://cs.gmu.edu/~eclab/projects/ecj/
123 stars 42 forks source link

Unable to build master #61

Closed remz1337 closed 4 years ago

remz1337 commented 4 years ago

Hello,

I just downloaded the latest release (v27) and ran mvn clean package but I'm getting multiple errors.

Using Java 1.8 and Maven 3 (from IntelliJ)

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test) on project ecj: There are test failures.

Thanks

remz1337 commented 4 years ago

I just tried on my linux machine and didn't work either. git clone ecj mvn clean package

and I get : [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile (default-testCompile) on project ecj

eclab commented 4 years ago

I'd recently made a non-backward-compatible change to Evolve and forgot to change the tests accordingly. I added a little bit of backward compatibleness again. See if it builds now.

On Aug 11, 2020, at 4:55 PM, Rémi Bédard-Couture notifications@github.com wrote:

I just tried on my linux machine and didn't work either. git clone ecj mvn clean package

and I get : [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile (default-testCompile) on project ecj

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

remz1337 commented 4 years ago

Thanks, it now builds successfully on Linux, but I still have some tests failure on Windows. I'll close this one and open another issue.

SigmaX commented 4 years ago

@eclab — the "fatal errors" do indeed appear fishy. I'll try and look later this week and see if our test harness has false negatives.

SigmaX commented 4 years ago

I went ahead and silenced the output of the tests (commit https://github.com/GMUEClab/ecj/commit/b188e3578343eaf50ff83fff0ed5c3d1c662b7fd). Some of the tests check for failures that are expected, so they do indeed print out "FATAL ERROR" upon success. Not sure if silencing everything is the best idea long term (since it could make it harder to debug failing tests), but at least the output of success is unambiguous this way.