Bug 1309068 - [RFE] Allow users specify if task will run with tty enabled/disabled
Summary: [RFE] Allow users specify if task will run with tty enabled/disabled
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Restraint
Classification: Retired
Component: general
Version: 0.1.23
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 0.1.25
Assignee: Bill Peck
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-16 18:40 UTC by Peter Hostačný
Modified: 2016-08-01 01:06 UTC (History)
6 users (show)

Fixed In Version: restraint-0.1.25
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-24 12:56:13 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1250080 0 low CLOSED [RFE] make ANSI color coding of output optional 2021-02-22 00:41:40 UTC

Internal Links: 1250080

Description Peter Hostačný 2016-02-16 18:40:06 UTC 
Description of problem:
It would be fine if users could specify which test will run with a tty enabled/disabled. Default value is debatable but an optional XML attribute at task should solve a lot of annoying problems (beakerlib outputs non-printable characters, yum/dnf produces long logs, etc..). On the other hand some tests could need a tty for their run (component like screen, etc..) - now it is workarounded by emulating a tty in the tests.

Default value can be discussed bellow.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
All tests run in emulated interactive terminal.

Expected results:
Possibility to run without a tty.

Additional info:
Comment 1 Bill Peck 2016-03-14 16:13:24 UTC 
http://gerrit.beaker-project.org/#/c/4731/
Comment 2 Bill Peck 2016-03-24 12:56:13 UTC 
Merged
Note You need to log in before you can comment on or make changes to this bug.