Locking for resources shared between integration tests execution
Description
Problem/Justification
None
Impact
None
Activity
Show:
Bug Clerk October 30, 2024 at 8:28 PM
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
CalebReporter
Vladimir VinogradenkoLabels
Components
Priority
UndefinedMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created October 30, 2024 at 8:28 PM
Updated January 27, 2025 at 3:43 PM
When two integration tests run at the very same time and share an external resource (e.g., an S3 bucket for backups), they might and will conflict, resulting if false negatives.
My proposal: ask for IT to set up some distributed locking service and make these tests use it.
Proposed implementation: redis + https://redis-py.readthedocs.io/en/v4.1.2/lock.html