[pony-build] Context Failures

Max Laite mlaite at gmail.com
Sat Apr 10 14:52:03 PDT 2010


Base behavior confirmed, break out of virtualenvContext when a required dep
fails, pass failure result to server.

Need to figure out how to pass the reason for failure now.

Max

On Sat, Apr 10, 2010 at 5:29 PM, Max Laite <mlaite at gmail.com> wrote:

> Alright......
>
> Looking for some suggestions on how to go about doing this context failure
> stuff. Which we can assume should work for all context classes if we want it
> to and not just Virtualenv.
>
> What I though may work as an initial "hey, throw something together quick."
>
>
> Global variable some_variable default to false...
>
> In VirtualenvContext, inside the check for what ret status was returned by
> _run_command.... Set the global variable to true then break, this would
> break out of initialize and start doing the rest of stuff in do().
>
> Inside do() add a test after context.initialize() to see if some_variable
> is true and if it is skip over the run commands for loop.....then do the
> rest of the do() code......
>
> Then the problem arises of, how do we get a message to the pb server of pip
> dep install was the reason for failure. Can we just do this in the
> update_client_info func?
>
> Anyways, it does not act how I would expect....
>
>
>
> *Well after writing that all out and thinking about it while typing.....Do
> we just add in a test in do() that checks for global var state... then
> within that if block, if it passes, do all the cleanup and reporting right
> there?*
>
>
> Open to any and all suggestions as I think global var may be a bit messy
> way to go?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/pony-build/attachments/20100410/9fa9d78c/attachment.htm>


More information about the pony-build mailing list