Subversion Repositories SmartDukaan

Last modification

• Rev 37410 – 44 d 5 h
• Author: amit

• Log message:

  Oppo warranty check: log to the logger instead of stdout
  
  Oppo has resolved nothing all day -- 83 ticks, the same 10 IMEIs recycled every
  time, zero "Serial Number ... Date" results -- and the log shows only a single
  line, 'Initiating webdriver...'. That is not silence: the class had 1 LOGGER call
  against 28 System.out.println, and the cron JVM's stdout is a socket inherited
  from the SSH session that launched it. Every diagnostic was going nowhere.
  
  So the code has been reporting what is wrong 28 times per attempt (which element
  was missing, the computed slider distance, success or failure per attempt, the
  parsed date) and all of it was discarded. Same pattern as the Vivo bug found
  today, where a five-word log line hid the real cause for weeks.
  
  Converted to LOGGER at info, with warn on the failure paths and error on the
  catch-all, which now includes the exception rather than a bare printStackTrace.
  The slider-widget timeout says which element it was waiting for, since that is
  the most likely failure point.
  
  No behaviour change -- only where the output goes.