Will n-body ever end? 1.64

Hi!
I have been running a 4 CPU n-body app for over two days now. It says that it has progressed 0.013%, which it has said since it started, and that it has 17414 days left to go. It is now 17 July 2017, the due date is 7/23/2017, and no other CPU task is being allowed to run. Will it ever end? Should I abort it? Should I just not run n-body apps? It is running on an AMD A10-7850K.

Hi again!
Since I have not gotten any advice as yet, and the deadline for the n-body app in question is only 36 hours away with 34008 days estimated left, I have aborted the job, aborted the other n-body jobs in the queue, and disallowed new n-body jobs. I have other Milkyway, non n-body, jobs which will miss their deadlines otherwise.

I've encountered this with n-body work units on occasion. Even though the estimated run time is 15-20 minutes, they sometimes tie up 4 CPUs for days. I abort them when I notice this and am inclined to not accept any more n-body work.

Anybody else experience this? Anyone from development listening?

I have been consistently experiencing the same problem. The 4 cpu n-body jobs were running fine up until a few months ago. I have also disallowed the n-body jobs.

They've always worked fine for me (on 4 completely different computers), although I may have started doing Milkyway after you experienced the problem. Maybe they fixed a bug?

I'm having this error too.

They start off with an estimated time of about 10 to 20 minutes, but when running, it quickly escalates to possibly 2-3 days.

Until this is resolved, i've now disabled N-Body from running on my 2 systems.