-
Bug
-
Resolution: Fixed
-
Minor
-
1.536 on OS X
From the Jenkins log of a non-productive instance I set up to test something:
Okt 25, 2013 11:26:43 AM hudson.WebAppMain$3 run INFO: Jenkins is fully up and running Okt 25, 2013 3:26:36 PM hudson.node_monitors.ResponseTimeMonitor$1 monitor WARNING: Making ffoooo offline because it’s not responding Okt 25, 2013 4:26:36 PM hudson.node_monitors.ResponseTimeMonitor$1 monitor WARNING: Making ffoooo offline because it’s not responding Okt 25, 2013 5:26:36 PM hudson.node_monitors.ResponseTimeMonitor$1 monitor WARNING: Making ffoooo offline because it’s not responding Okt 25, 2013 6:26:36 PM hudson.node_monitors.ResponseTimeMonitor$1 monitor WARNING: Making ffoooo offline because it’s not responding Okt 25, 2013 7:26:36 PM hudson.node_monitors.ResponseTimeMonitor$1 monitor WARNING: Making ffoooo offline because it’s not responding Okt 25, 2013 8:26:36 PM hudson.node_monitors.ResponseTimeMonitor$1 monitor WARNING: Making ffoooo offline because it’s not responding
The node in question is a dumb slave configured to connect via JNLP. It never was connected.
There should be no warnings about responsiveness for nodes that aren't connected.
- links to
[JENKINS-20272] Disconnected nodes don't need to be checked for reponse time
Workflow | Original: JNJira [ 151796 ] | New: JNJira + In-Review [ 178067 ] |
Assignee | New: Andrew Bayer [ abayer ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Remote Link | New: This issue links to "PR #2911 (Web Link)" [ 17001 ] |
Remote Link | New: This issue links to "CloudBees Internal OSS-2256 (Web Link)" [ 18373 ] |
Status | Original: In Review [ 10005 ] | New: In Progress [ 3 ] |
Assignee | Original: Andrew Bayer [ abayer ] | New: Oliver Gondža [ olivergondza ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |