Project

General

Profile

action #55151

[functional][y] provide message explaining the failure in script_run

Added by ybonatakis almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
ybonatakis
Category:
Feature requests
Target version:
-
Start date:
2019-08-06
Due date:
2019-10-08
% Done:

0%

Estimated time:
5.00 h
Difficulty:

Description

Description

I'm as a openQA test developer would like to put message in script_run calls to provide more details about executed command.

Acceptance criteria

  1. Test developer can provide custom message for script_run
  2. Unit tests are added for the new functionality

History

#1 Updated by ybonatakis over 2 years ago

  • Due date set to 2019-09-10

#2 Updated by riafarov over 2 years ago

  • Subject changed from provide message explaining the failure in script_run to [functional][y] provide message explaining the failure in script_run
  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 5.00 h

#3 Updated by ybonatakis over 2 years ago

  • Status changed from Workable to Feedback

#4 Updated by riafarov over 2 years ago

  • Due date changed from 2019-09-10 to 2019-09-24

We have failing tests, let's try next sprint.

#5 Updated by ybonatakis over 2 years ago

  • Status changed from Feedback to In Progress

#6 Updated by riafarov over 2 years ago

  • Target version set to Milestone 28

#7 Updated by ybonatakis over 2 years ago

  • Status changed from In Progress to Feedback
  • Target version deleted (Milestone 28)

#8 Updated by JERiveraMoya over 2 years ago

  • Due date changed from 2019-09-24 to 2019-10-08

Still working on it. unit test failing. Moving to next sprint.

#9 Updated by JERiveraMoya over 2 years ago

ybonatakis, is it fine for you if we set this ticket to in-progress again? Now is missing the unit test coverage and it will take you some time.

#10 Updated by ybonatakis over 2 years ago

  • Status changed from Feedback to Resolved

#11 Updated by okurz over 2 years ago

  • Status changed from Resolved to Feedback

I had to revert the change in os-autoinst as it caused a very tricky regression: https://github.com/os-autoinst/os-autoinst/pull/1215

https://openqa.opensuse.org/tests/1045173#step/yast2_lan/9 is showing the problem where there is an additional echo with no argument that is overwriting the exit status of the previous command.
I applied the revert and fixed the workers with an immediate rollback: for i in aarch64 openqaworker1 openqaworker4; do echo $i && ssh root@$i "transactional-update rollback last && reboot"; done

#12 Updated by ybonatakis over 2 years ago

  • Status changed from Feedback to Resolved

#13 Updated by okurz over 2 years ago

The feature is deployed to o3 now so it could be used. I assume so far no script_run call is using this feature yet.

Also available in: Atom PDF