sorry for not being able to pinpoint the root cause, but every task you
queue has potentially zillions of variables to go though.
if a
def mytask(a, b):
return a+b
works, then the "culprit" of the scheduler not being able to finish the
task MAY (I'm pretty sure scheduler is ATM robustly tested, but I'm not
saying it doesn't have bugs for sure) be in the definition of the task.
We had users with problems filling stdout and stderr, but those were tasks
that even in the web2py shell did not complete.
Scheduler itself just launches a fresh shell with the usual environment,
executes the task, intercepts stdout and stderr and catches the results, so
testing in a web2py shell if it works usually makes sure that the task is
indeed "well coded".
On Friday, August 22, 2014 7:57:31 PM UTC+2, Stephen Weiss wrote:
>
>
> No, not doing any print statements, only logger.debug calls.
>
> The work that the running task does make Popen calls, not popen2 calls, if
> that's any help.
> However, I don't know how to go about checking if the stderr and/or stdout
> pipes are not filled.
>
> No, I didn't try running the task in a web2py shell, but I can work on
> that.
>
> Thanks!
>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
