Versions Compared

Old Version 4

changes.mady.by.user Kanupriya Pandey

Saved on

compared with

New Version Current

changes.mady.by.user Kanupriya Pandey

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

While tuning, by default log level is set to (more noisy) INFO level.  Once a given tune is compete, default log level is changed to WARN until end of the playback.  This is compromised to avoid log flooding during steady state.

Log Level

Macro to be used 

Description

ERROR

AAMPLOG_ERR

Log level to print "error" logs.  This is intended to print things that should never (logically) happen, severe problems worth raising tickets.
INFO

AAMPLOG_INFO

Log level to print debug / informative messages . INFO level logs are normally available while tuning, but disabled during playback.  This level logs are good for quick issue triage. 

Developer can force INFO level logging to always be printed using aamp.cfg "info"

TRACE

AAMPLOG_TRACE

Log level to print trace messages . Used for triaging/development purpose only. Never gets logged in production. Trace level logging can be enabled with configuration 
WARN

AAMPLOG_WARN

Log level to print warning messages and for any logs with critical information during regular flow. This log level will be printed always.  Warnings should be used for exceptions that player is able to handle robustly, or for environmental problems that don't reflect a client issue.

Process Notes

  • Please add label aamp_<sprint> (i.e. aamp_2302) to all the tickets being worked this sprint along with _aamp label.
  • Ensure Dev Owner and Dev Manager fields are populated.
  • Story points should  be updated in each ticket before raising review
  • To adhere to Sprint Release timing from Release Management team , we also need to merge all AAMP code fixes to stable2 before sprint end.
  • Development freeze will be done by end of 2nd week followed by a week for regression and validation time and a week for approval and merge to stable2.
  • For complex RDK tickets spanning multiple sprints, separate development branches can be requested.
  • Ticket should be moved from draft/under review to Code development . All bug tickets must capture a Root Cause Analysis.
  • Before requesting merge, please make sure that tests/utests are still working.  We strongly recommend adding new utests to improve code coverage and protect against regressions.
  • When ready with review , add label _AAMP_PENDING_REVIEW.  Make sure development test logs are added to the ticket and update the test scenarios clearly in the ticket.  This is particularly important - need to ensure that test guidance is clear for QA engineers.
  • Link the tickets correctly so that dependency can be picked for cherry picks.
  • Message #aamp-dev-private following convention there.