it really doesn't change that much if it's bad code or good one, it's executed in web2py env that traps the exception. Unless you're overriding multiprocessing, datetime, etc etc etc (but this is just shooting really high with the fantasy) the whole scheduler would die (not just the task) but in that case you won't see it marked as failed and surely the times_failed counter wouldn't go up.
On Wednesday, February 3, 2016 at 5:51:35 PM UTC+1, Alex wrote: > > yeah, it's very unusual. This only happened a few times in the last 4 > years for me. But one of the reasons is that it only occurs when the task > raises an exception or runtime error. Usually my tasks run fine but a few > times I deployed "bad" code with failed tasks. And when the task fails it's > not so uncommon anymore. > > On Tuesday, February 2, 2016 at 9:31:39 PM UTC+1, Tim Richardson wrote: >> >> >>>> But of course it would be good to know what's going on here and why >>>> this can happen. >>>> >>> >> Must be unusual. I've been doing something similar for about two years >> over various web2py versions (on windows and ubuntu) and haven't seen this >> behaviour. >> > -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
