Skip to content

Instantly share code, notes, and snippets.

@pavelsavara

pavelsavara/wasm-duty.md

Created July 12, 2024 10:19
Show Gist options
  • Save pavelsavara/749812a192b14d6082851fa708544440 to your computer and use it in GitHub Desktop.
Save pavelsavara/749812a192b14d6082851fa708544440 to your computer and use it in GitHub Desktop.
Download ZIP
WASM build duty rotation
Raw
wasm-duty.md

How to

Check new issues that need triage

  • untriaged wasm issues
  • Try to guess which release it belongs to. If you don't know assign current.
  • Assign them to specific team member. If you don't know, assign @lewing

Check Known Build Errors

  • Known Build Errors
  • if something is at 0 hits for more than a week, remove blocking-clean-ci
  • if something is above 5 hits per day
    • add blocking-clean-ci
    • add it to Current drama below
    • investigate yourself briefly
  • If it's timeout or deadlock, it may be not clear which specific test is causing it
    • create PR and add <XunitShowProgress>true</XunitShowProgress> so that we learn which test method is the cause
    • merge it if necessary
  • If it's MT and it happens in speficic unit test method or class, create PR and disable it with active issue.
    • Keep the Known Build Error open to confirm mitigation in next few days
    • mark it with diabled test because of [ActiveIssue]
  • Assign it to specific team member. If you don't know, assign yourself until end of your duty week
  • If it was already assigned, check with assigned person about status

Check for wasm failures which don't have issue yet

Other links

All wasm issues All wasm PRs

Current drama

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment