Skip to content

Pylint - Messages

Information Messages
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Parsing console log (workspace: '/Users/jenkins/workspace/CE_gpkit_PR_pylint/buildnode/macys')
Post processing issues on 'macys' with source code encoding 'UTF-8'
Creating SCM blamer to obtain author and commit information for affected files
-> Git blamer successfully created in working tree '/Users/jenkins/workspace/CE_gpkit_PR_pylint/buildnode/macys'
Resolving file names for all issues in workspace '/Users/jenkins/workspace/CE_gpkit_PR_pylint/buildnode/macys'
-> resolved paths in source directory (1 found, 0 not found)
Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
-> all issues already have a valid module name
Resolving package names (or namespaces) by parsing the affected files
-> all affected files already have a valid package name
No filter has been set, publishing all 1 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 1 issues (skipped 0 issues)
Invoking Git blamer to create author and commit information for 1 affected files
-> GIT_COMMIT env = 'e9c3db5c64654accdb05e41eeff2e4e63ad830d7'
-> Git commit ID = 'e9c3db5c64654accdb05e41eeff2e4e63ad830d7'
-> Git working tree = '/Users/jenkins/workspace/CE_gpkit_PR_pylint/buildnode/macys'
-> blamed authors of issues in 1 files
Blaming of authors took 3 seconds
Copying affected files to Jenkins' build folder '/var/lib/jenkins/jobs/CE_gpkit_PR_pylint/configurations/axis-buildnode/macys/builds/2446/files-with-issues'
-> 1 copied, 0 not in workspace, 0 not-found, 0 with I/O error
Repository miner is not configured, skipping repository mining
Reference build recorder is not configured
Obtaining reference build from same job (macys)
Using reference build 'CE_gpkit_PR_pylint/buildnode=macys #2437' to compute new, fixed, and outstanding issues
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Successfully parsed console log
-> found 1 issue (skipped 0 duplicates)
Parsing console log (workspace: '/jenkins/workspace/CE_gpkit_PR_pylint/buildnode/reynolds')
Post processing issues on 'reynolds' with source code encoding 'UTF-8'
Creating SCM blamer to obtain author and commit information for affected files
-> Git blamer successfully created in working tree '/jenkins/workspace/CE_gpkit_PR_pylint/buildnode/reynolds'
Resolving file names for all issues in workspace '/jenkins/workspace/CE_gpkit_PR_pylint/buildnode/reynolds'
-> resolved paths in source directory (1 found, 0 not found)
Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
-> all issues already have a valid module name
Resolving package names (or namespaces) by parsing the affected files
-> all affected files already have a valid package name
No filter has been set, publishing all 1 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 1 issues (skipped 0 issues)
Invoking Git blamer to create author and commit information for 1 affected files
-> GIT_COMMIT env = 'e9c3db5c64654accdb05e41eeff2e4e63ad830d7'
-> Git commit ID = 'e9c3db5c64654accdb05e41eeff2e4e63ad830d7'
-> Git working tree = '/jenkins/workspace/CE_gpkit_PR_pylint/buildnode/reynolds'
-> blamed authors of issues in 1 files
Blaming of authors took 2 seconds
Copying affected files to Jenkins' build folder '/var/lib/jenkins/jobs/CE_gpkit_PR_pylint/configurations/axis-buildnode/reynolds/builds/2446/files-with-issues'
-> 1 copied, 0 not in workspace, 0 not-found, 0 with I/O error
Repository miner is not configured, skipping repository mining
Reference build recorder is not configured
Obtaining reference build from same job (reynolds)
Using reference build 'CE_gpkit_PR_pylint/buildnode=reynolds #2445' to compute new, fixed, and outstanding issues
Reference build recorder is not configured
Obtaining reference build from same job (CE_gpkit_PR_pylint)
Using reference build 'CE_gpkit_PR_pylint #2437' to compute new, fixed, and outstanding issues
Issues delta (vs. reference build): outstanding: 0, new: 1, fixed: 0
Evaluating quality gates
-> FAILED - Total (any severity): 1 - Quality QualityGate: 1
-> Some quality gates have been missed: overall result is FAILED
Health report is disabled - skipping
Created analysis result for 1 issues (found 1 new issues, fixed 0 issues)
Attaching ResultAction with ID 'pylint' to build 'CE_gpkit_PR_pylint #2446'.