https://wiki.rdkcentral.com/display/CMF/CMF+Video+Sanity+Tests Describes all the video platform and tests we run on them

Re-triggering Tests

• • All re-triggers (if you expect them to vote to Gerrit/Github must be done from the component flow jenkins  job)
  • Watch the #smoke-test channel for failures, this has a link to the component flow and change for each failure
  • Only need to re-trigger on main dev branches
    • master
    • rdk-next
    • stable2
    • dev_sprint_23_1
      • note stuff may fail here, so we just re-trigger to make sure of status, if everything is failing ping aamp team
    • If something gone wrong with jobs/lab Alan should investigate

Current Known Failures

• • Flashing
    • sometimes we lose telnet connection to iolan during flashing phase of flows, just need to re-trigger
  • Turris
    • sometimes the serial port is unreliable, just need to re-trigger
  • RPI-B
    • Sometimes flashing fails with ccspwifiagent, hostapd
      • Re-trigger if it fails again, it needs investigation
        • May need a manual verification build or Keerthana help
    • 5Ghz wifi failures these seem to occur when rdkb is busy, either override the Verified vote or re-trigger
    • WPA supplicant restart failures on our wifi clients  – have to re-trigger
    • Web UI Issues probably need input from Keerthana
  • RPI-V
    • Seeing AAMP-CI tests failing on mediaclient, either re-trigger or override the verified vote
    • There is an occasional bug where sometimes everything passes on re-runs within the test but Verified vote still -1, I haven’t had time to track this down.
  • BRCM refboard LGI refapp
    • Occassionally the home screen check fails (video not playing on boot)
      • Just re-run or override the Platform Verified label
  • Amlogic/Realtek
    • Occasionally but rarely these fail, normally work on re-trigger
    • If it’s consistently failing need to look at state of device as it may have become corrupt during flashing, or if a build was flashed where IP was not getting assigned it will need manual recovery from me
    • if in a bad state just reserve the device from LOCKABLE_RESOURCES on Jenkins as we have 3 of each in the racks and I will sort when back

Device in a bad state

• • If a device gets into a bad state where it’s regularly failing simply reserve it from https://jenkins.cmf.code.rdkcentral.com/lockable-resources/

Nightly CI

• • Known issue with rpi-b 32 bit tdk builds
    • https://jira.rdkcentral.com/jira/browse/REFPLTB-2178
  • Someone please check daily to make sure nothing too bad has gone wrong in our nightly CI
  • https://jenkins.cmf.code.rdkcentral.com/view/NIGHTLY/job/nightly-branches-platform/
  • https://jenkins.cmf.code.rdkcentral.com/view/NIGHTLY/job/nightly-branches-dunfell/
  • https://jenkins.cmf.code.rdkcentral.com/view/COMMUNITY/

Disable Sanity on a Platform

• • If you want to disable sanity for a platform you need to turn off UPLOAD_IMAGES in the build jobs (DSL)
  • We normally don’t do this … last resort…

Disable Sanity on a Branch

• • If you want to disable sanity for a branch update the gerrit-vote-rdk-next jobs (in both community and internal dsl)
  • Only need to do this if some branch is causing lots of noise/taking resources in CI

Disable All Testing

• • https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-contribution-polling/
  • If you want to turn off all testing disable
  • Ask steve/simon to not run imports

Disable a Test or Tests

• • Each of the flow jobs has a TEST env var which is passed to hv16 job, this var can be edited to remove/add tests as required
  • If there is a regression which only affects one test then raise bug and remove test until it is resolved
  • Also if a test becomes problematic/unstable just remove and I will take care of later

Re-Run All Contribution Tests

• • To re-run all the tests for a contribution use the https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-contribution-flow/ job, you can get the test trigger from the console of corresponding gerrit-vote-rdk-next job, e.g.
  • https://jenkins.code.rdkcentral.com/job/gerrit-vote-rdk-next/53661/console
  • s3://rdkcm-community-artifacts/jobs/test_trigger2/build-component_65805
  • I rarely do this, normally we retriever the builds instead via a rebase or Gerrit trigger

Sharing builds from contributions, nightly etc

• • Use https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-download-url-generator/
  • If it’s a RPI build you need to redo the build first with BUILD_FOR_UBOOT set to 0 to have sd image format (not uboot)

Slack channels

• • #community-builds
  • #smoke-test
  • #nightly
  • #test-errors (good to monitor for failure patterns)