Running the test suite on bullseye/sid generates the following warning:
,---
====================================================================== warnings summary ================================================================>
/usr/lib/python3/dist-packages/_pytest/junitxml.py:446
/usr/lib/python3/dist-packages/_pytest/junitxml.py:446: PytestDeprecationWarning: The 'junit_family' default value will change to 'xunit2' in pytest 6>
https://docs.pytest.org/en/stable/deprecations.html#junit-family-default-value-change-to-xunit2
for more information.
_issue_warning_captured(deprecated.JUNIT_XML_DEFAULT_FAMILY, config.hook, 2)
-- Docs: https://docs.pytest.org/en/stable/warnings.html
`---
Adding a config file and setting the junit family explicitly fixes
silences the warning.
Change-Id: I929b0c4630769ed263be0aeb8776a0233954e599
* simple POST via request function
* interface to store/retrieve/delete values from a list
at central redis
Change-Id: Ibae0f9b5c04dec3004b6d33e271866c722da3182
* final value is fetched from provisioning using pref value as id
* config: list of preferences needed to be loaded by kamailio
so we wont load unnecessary data into shared memory
Change-Id: I92e4bbfbe7ba55a06e79384aaa0d792556a39e22
The 'duration' variable is a string but it was written as int,
causing kamailio to write error lines
Change-Id: I2df1524d331e9b1d54bb0bdb84c06f4280e14fae
> ngcp/fp.lua:30:121: line is too long (126 > 120)
> ngcp/pprof.lua:28:121: line is too long (158 > 120)
Change-Id: Icf87f29049b2cc4ce29e7c1f5c78d9f2a53572c0
https://www.lua.org/manual/5.2/manual.html#8.3
> (Modules are not expected to set global variables anymore.)
EXPORT_ASSERT_TO_GLOBALS was just there for backwards compatibility
Change-Id: I11ac6d24746ca3c965b16ad523efff1f12ef0e9a
We are going to use both modules app_lua and app_lua_sr until we
solve the missing pieces on KEMI:
* KSR.pvx.xavp_get() returns a string like '<<xavp:%p>>' not a table like
sr.xavp.get()
* KEMI lacks of something like sr.xavp.get_keys() funtion
So, migrate everything that we can to KEMI and keep using sr approach
for just that two cases
- mocks/sr.lua: use same objects for same behaviour
Change-Id: I475ff8f820586cdc94c75bff7466238215e05673
The script collects all the callID from redis, then, one by one
it checks if callID exist in kamailo. At this time a call existing
in redis before may be destroyed in kamailio dlg.list. And so
script believe it's a stuck call.
Solution: collect CallID from REDIS and kamailio.dlg at the same
time, and compare afterwards.
Change-Id: I233a498e42bf5113b5b11ea688487e1840cd84a6
We also need to switch from python-xmlrunner to python3-pytest, as
the former is not present in Debian unstable/testing anymore (see
<https://bugs.debian.org/935688>), and does not provide python3
support in Debian buster anyway.
Change-Id: I8af9ead2755af2e24f5bedf53d8cd20c4ed63b85
Merge two file stanzas for Sipwise copyright, and use the one with the
canonical Sipwise copyright entity.
Change-Id: Iae16419b8d7d6af0555968e109a777b7951c121c
In the new version of LuaUnit assertTrue() and assertFalse()
functions are changed to striclty evaluate that the data is
True or false.
Where necessary the fuctions have been substituted in the test
with the new assertEvalToTrue() or assertNil().
Change-Id: I0c728323752a4458e93f516c7529670433c516d1
Sipwise Jenkins Builder
Victor Seva
Guillem Jover
Manuel Montecelo
Marco Capetta
Alexander Lutay