wazo-confd integration tests sometimes fail during creation of extensions fixtures because of conflict on the extension number(for a given context).
The failing test in question is this instance:
Since the fixture in this example fails after randomly selecting the extension 1000 from a range of 2000 values(random.randint(1000, 1999)), a likely explanatory cause is missing cleanup logic on extensions created by other tests.
To reliably reproduce:
Zendesk Ticket IDs
None
Activity
Charles Langlois
April 15, 2025 at 6:21 PM
Does not solve the issue, but I spotted this instance of resources being created on setup but not cleaned up on teardown for FuncKey tests:
https://zuul.wazo.community/logs/352/local/35254047798641598666468cde3e970f/tox/integration/3-commands[1].log
wazo-confd integration tests sometimes fail during creation of extensions fixtures because of conflict on the extension number(for a given context).
The failing test in question is this instance:
Since the fixture in this example fails after randomly selecting the extension 1000 from a range of 2000 values(
random.randint(1000, 1999)), a likely explanatory cause is missing cleanup logic on extensions created by other tests.To reliably reproduce: