Review Request 144: Fixed job expiration under SFCB.
Roman Rakus
reviewboard at gallagherhome.com
Wed Apr 10 11:03:09 UTC 2013
> On April 10, 2013, 10:52 a.m., Roman Rakus wrote:
> > It's strange. Push it, but the best would be to ask SFCB upstream and possibly fix it.
>
> Jan Safranek wrote:
> It's documented behavior of CMPI, Pegasus is just less restrictive about this.
I see. Thanks for explanation.
- Roman
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard-openlmi.rhcloud.com/r/144/#review155
-----------------------------------------------------------
On April 8, 2013, 2:07 p.m., Jan Safranek wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://reviewboard-openlmi.rhcloud.com/r/144/
> -----------------------------------------------------------
>
> (Updated April 8, 2013, 2:07 p.m.)
>
>
> Review request for OpenLMI Developers.
>
>
> Repository: openlmi-storage
>
>
> Description
> -------
>
> Fixed job expiration under SFCB.
>
> SFCB does not allow logging in not-registered threads, therefore
> we must not log in job's Timer thread, i.e. Job._expire method.
>
> Jobs now expire silently, without any logging, I have bad feelings about it.
>
>
> Diffs
> -----
>
> src/openlmi/storage/JobManager.py e182c16e98a51d0fad3e032895d1103cf333ff64
>
> Diff: http://reviewboard-openlmi.rhcloud.com/r/144/diff/
>
>
> Testing
> -------
>
>
> Thanks,
>
> Jan Safranek
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/openlmi-devel/attachments/20130410/256b3087/attachment.html>
More information about the openlmi-devel
mailing list