From b11d31ef23c5dfee6bfa54afbec47fc8b8bab7b1 Mon Sep 17 00:00:00 2001 From: Lars Wirzenius Date: Sun, 13 May 2018 15:30:23 +0300 Subject: Change: how controller stores persistent data Replace old State class with new FilePersistentState and TransactionalState classes. Use new Resource class instead of raw dicts. Use context managers for creating, updating resources, to avoid mistakes from accidentally not saving changes. Overall persistence should now be rather simpler. This should open up a possibility for changing the controller to insert more actions into the build graph, to trigger notifcations via the workers. --- yarns/900-implements.yarn | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'yarns/900-implements.yarn') diff --git a/yarns/900-implements.yarn b/yarns/900-implements.yarn index 8a7dff1..4086a2f 100644 --- a/yarns/900-implements.yarn +++ b/yarns/900-implements.yarn @@ -161,8 +161,7 @@ along with this program. If not, see . IMPLEMENTS THEN the list of builds is (.+) expected = set(json.loads(get_next_match())) print('expected', expected) - body = json.loads(vars['body']) + body = json.loads(vars['body'])['builds'] print('body', body) - actual = set(o['build_id'] for o in body['builds']) - print('actual', actual) - assertEqual(actual, expected) + builds = set(build['build_id'] for build in body) + assertEqual(builds, expected) -- cgit v1.2.1