Closed RyszardWithAZ closed 10 months ago
@RyszardWithAZ What's your $ZV
? There's a known server-side bug that affects compilation output redirection. I'm not sure how the unit tests are run on compile, but since the results are just console output the cause may be this known bug.
@RyszardWithAZ What's your
$ZV
? There's a known server-side bug that affects compilation output redirection. I'm not sure how the unit tests are run on compile, but since the results are just console output the cause may be this known bug.
IRIS for UNIX (Red Hat Enterprise Linux 9 for x86-64) 2022.1.2 (Build 574_0_22637U) Thu Jul 27 2023 18:49:43 EDT
Yeah, that version has the bug unfortunately. This has been fixed in versions 2022.1.4+, 2023.1.2+, and 2023.3. Since you're on an adhoc I doubt you can upgrade easily, but I can give you the devkey for the fix to include in your next adhoc. You can try a community edition kit of one of those versions to test if the fix resolved your issue. #1172 is a previous issue related to this bug.
Oh that's great, I'll let my internal folks know that there's a fix coming!
No problem, happy to help! The internal tracking number for the fix is DP-424221.
This has been happening for a long time now (for years now!), but I never followed up on it until today.
When the unit tests are run after a routine/class compile, we get the results in the Output window. BUT, the actual results don't display.
See attachments for what I get in VScode vs in Studio. vscode output.txt studio output.txt
In the VScode output, note the big space between the begins... and the passed message. In between all those, we get the actual results, like