You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I thought that MR #87 and #88 would solve this issue, it still happens on Windows 10 using MiniZinc 2.7.2. The flag -t is now passed correctly to Chuffed, but it seems like MiniZinc still kills Chuffed before it has the time to print anything. This can be seen using the flag -s, where Chuffed doesn't print any of its statistics when the timeout kicks in (when I'm pretty sure back in the days, it was doing so). Note that this behavior of missing output also happens when using Ctrl+C (only ***Interrupted*** is printed).
The text was updated successfully, but these errors were encountered:
We believe that the problem was caused by Chuffed not printing the comment that terminates a statistics block. This meant that MiniZinc did not flush the statistics back to the user.
Relates to #85 and MiniZinc/libminizinc#523.
While I thought that MR #87 and #88 would solve this issue, it still happens on Windows 10 using MiniZinc 2.7.2. The flag -t is now passed correctly to Chuffed, but it seems like MiniZinc still kills Chuffed before it has the time to print anything. This can be seen using the flag -s, where Chuffed doesn't print any of its statistics when the timeout kicks in (when I'm pretty sure back in the days, it was doing so). Note that this behavior of missing output also happens when using Ctrl+C (only ***Interrupted*** is printed).
The text was updated successfully, but these errors were encountered: