Each scheduler in tests needs its own connection registries.
This change only affects tests.
Change-Id: I2ad188cf5a72c46f7486c23ab653ff574123308b
Story: 2007192
These tests have a race where we rely on input events for unknown
projects in gerrit/github to populate our fake change and project
databases for those event sources. Before our dependent change is able
to be processed we need the parent change's event to be fully processed
and populate the database.
Without this we get database lookup errors which leads to us never
running jobs for the dependent change. When that happens we are unable
to properly assert the test conditions that the dependent change is
tested without the parent change.
Fix this by adding the parent change events, waiting for things to
settle, then adding the child change events.
Change-Id: I0641c44051d760c7be0f408f6b9b59222b8d4e90
To improve consistency and remove `self.sched` and
use `self.scheds.first.sched` in all tests.
This change only touches tests.
Change-Id: I0a8c3f8ad634d1d88f3c68a11e4d5587993f4a0d
Story: 2007192
As a preparation for scale-out-scheduler the scheduler in tests
were extracted in order to start multiple instances in a previous
change.
This change continues on by introducing a manager to create
additional scheduler instances and the ability to call certain
methods on some or all of those instances.
This change only touches tests.
Change-Id: Ia05a7221f19bad97de1176239c075b8fc9dab7e5
Story: 2007192
This change changes the dependency cycle error handling in order
to report the error to the user via the standard report mechanics.
Change-Id: I7cdbd9b7b48fd612b2887007b70acedd7a8e3113
The Gerrit change depends on a GitHub change which hasn't finished
propogating by the time the Gerrit event was received. Wait until
things have settled after the GitHub change is created.
Change-Id: I0750c9992f35cf52278cf24562802f7fc4ef0319