-
Notifications
You must be signed in to change notification settings - Fork 26
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
Premature termination #184
Comments
I believe it's a bug from upstream, but needs confirmation. |
any news on this? |
Sent my understanding to @TobiasWrigstad , but never had the chance to really discuss them. |
I vaguely recall this. Maybe this can be discussed on our next group meeting? (I am quite swamped at the moment.) |
I believe this could be related to #274 |
I don't think #184 and #274 are related. Fixed in upstream, presumably by ponylang/ponyc@750feca, and merged in |
(I believe @albertnetymk is already working on a fix for this, but I'm opening an issue so that it's easier to track.)
The issue is that one of my benchmarks (Chemeneos) sometimes prematurely exits. The program sometimes terminates before it would normally exit. (might be related to #104? Notice line 170 of chameneos_redux.enc, no blocking is used in this case though. )
This problem doesn't occur using the following commit (and those before it):
[a47e15a] Merge pull request #166 from albertnetymk/trace-future-value
The code is located at https://gist.github.com/eastlund/b7ce51ac8e605ec4220b
Remember to run the program with an argument, the problem occurs a lot on my machine when using 5000000 as input argument, but this likely differs between machines.
Expected output when running ./chameneos_redux 5000000:
Some numbers will differ between each run. (this output will be changed a bit in the final version of the benchmark) The important thing is that the last "spelled" line is printed ("one zero zero zero zero zero zero zero" in this case).
Example of erroneous output:
The program doesn't always prematurely terminate at the exact same point each time, the above example is the one that was most common for me. Also note that the issue can be difficult to reproduce and it's unlikely to occur on my machine when using sizes < 10^6 (have not tested if the probability of failure scales with input size)
I think @kikofernandez previously mentioned that this issue does not appear on MacOS (confirmation needed). It does appear on Linux (Ubuntu 14.04 LTS) and FreeBSD though.
(for info about the benchmark itself: http://benchmarksgame.alioth.debian.org/u32/performance.php?test=chameneosredux)
The text was updated successfully, but these errors were encountered: