The project is down because the old program failed, rather than because of a planned upgrade to a new program.

See message 55448

Not properly tested before deployment? Does the issue explain all the computation errors on the work units?

I don't get how a "program" can "fail" unless changes were made to the data being used by the project that caused it to "fail".

We (the general public) don't yet know exactly why it failed - only the project staff have access to the internal technical data.

But our working assumption is that it was designed to fail after one year of flawless service, due to a legal (licencing) constraint. Not a 'technical' failure that would be revealed by beta testing.

@Everyone eager for BOINC GPU workunits while this is being worked out: From what my machine has been running, I can recommend collatz, Einstein@Home, Moo Wrapper, PrimeGrid and Asteroids@Home. Between GPU Grid and those my Nvidia GPU always gets enough WUs. Collatz and Einstein even send WUs for my integrated Intel GPU.

---

Man, I don't understand the outrage. If you are annoyed so much, then just start to crunch another project. Y'all acting like you are paying money for a service that is temporarily unavailable for a week. You don't pay money to be able to crunch for GPUGRID, instead you are even receiving credits (GRC) for doing that.

If you are worried that you will lose so much GRC while the machine stands still, just crunch another project in the meantime.

There is a check that the app does not become too old. Building may not be a big hindrance, but doing the contrieved boinc deployment steps is. Project restarted.

Project restarted.

Cannot download tasks - "No tasks available ..."
how come?