View Issue Details

IDProjectCategoryView StatusLast Update
0005540Spring engineAIpublic2017-05-10 12:14
ReporterGoogle_Frog Assigned ToKloot  
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionno change required 
Product Version103.0 +git 
Summary0005540: 103.0.1-805 Circuit AI does not load
DescriptionCircuit AI loads with 103.0.1-764-gae7487f but not with 103.0.1-805-gdf6f458. The attached infolog has an error within it that says Circuit was not found.
TagsNo tags attached.
Attached Files
infolog.txt (Attachment missing)
infolog-2.txt (Attachment missing)
infolog-3.txt (Attachment missing)
Checked infolog.txt for Errors

Activities

Kloot

2017-04-28 12:38

developer   ~0017539

The dll needs to be recompiled if Circuit uses code from Spring's System/Util header.

Google_Frog

2017-05-10 05:13

reporter   ~0017589

lamer recompiled circuit 10 days ago and it has the same issue since then. The latest version I tested is 103.0.1-877-g9eb8948.

Google_Frog

2017-05-10 05:16

reporter   ~0017590

Issue here: https://github.com/rlcevg/CircuitAI/issues/39

Should this have been a windows-only problem? lamer says he has no problem on linux which makes little sense for a library issue. Perhaps they are not compiling with a recent enough engine.

lamer

2017-05-10 11:46

reporter   ~0017592

Infolog says
Binary Word Size: 32-bit emulated
But it tries to load CircuitAIHard64 (64-bit)

My guess is that chobby downloaded circuit for wrong platform (maybe because both platform 32/64 are present).

Kloot

2017-05-10 12:00

developer   ~0017593

Last edited: 2017-05-10 12:02

I have no older local builds of CircuitAI in reserve to test if this was/is OS-specific, although my first guess would be no. It may also be due to differences in the compiler used for win-buildbot Spring and the Circuit dll, or a 32-/64-bit binary mismatch.

For me personally the AI lib (compiled from f874a90d) loads with engine 9eb89489 and ZK fa79d7e5, it just crashes during initialization.

Kloot

2017-05-10 12:11

developer   ~0017594

Last edited: 2017-05-10 12:14

didn't read the logs carefully enough, confirmed to be mismatched binaries.

Issue History

Date Modified Username Field Change
2017-04-28 07:28 Google_Frog New Issue
2017-04-28 07:28 Google_Frog File Added: infolog.txt
2017-04-28 12:38 Kloot Note Added: 0017539
2017-04-29 14:45 Kloot Assigned To => Kloot
2017-04-29 14:45 Kloot Status new => closed
2017-04-29 14:45 Kloot Resolution open => no change required
2017-05-10 05:13 Google_Frog Status closed => feedback
2017-05-10 05:13 Google_Frog Resolution no change required => reopened
2017-05-10 05:13 Google_Frog Note Added: 0017589
2017-05-10 05:14 Google_Frog File Added: infolog-2.txt
2017-05-10 05:14 Google_Frog File Added: infolog-3.txt
2017-05-10 05:16 Google_Frog Note Added: 0017590
2017-05-10 05:16 Google_Frog Status feedback => assigned
2017-05-10 11:46 lamer Note Added: 0017592
2017-05-10 12:00 Kloot Note Added: 0017593
2017-05-10 12:01 Kloot Note Edited: 0017593
2017-05-10 12:02 Kloot Note Edited: 0017593
2017-05-10 12:11 Kloot Status assigned => resolved
2017-05-10 12:11 Kloot Resolution reopened => no change required
2017-05-10 12:11 Kloot Note Added: 0017594
2017-05-10 12:14 Kloot Note Edited: 0017594