[asterisk-dev] [Code Review] Allow running test suite locally - initial work
Paul Belanger
reviewboard at asterisk.org
Wed Mar 6 13:39:19 CST 2013
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/2371/#review7999
-----------------------------------------------------------
/asterisk/trunk/lib/python/asterisk/asterisk.py
<https://reviewboard.asterisk.org/r/2371/#comment15315>
I don't think this actually will work as you expect. We initial did this at the beginning but started to see filename get truncated due to the length of patch names.
- Paul
On March 6, 2013, 12:42 p.m., Tzafrir Cohen wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2371/
> -----------------------------------------------------------
>
> (Updated March 6, 2013, 12:42 p.m.)
>
>
> Review request for Asterisk Developers.
>
>
> Summary
> -------
>
> Place anything needed for the test suite (except the actual sources of Asterisk) under the test suite directory.
>
> Fix parts in the python code. Add a wrapper script (run_local) for the required automation.
>
> Work is still needed on asttest (add a destdir option? Consolidate all the run-test scripts to run it through a common function?) but I'm not exactly sure how the information is passed to Lua.
>
>
> Diffs
> -----
>
> /asterisk/trunk/lib/python/asterisk/asterisk.py 3660
> /asterisk/trunk/run_local PRE-CREATION
>
> Diff: https://reviewboard.asterisk.org/r/2371/diff
>
>
> Testing
> -------
>
>
> Thanks,
>
> Tzafrir
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130306/571dcb1d/attachment.htm>
More information about the asterisk-dev
mailing list