Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix unit testing in modules needing engine-tests + natives #71

Open
Cervator opened this issue Apr 24, 2014 · 0 comments
Open

Fix unit testing in modules needing engine-tests + natives #71

Cervator opened this issue Apr 24, 2014 · 0 comments

Comments

@Cervator
Copy link
Member

Example module is Pathfinding, which had a transitive dependency on engine-tests (before I changed Core's build.gradle to blindly always depend on latest engine + engine-tests, probably temporarily) as well as a need for natives

While Jenkins now copies in natives for module builds unit tests that depend on an origin class in engine-tests, such as HeadlessEnvironment, the execution starts within the Gradle cache directory which is where the engine-tests jar ends up. Then natives detection fails to find the natives directory in the job workspace

http://jenkins.movingblocks.net/view/Modules/job/Pathfinding/106/console
MovingBlocks@a3181c1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant