Details
-
Bug
-
Resolution: Fixed
-
Minor
-
1.536 on OS X
Description
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.
Attachments
Issue Links
- links to
