Bug 1671647 - Anomalies in python-lint build job
Summary: Anomalies in python-lint build job
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-01 07:22 UTC by Sheetal Pamecha
Modified: 2019-02-05 12:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-05 12:23:41 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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/
Note You need to log in before you can comment on or make changes to this bug.