Bug 1530111 - Logs unavailable if a regression run was aborted
Summary: Logs unavailable if a regression run was aborted
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-02 04:59 UTC by Nithya Balachandran
Modified: 2018-07-20 04:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-20 04:47:44 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Nithya Balachandran 2018-01-02 04:59:02 UTC
Description of problem:

The gluster logs are unavailable if a regression run was aborted.

Eg: https://build.gluster.org/job/centos6-regression/8171/console

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Nigel Babu 2018-07-20 04:47:44 UTC
I'm going to WONTFIX this. With the advent of per test timeouts, we will no longer abort the entire regression job. This is not a problem we have to spend a lot of time solving.


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