[asterisk-bugs] [JIRA] (ASTERISK-23244) [patch] testsuite: run-local fails to recognize modules

[Walter Doekes (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-23244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Walter Doekes updated ASTERISK-23244:
-------------------------------------

    Attachment: issueA23244_testsuite-run-locals-local-modules.patch

The menuselect bit was ok. The path fix wasn't. The Dependency class should not have to know anything about environment variables.

This updated patch may possibly fix or break other uses of .directories. That'll have to be looked over.
                
> [patch] testsuite: run-local fails to recognize modules
> -------------------------------------------------------
>
>                 Key: ASTERISK-23244
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23244
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Tests/testsuite
>    Affects Versions: SVN
>            Reporter: Corey Farrell
>         Attachments: issueA23244_testsuite-run-locals-local-modules.patch, testsuite-run-local.patch
>
>
> When lib/python/asterisk/test_config.py checks for an asterisk module, it fails to adjust path by $AST_TEST_ROOT.  This prevents asterisk modules from being found from within run-local.
> Additionally when 'run-local setup' configures asterisk, it does not enable dev-mode, TEST_FRAMEWORK or DONT_OPTIMIZE.  This change can be avoided by running configure yourself before run-local setup, but a large number of tests require TEST_FRAMEWORK.  Since run-local doesn't currently work, now seems like a good time to set reasonable defaults.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira