Actions
action #17628
closedtest-module doesn't appear if it gets triggered twice
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
-
Start date:
2017-03-09
Due date:
% Done:
0%
Estimated time:
Description
We discussed with this Santi, and it seems like a bug. So here it is.
Look at: https://openqa.suse.de/tests/806953
This is what it should display:
boot_to_desktop
patch_and_reboot
boot_to_desktop
consoletest_setup
...
but this is what gets displayed:
boot_to_desktop
patch_and_reboot
consoletest_setup
....
So, it somehow gets confused and it fails to display the boot_to_desktop testmodule twice.
You can also verify that the boot_to_desktop gets triggered twice from the logs:
11:57:13.4373 28699 ||| starting boot_to_desktop tests/boot/boot_to_desktop.pm at 2017-03-09 11:57:13
11:59:34.8097 28699 ||| starting boot_to_desktop tests/boot/boot_to_desktop.pm at 2017-03-09 11:59:34
Updated by okurz about 7 years ago
- Is duplicate of action #10514: [tools][sprint 201711.2] Prevent test module name clashes (problem on loading test module twice / multiple times / more than one) added
Actions