summaryrefslogtreecommitdiffstats
path: root/test/async_test.py
Commit message (Collapse)AuthorAgeFilesLines
* Since the async status codes changes, there were two test cases for ↵Adrian Likins2009-01-281-4/+1
| | | | | | JOB_FINISHED, so got rid of one of them.
* Jobthing status codes cleanup.Krzysztof A. Adamski2008-06-061-2/+2
|
* Changing func/func/overlord/client.py:Client() to Overlord(). Client() stillAdrian Likins2008-03-281-10/+10
| | | | | | | works but will dive a deprecation warning. First pass at this refactor. I think just about everything has been updated, but some questions remain. Like if client.py needs a name change.
* All exceptions, async or otherwise, now come back as easily detectable ↵Michael DeHaan2008-01-291-0/+2
| | | | | | | signatures. Use utils.is_error(result) to determine if something is an error or isn't. Example scripts as well as func-inventory have been updated. See async_test.py for examples.
* Fixed async_test.py for all success/failure cases. Still need to tweak the ↵Michael DeHaan2008-01-241-2/+2
| | | | | | | code so that failure information for remote commands can be obtained (i.e. detals of the exceptions) without reading the remote logs. Async is weird because the information can't come back in faults (well, it can, but we don't want it to).
* Still working on async (pardon the debug output still), there's a long ways ↵Michael DeHaan2008-01-241-13/+34
| | | | | | | to go with the partial status reporting but it is getting better at actually doing the task, just a few kinks to work out in getting results reported correctly.
* Fixup to client noglobs invocation.Michael DeHaan2008-01-241-4/+4
|
* Working on async error handling, lots more to do...Michael DeHaan2008-01-231-1/+6
| | | | (If it hits no exceptions, returns are right, it's the partial error case to deal with next...)
* Double-barrel asynchronous calls. Async can now occur on both sides ↵Michael DeHaan2008-01-231-0/+3
| | | | | | | | simultaneously and still appears as if there is only one "global" job id to the API caller, the minion job id's are managed in the background, complete with partial result response as things come in which should be very nice for ajaxy implication. job_status API does still need to be modified to list active jobs as well as to store the job name.
* Moving the async and multiprocess stuff to top level so we can use themMichael DeHaan2008-01-231-1/+1
| | | | on the minion for minion side async funness.
* Jobthing is now functional (see async_test.py for example usage), we still needMichael DeHaan2008-01-151-0/+38
to delete jobs that have expired after a certain amount of time to avoid keeping too many results around in storage.