Trouble with compiling on Windows

[Lustyn]

:KristAPI:processResources UP-TO-DATE
:KristAPI:classes
:KristAPI:jar
:compileJava
warning: [options] bootstrap class path not set in conjunction with -source 1.6
1 warning
:processResources
:classes
:jar
:assemble
:compileTestJava

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all dependencies for configuration ':testCompile'.
> Could not resolve junit:junit:4.12.
  Required by:
      :turbokrist:unspecified
   > Could not resolve junit:junit:4.12.
      > Could not parse Ivy file file:/C:/Users/justy/.gradle/caches/modules-2/metadata-2.16/descriptors/junit/junit/4.12/4471c3b2f5ea2d40ffaa8b3948cdbacd/ivy.xml
         > Content is not allowed in prolog.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 36.953 secs```

[Lustyn]

@apemanzilla No BSOD this time around...

[Lustyn]

@BTCTaras: :100:

[dmarcuse]

In this case, it errored before it even ran the code - it couldn't find junit, which is used to run the tests.

I'm guessing that what happened is that when you got a BSOD the first time you tried to build, gradle didn't stop properly and left a bunch of broken caches everywhere. Try these commands, in order:

gradlew clean
gradlew build --refresh-dependencies

[Lustyn]

Got the same identical error.

[Lustyn]

:clean
:KristAPI:clean
:turbokrist-cli:clean UP-TO-DATE

BUILD SUCCESSFUL

Total time: 7.714 secs
C:\Users\justy\Desktop\turbokrist-master\turbokrist>gradlew build --refresh-dependencies
:KristAPI:compileJava
:KristAPI:processResources UP-TO-DATE
:KristAPI:classes
:KristAPI:jar
:compileJava
warning: [options] bootstrap class path not set in conjunction with -source 1.6
1 warning
:processResources
:classes
:jar
:assemble
:compileTestJava

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all dependencies for configuration ':testCompile'.
> Could not resolve junit:junit:4.12.
  Required by:
      :turbokrist:unspecified
   > Could not resolve junit:junit:4.12.
      > Could not parse Ivy file file:/C:/Users/justy/.gradle/caches/modules-2/metadata-2.16/descriptors/junit/junit/4.12/4471c3b2f5ea2d40ffaa8b3948cdbacd/ivy.xml
         > Content is not allowed in prolog.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 26.832 secs

[dmarcuse]

Alright. You should have a folder named .gradle in your user home folder. Can you try deleting said folder, then running the commands from above?

By the way, the backticks (`) need to be on newlines for code formatting.

[Lustyn]

Got yet another BSOD. KERNEL_SECURITY_CHECK_FAILURE

[dmarcuse]

This problem is definitely with your system configuration then. This error is usually related to driver issues or memory corruption.

[Lustyn]

Thought I would link this info here for anyone interested: https://forums.geforce.com/default/topic/904988/kernel-security-check-failure/?offset=114

[Lustyn]

Aswell as this: http://nvidia.custhelp.com/app/answers/detail/a_id/3832

[Lustyn]

Installing that driver allowed me to build the project without issues.

[dmarcuse]

In that case you should be able to run it just fine.

[Lustyn]

I am able to run it just fine, but the speeds are unfortunately disappointing for turbokrist. Around 2-5MH/s for NVIDIA 940m...

However, using JCLMiner I got around 200MH/s for NVIDIA 940m...

I think turbokrist might need some optimization.

I am using the same worksize for both.

[dmarcuse]

No, I haven't implemented the profiler so it's going to be running with a low work size. Remember the -d ###:### option from JCLMiner? Use that but with -w instead of -d, so it looks like this - -w ###:###

[Lustyn]

Yes, I am using the identical worksize on both. Unfortunately, still getting a measly 2.2 MH/s