Jenkins is going to shut down

Pylint - Messages

Information Messages
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Parsing console log (workspace: '/Users/jenkins/workspace/CE_gpfit_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_gpfit_PR_pylint/buildnode/macys'
Resolving file names for all issues in source directory '/Users/jenkins/workspace/CE_gpfit_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)
-> resolved module names for 2 issues
Resolving package names (or namespaces) by parsing the affected files
-> resolved package names of 1 affected files
No filter has been set, publishing all 2 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 2 issues (skipped 0 issues)
Invoking Git blamer to create author and commit information for 1 affected files
-> GIT_COMMIT env = '3d3f9588a59f5e59faf32df9fb7fc6412d910e58'
-> Git commit ID = '3d3f9588a59f5e59faf32df9fb7fc6412d910e58'
-> Git working tree = '/Users/jenkins/workspace/CE_gpfit_PR_pylint/buildnode/macys'
-> blamed authors of issues in 1 files
Blaming of authors took 1 seconds
Copying affected files to Jenkins' build folder '/var/lib/jenkins/jobs/CE_gpfit_PR_pylint/configurations/axis-buildnode/macys/builds/168/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_gpfit_PR_pylint/buildnode=macys #165' to compute new, fixed, and outstanding issues
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Successfully parsed console log
-> found 2 issues (skipped 0 duplicates)
Parsing console log (workspace: '/jenkins/workspace/CE_gpfit_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_gpfit_PR_pylint/buildnode/reynolds'
Resolving file names for all issues in source directory '/jenkins/workspace/CE_gpfit_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)
-> resolved module names for 2 issues
Resolving package names (or namespaces) by parsing the affected files
-> resolved package names of 1 affected files
No filter has been set, publishing all 2 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 2 issues (skipped 0 issues)
Invoking Git blamer to create author and commit information for 1 affected files
-> GIT_COMMIT env = '3d3f9588a59f5e59faf32df9fb7fc6412d910e58'
-> Git commit ID = '3d3f9588a59f5e59faf32df9fb7fc6412d910e58'
-> Git working tree = '/jenkins/workspace/CE_gpfit_PR_pylint/buildnode/reynolds'
-> blamed authors of issues in 1 files
Blaming of authors took 1 seconds
Copying affected files to Jenkins' build folder '/var/lib/jenkins/jobs/CE_gpfit_PR_pylint/configurations/axis-buildnode/reynolds/builds/168/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_gpfit_PR_pylint/buildnode=reynolds #165' to compute new, fixed, and outstanding issues
Reference build recorder is not configured
Obtaining reference build from same job (CE_gpfit_PR_pylint)
Using reference build 'CE_gpfit_PR_pylint #165' to compute new, fixed, and outstanding issues
Issues delta (vs. reference build): outstanding: 0, new: 2, fixed: 0
Evaluating quality gates
-> FAILED - Total (any severity): 2 - Quality QualityGate: 1
-> Some quality gates have been missed: overall result is FAILED
Health report is disabled - skipping
Created analysis result for 2 issues (found 2 new issues, fixed 0 issues)
Attaching ResultAction with ID 'pylint' to build 'CE_gpfit_PR_pylint #168'.