New breakage!

[guygastineau]

@ErikSchierboom

Somehow the tests are failing now in the automated test runner. Here I have a screenshot of my solution to rna-transcription failing in the automated runner. I dumped it into a new test directorty here though, and I don't get the syntax error result.json. I get a passing results.json. The opacity of the website's process of running these exercises makes it very hard for me to figure out why this is happening when all of our tests are passing.

---

Here is a dump of the results.json I get when I run the test-runner tests locally including my rna-transcription exercise.

{"version": 2, "status": "pass", "tests": [{"name": "Empty RNA sequence", "status": "pass", "output": null, "test_code": "(equal? (dna->rna \"\") \"\")\n"}, {"name": "RNA complement of cytosine is guanine", "status": "pass", "output": null, "test_code": "(equal? (dna->rna \"C\") \"G\")\n"}, {"name": "RNA complement of guanine is cytosine", "status": "pass", "output": null, "test_code": "(equal? (dna->rna \"G\") \"C\")\n"}, {"name": "RNA complement of thymine is adenine", "status": "pass", "output": null, "test_code": "(equal? (dna->rna \"T\") \"A\")\n"}, {"name": "RNA complement of adenine is uracil", "status": "pass", "output": null, "test_code": "(equal? (dna->rna \"A\") \"U\")\n"}, {"name": "RNA complement", "status": "pass", "output": null, "test_code": "(equal? (dna->rna \"ACGTGGTCTTAA\") \"UGCACCAGAAUU\")\n"}]}

[ErikSchierboom]

@guygastineau The test runner returns the following in production: {"version":2,"status":"error","message":"Syntax error","tests":null}

I'll try to dig a bit deeper.

[guygastineau]

Thank you!

[ErikSchierboom]

I can at the very least confirm that the docker image works locally, so it should be some environment-specific issue.

[ErikSchierboom]

Could it somehow be due to exercism/scheme#262?

[guygastineau]

Well, it didn't happen until that PR. The new tests are tested against here though. It might be due to a misconfiguration in the per exercise or track-wide json config? I tried to update the config.json stuff to indicate that we have two test files "test-util.scm" and "test.scm" for each exercise, but maybe I messed it up.

[ErikSchierboom]

@guygastineau No, that should be fine. It does not make sense as locally I've updated to the latest version and that works.

[guygastineau]

I know. This is pretty confusing :/

[guygastineau]

I have to go to the gym, and I have some other work this afternoon, but I can be responsive throughout the afternoon here, EST, if we figure this out. I figure it is getting later where you are though, and you shouldn't spend your whole evening on this. I appreciate your time helping me with this ❤️

[guygastineau]

Are you able to see output from the test-runner on stderr from the docker image running the tests? The Syntax error message only occurs from one place in the code. It is asimplification to shield users/students from weird outout, but I make the test-runner print the exception out to stderr with a format like "Non-fatal error: %s\n". So, reading the stderr of the docker running the test for the site will give us a clue if it is available.

[iHiD]

Erik's finished for the day now.
stderr is Non-fatal error: (error assoc \"improperly formed alist ~s\" GC)\n"

[guygastineau]

@iHiD I pinged you at #34 . It now provides the full, raw output from both scheme implementations we try running the solutions whereas the previous output from stderr was just the first token of the output.

[iHiD]

I've merged that. Give it 10 then rerun your solution and I'll get the latest stderr for you?

[guygastineau]

I am still at the gym. Somehow it seems to have resolved itself. I don't know how that would happen or what it means, but only trying from my phone (very difficult) it appears the solution ran and is passing all tests now.

[guygastineau]

Nevermind. I got back to my laptop and upgraded the exercise again. It fails with the same error. If you are still up, @iHiD, there should be new stderr output now.