-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11-01-04 07:30 PM, Martin Pool wrote: > On 5 January 2011 02:29, Julian Edwards <[email protected]> wrote: >> Dear all >> >> I've seen this problem pop up in similar ways a few times now, where we're >> processing a bunch of data in a cron job (whether externally on the API, or >> internally) and it needs to do a batch of work, remember where it left off >> (whether reaching a batch limit or the live data is paused), and continue >> later. > > I think I something like this in a bug last December about the branch > scanner being killed when it runs out of memory. This apparently > doesn't happen very often and it wasn't totally clear to me or people > I asked what would happen to jobs (using the word loosely) that were > in progress at the moment it was killed.
You don't need to use the word loosely. They are represented by Jobs in the database table, and we store plenty of information about their state. If they fail, we mark them as failed, and we don't re-run them, because there's no reason to expect them to succeed. However, we cannot keep track of their status in a convenient way or restart failed jobs from a web page because the Product Strategist did not permit me to create a LEP for a Job Console, much less schedule its implementation. Aaron -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0kicYACgkQ0F+nu1YWqI1cdQCcC3qwckOcyXDMSs9/E9iAOmOM OAcAnjT7T3QlGOmnlKDJ8nxDJMkWrmUP =OPVH -----END PGP SIGNATURE----- _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
