Skip to content
This repository was archived by the owner on May 25, 2026. It is now read-only.

rev187

  • rev187
  • b201643

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    GPG key ID: 4AEE18F83AFDEB23
    Expired
    Verified
    Learn about vigilant mode

  • Choose a tag to compare

    View all tags
rev187: Use 60s interval for fast forward instead of 5s (#306)
  • rev187
  • b201643

  • Choose a tag to compare

    View all tags

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    GPG key ID: 4AEE18F83AFDEB23
    Expired
    Verified
    Learn about vigilant mode
@carlcsaposs-canonical carlcsaposs-canonical tagged this 23 Aug 18:39 
When wait_for_idle called in fast forward

wait_for_idle requires all units to be idle for 15 seconds in a row. Fast forward triggers update status events every 5 seconds, which causes the charm to execute (not idle). This causes wait_for_idle to stall on less powerful hardware (e.g. `large` self-hosted runners) and potentially slows down integration tests on more powerful hardware
Assets 2
Loading