Search results

The default location for the exe installer packaging we use puts things in the Program Files folder. It probably should be moved elsewhere maybe?

https://johann.loefflmann.net/en/software/jarfix/index.html I'd run this should fix the association and then you should just be able to double click the jar files from github and it /should/ run.

Try to run the jar version from https://github.com/kolmafia/kolmafia/releases/tag/r26310 and not the EXE version now.

Uninstall any Java versions you currently have on your computer and then install 17 from https://adoptium.net/index.html It looks like you still have an older version installed that's causing all kinds of problems so this should probably resolve it.

The image is hosted by a third party website... maybe they were having issues? It's from https://shields.io

I don't have access the Github builds. But according to the actions log. Java configuration: Distribution: temurin Version: 17.0.2+8 Path: C:\hostedtoolcache\windows\Java_Temurin-Hotspot_jdk\17.0.2-8\x64 Jenkins is still using Java 16 (last big update I did 17 wasn't in...

In the scripts menu in the menu bar or if you know the name of the script you can call it from the CLI with the name of it... for example you can just type autoscend to run autoscend if you have it installed etc.

https://ci.kolmafia.us/job/Kolmafia/27295/execution/node/3/ws/build/reports/tests/test/index.html

Not sure how many people actually have the relay browser automatically open but I've been playing that way forever. So I'd like to see if you have relay browser set to automatically open that if you have enabled SVN update on login that it will delay opening of the relay browser until after the...

I wonder did you reboot at all inbetween these issues? Kind of sounds like there was a zombie java process still running that had stuff tied up.

Increasing the heap size for the java process and adding a swap file seems to have resolved this. I've removed debug mode from the Jenkins build process.

Looks like the jgit repo is returning a 502 server error and when it's checking for updates it's dying.

I made some configuration changes and added a swap file to the server, we'll see if this helps alleviate issues.

Not sure if anyone else might be more familiar with Gradle but we had it freeze today and here's the log: https://gist.github.com/fewyn/749b6a09209a4290ae833a378ab1da6c I thought it might be a memory issue but what I've seen that's just normal health checks. Any ideas out there?

And of course since adding it nothing has frozen except now it's doing it on builds... added a debug flag to the jar build portion to hopefully help identifying the culprit.

https://ci.kolmafia.us/job/Kolmafia/26709/execution/node/3/ws/build/reports/tests/test/index.html Tests are failing.

This is more of a tracking thing for myself but Jenkins has been freezing for awhile only sometimes during the testing of builds. Happened this morning with 26080, I have had a bandaid in place for awhile now where if Jenkins becomes unresponsive after 15 minutes it'll automatically restart the...

Is that new?

Uninstall your current version of JAVA and get 17 from https://adoptium.net/index.html. The version from Java.com/Oracle is outdated.

Build failed because Jenkins locked up for ~20 minutes looks like it got stuck on some test but I can't really figure out what and when Jenkins finally restarted it just timed out.