Bug 1226461

Summary:	Log files are opened incorrectly in Copr builds
Product:	[Community] Copr	Reporter:	Minh Ngo <nlminhtl>
Component:	frontend	Assignee:	Miroslav Suchý <msuchy>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	ignatenko, vgologuz
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-01 12:12:28 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 Minh Ngo 2015-05-29 21:12:24 UTC

Log files are opened incorrectly in Copr builds. For example, https://copr-be.cloud.fedoraproject.org/results/minh/fedora-ukraine/fedora-22-x86_64/leechcraft-azoth-0.6.75-10.fc22/build.log

Another one, that is "supposed" to be an archive can be read successfully https://copr-be.cloud.fedoraproject.org/results/minh/fedora-ukraine/fedora-22-x86_64/leechcraft-azoth-0.6.75-10.fc22/build.log.gz .

Probably, the first file is an archive and the file formats has been mixed up.

How reproducible:
Every time.

Steps to Reproduce:
1. Open firefox (or maybe another browser, but I have checked only for firefox)
2. Open the copr repository
3. open any build.log
  
Actual results:
Magic characters

Expected results:
build.log.gz

Comment 1 Igor Gnatenko 2015-05-29 21:13:56 UTC

I can confirm. log.gz is plaintext and log is archive.

Comment 2 Valentin Gologuzov 2015-06-01 12:12:28 UTC


*** This bug has been marked as a duplicate of bug 1223670 ***