-
Notifications
You must be signed in to change notification settings - Fork 123
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
timer-3.2 test failure when building with tcl on osx #282
Comments
Thanks for the report. This is not a bug in JimTcl. It is simply that these timer tests are a bit fragile if running on a VM or an overloaded system. I suggest just disabling timer.test. BTW, I have some comments on the nixos configuration of JimTcl. Where is the best place to provide that feedback? |
On systems where we aren't getting enough cpu time. Heuristic check, but probably good enough in practice. Fixes #282 Signed-off-by: Steve Bennett <steveb@workware.net.au>
See #283 |
Thanks, we'll try applying that patch!
You can open an issue here and tag me |
When jimtcl is built with tcl on osx, this test fails:
This does not happen on linux or when bootstrapping with jim.
Initially discovered here: NixOS/nixpkgs#253638 (comment)
The text was updated successfully, but these errors were encountered: