Bug 1309068

Summary:	[RFE] Allow users specify if task will run with tty enabled/disabled
Product:	[Retired] Restraint	Reporter:	Peter Hostačný <phostacn>
Component:	general	Assignee:	Bill Peck <bpeck>
Status:	CLOSED NEXTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	0.1.23	CC:	asavkov, bpeck, dcallagh, dkutalek, mjia, rjoost
Target Milestone:	0.1.25	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	restraint-0.1.25	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-24 12:56:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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