Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Minizinc option -t kills Chuffed before it prints output #135

Closed
raphaelboudreault opened this issue May 10, 2023 · 1 comment · Fixed by #139
Closed

Using Minizinc option -t kills Chuffed before it prints output #135

raphaelboudreault opened this issue May 10, 2023 · 1 comment · Fixed by #139
Labels

Comments

@raphaelboudreault
Copy link

raphaelboudreault commented May 10, 2023

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).

@Dekker1
Copy link
Collaborator

Dekker1 commented May 24, 2023

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.

@Dekker1 Dekker1 added the bug label May 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants