Abnormally long wait time and API connection error when generating evaluation report

[BOBOGUAGUA428]

Description:

After completing a CodeTrial session, the system takes an unusually long time to generate the evaluation report. The UI eventually displays a fallback message stating "The report is still unavailable. Leave safely, then retry the interview when the provider recovers" and shows an extended waiting timer (e.g., "Waiting 02:15").

Expected behavior:

The evaluation report should be generated within a reasonable timeframe.

Actual behavior:

The UI hangs on the "Jim is writing up your evaluation..." loading screen for an excessive amount of time. Meanwhile, the terminal running the executable logs the following network error:
interim review skipped: error sending request for url (https://generativelanguage.googleapis.com/v1beta/models/gemini-3.1-flash-lite:generateContent)
timing: Gemini cut its own turn, 2.8s of it unplayed; candidate audio so far: (nothing transcribed; check speaker echo or background noise)
timing: 0.77s from the candidate finishing to the reply starting
timing: 0.82s from the candidate finishing to the reply starting
interview ended by the browser: room=interview-cmfy0945 topic=control

(According to the terminal logs, the system was actually still processing replies in the background and it successfully detected that I manually aborted/terminated the CodeTrial session,However, the system still failed to proceed to the final grading and report generation phase.)

[jserv]

@BOBOGUAGUA428 #97 reports the same ending and asks for the same fix: the interview finishes, report generation fails on the Gemini generateContent call, no scores are produced. Yours failed on a transport error rather than a 503, which is the same class of provider failure, and #97 already asks for a retry on a transient one.

The message you saw, "The report is still unavailable. Leave safely, then retry the interview when the provider recovers", is deliberate rather than a hang. Commit 6db1a4f added it so that a provider that cannot answer is reported instead of being waited on indefinitely. The long wait and that line are therefore the known behavior; what is still open is the retry that #97 asks for.

Two facts would tell us whether anything here is separate from #97. The git revision of your build, from codetrial --version. And whether you ended the session from the browser before Jim finished: your log ends with interview ended by the browser, and how an early exit should interact with the report is #100.

If those come back with nothing new, please continue in #97 rather than keeping two threads on the same failure.

[dots0101]

You can even wait for more than 30 minutes.