Skip to content

Commit

Permalink
Fix sync issue in mm_ping scenario leading to sporadic failures
Browse files Browse the repository at this point in the history
* Ensure the server outlives the client job as it is the owner of the
  barriers; otherwise the client might fail with `lock owner already
  finished`
* Note that this is in-line with the examples in our documentation on
  https://open.qa/docs/#_test_synchronization_and_locking_api
* See https://progress.opensuse.org/issues/156052#note-6 for details
  • Loading branch information
Martchus committed Feb 28, 2024
1 parent 86ff8ad commit bc3618d
Show file tree
Hide file tree
Showing 2 changed files with 22 additions and 0 deletions.
1 change: 1 addition & 0 deletions schedule/functional/mm_ping.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -8,3 +8,4 @@ schedule:
- installation/bootloader_start
- boot/boot_to_desktop
- network/setup_multimachine
- network/conclude_multimachine
21 changes: 21 additions & 0 deletions tests/network/conclude_multimachine.pm
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# SUSE's openQA tests
#
# Copyright SUSE LLC
# SPDX-License-Identifier: FSFAP

# Summary: Waits for parallel children to finish
# Maintainer: Marius Kittler <mkittler@suse.de>

use base 'basetest';
use strict;
use warnings;
use testapi;
use mmapi;

sub run {
my $hostname = get_required_var('HOSTNAME');
my $is_server = ($hostname =~ /server|master/);
wait_for_children if $is_server;
}

1;

0 comments on commit bc3618d

Please sign in to comment.