Project

General

Profile

Actions

action #90332

open

have a reasonable timeout in lock API calls

Added by okurz over 3 years ago. Updated over 3 years ago.

Status:
Workable
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2021-03-19
Due date:
% Done:

0%

Estimated time:

Description

Motivation

As brought up in SUSE QE Tools workshop 2021-03-19 multi-machine tests, especially during test development, can waste a lot of developer time and hardware ressources because a wait on a barrier or mutex from https://github.com/os-autoinst/os-autoinst/blob/master/lockapi.pm never times out itself but only the complete openQA job is eventually aborted when it runs into MAX_JOB_TIME. Some time and user confusion could be saved with earlier timeouts

Acceptance criteria

  • AC1: waiting on mutex and barrier times out after a reasonable timeout
  • AC2: timeout can be configured when creating mutex and barrier

Suggestions

  • Research what are industry best practices for mutex and barriers
  • What would be a good selection for a "reasonable" timeout?
  • Add a timeout parameter with default value
  • Ensure it's covered in documentation
  • Inform about the change - can be implicit if your git commit message subjects are good enough :)
Actions

Also available in: Atom PDF