I added lots of print logging and the runner just seems to disappear into the black hole somewhere with no information.
Any tips on on what triggers the runner to think the command has ended or if you can see any errors that aren’t surfaced with debug=true would be helpful.
yeah, I was hoping with debug = true, I would get an trace, dump or a report if my program ends early but no luck. Is there anyway to trigger anything else?
Like I said I’ve tried a few environments and can’t get the same thing to happen. But I don’t have the same test harness.
yeah, I was hoping with debug = true, I would get an trace, dump or a report if my program ends early but no luck. Is there anyway to trigger anything else?
That flag only controls the verbosity of the tester’s logs. Unfortunately, some stages don’t have detailed output even with debug = true.
One thing you could try is comparing your current code with a previous version that successfully passed Stage #BR6.