Bug 1671647

Summary:	Anomalies in python-lint build job
Product:	[Community] GlusterFS	Reporter:	Sheetal Pamecha <spamecha>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	atumball, bugs, gluster-infra, nigelb
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-05 12:23:41 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 Sheetal Pamecha 2019-02-01 07:22:33 UTC

Description of problem:
In codebase the python script runs successfully and returns expected output but when running pylint on same script gives no-name-in-module error on jenkins

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 2019-02-01 08:06:11 UTC

Can you also paste in a link of where this is happening?

Comment 2 Amar Tumballi 2019-02-02 03:11:43 UTC

https://build.gluster.org/job/python-lint/

All the latest builds are passing, but if you go inside Console, and watch, there are some exceptions thrown.

Comment 3 Nigel Babu 2019-02-05 12:23:41 UTC

Ah, this was because we were trying to lint the virtualenv. I've fixed this up in this review and now it should fail correctly: https://review.gluster.org/#/c/build-jobs/+/22155/