You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Run services and agents tests on CI only when related files change #7278
@suhaibmujahid Is running all tests for a changed component, and all service and agent tests when shared libraries change, enough for this issue? Or is more precise test selection expected?
@SanyaKor that's better than nothing, but ideally, if it isn't too complex, run the tests for the individual services, agents, or libs that changed.
An extra step would be to use the workspace dependency graph to also run tests for dependent packages. For example, if we change libs/phabricator-client, run the tests for libs/phabricator-proxy too, since it depends on it.
Activity
SanyaKor commentedon Oct 24, 2026
@suhaibmujahid Is running all tests for a changed component, and all service and agent tests when shared libraries change, enough for this issue? Or is more precise test selection expected?
suhaibmujahid commentedon Oct 26, 2026
@SanyaKor that's better than nothing, but ideally, if it isn't too complex, run the tests for the individual services, agents, or libs that changed.
An extra step would be to use the workspace dependency graph to also run tests for dependent packages. For example, if we change
libs/phabricator-client, run the tests forlibs/phabricator-proxytoo, since it depends on it.