Coding-only loop ended the session and jumped to the report with ~16 min left, while tests were 2/4 and code was still being edited

Geschlossen
  • Stimmt etwas nicht?
#83 5 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
cpp
Bereich
full-stack

Rechercherichtung

No source file or test is named. Start by reproducing the coding-only loop with a 30-minute Medium interview, incomplete code, and failing tests, then trace the REACTO completion, timer, and transition to the final report. Done means the session does not end before the selected duration or an explicit user action, including when REACTO steps appear complete.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Description:

In a Medium interview running in coding-only loop mode (behavioral round skipped), the session ended on its own and jumped to the final report with ~16 minutes still on the clock. My code was still being edited and the last test run was only 2/4 passing, yet all REACTO steps were shown as complete and Jim wrapped up the session. I did not choose to end the interview.

What happened:

Started a Medium interview, 30 min, in coding-only loop mode.
Worked through the problem; the REACTO tracker showed all steps checked: Repeat, Example, Algorithm, Coding, Test, Optimizations.
Ran the tests: result was 2/4 passed (FAIL two profitable swings: expected 7, got 14). I was still editing the code (line 12 was mid-typing) to fix the failing cases.
With the timer at 16:37 remaining, Jim said:
"Thanks so much for your time today, it was great speaking with you. Your performance report will be ready in just a moment."

The session ended and jumped straight to the final report, even though the code was incomplete and tests were not passing.
Expected:
The session should continue until the chosen duration elapses (or I end it), especially while tests are failing and the code is still being edited. Marking all REACTO steps complete should not end the session while tests are at 2/4.

Actual:
With ~16 minutes left, tests at 2/4, and code still being edited, all REACTO steps were marked complete and the session ended and jumped to the final report.

Reproducibility:
Observed once on 2026-09-21. I ran another interview the next day and it did not happen again, so I could not reproduce it. Reporting it as a real observed incident rather than a reliably reproducible one.

Screenshot:

Taken one second before the session jumped to the report
Image

Environment:

Date/time: 2026-09-21, ~20:10 (UTC+8)
OS: Windows 11
Browser: Microsoft Edge 153.0.4234.48
Interview mode: coding-only loop (behavioral round skipped)
Interview: Medium, duration 30 min
Problem: Single Slot Reseller
Language: C++
Timer at cutoff: 16:37 remaining
Test results at cutoff: 2/4 passed (FAIL two profitable swings: expected 7, got 14)
Report: generated normally (no error)
Git revision: 7efebb0 (7efebb002b7c2a3e9fb856a0855582d32ca77d98)

Vorherrschende Sprache
Rust
Sterne
223
Forks
148
Ø Merge
1 T. 11 Std.
Gemergte PRs (30 T.)
224

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus sysprog21/codetrial

Alle Issues in sysprog21/codetrial

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.