Bug 624651 - [RFE] rhts-submit-log should be able to upload log to the sub-result
Summary: [RFE] rhts-submit-log should be able to upload log to the sub-result
Status: NEW
Alias: None
Product: Beaker
Classification: Community
Component: command line (Show other bugs)
(Show other bugs)
Version: 0.5
Hardware: All Linux
medium
medium vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact:
URL:
Whiteboard: SimpleHarness
Keywords: FutureFeature, Triaged
Depends On:
Blocks: 545868 524612
TreeView+ depends on / blocked
 
Reported: 2010-08-17 11:26 UTC by Jan Hutař
Modified: 2018-11-09 23:05 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Jan Hutař 2010-08-17 11:26:04 UTC
Description of problem:
I would like to be able to upload more than 1 log to the sub-result. Currently only rhts-report-result can attach (only one) file to the tests sub-result.


Additional info:
This might be extra option to rhts-submit-log where I can specify sub-test name, or changing rhts-report-result so it can upload multiple files.

Comment 1 Nick Coghlan 2012-10-17 04:37:53 UTC
Bulk reassignment of issues as Bill has moved to another team.

Comment 3 Vladimir Benes 2014-02-21 16:28:28 UTC
any update here? We use STH (Simple test harness) and it works with sub task massively. 
Uploading webm videos to each dogatil job would be more accurate to each sub-task instead to task itsel with $TEST recognition.

see:
https://beaker.engineering.redhat.com/jobs/593560

Comment 4 Bill Peck 2014-02-21 16:43:45 UTC
I'm slightly confused. You say your using an alternate harness but you still need rhts-submit-log?

Comment 5 Jan Tluka 2014-11-03 16:25:04 UTC
Hi, this would be very handy also in our network regression testing where I need to submit 2 and more log files.

+1 for this feature!

Comment 6 Dan Callaghan 2014-11-19 04:09:40 UTC
There is no nice way to squeeze this into rhts-report-result because its API unfortunately is based on four positional arguments, not options.

    Usage: rhts-report-result TESTNAME TESTRESULT LOGFILE [METRIC]

For alternative harnesses I recommend just using the lab controller HTTP API directly to upload as many files as you want, instead of going through the mess of the rhts-* shell layer.

I will have a look if restraint has a good way of allowing this.

Comment 7 Jan Tluka 2014-11-19 09:34:07 UTC
(In reply to Dan Callaghan from comment #6)
> There is no nice way to squeeze this into rhts-report-result because its API
> unfortunately is based on four positional arguments, not options.
> 
>     Usage: rhts-report-result TESTNAME TESTRESULT LOGFILE [METRIC]
> 
> For alternative harnesses I recommend just using the lab controller HTTP API
> directly to upload as many files as you want, instead of going through the
> mess of the rhts-* shell layer.
> 
> I will have a look if restraint has a good way of allowing this.

Where can I find documentation on Beaker HTTP API?

Comment 8 Dan Callaghan 2014-11-19 13:50:22 UTC
(In reply to Jan Tluka from comment #7)
> Where can I find documentation on Beaker HTTP API?

The bits for harnesses is here:

https://beaker-project.org/docs/alternative-harnesses/


Note You need to log in before you can comment on or make changes to this bug.