API issues sorting specs are not deterministic
Summary
As you can see on the following builds there are random failures after the merge of !6281 (merged)
This problem only manifest on CI , because on that environment we use MySQL which doesn't have millisecond precision so the created_at
attribute cannot be used for ordering in a deterministic way. To fix the failing we're going to create issues in different seconds.
INSERT INTO `issues` (`state`, `title`, `author_id`, `project_id`, `confidential`, `assignee_id`, `updated_at`, `iid`, `created_at`) VALUES ('opened', 'Eos fuga assumenda dolore adipisci nihil ad iure quidem.', 2, 1, 1, 3, '2016-09-12 10:52:15', 2, '2016-09-12 12:52:15')
/cc @DouweM can we consider change the API behaviour and instead of ordering by created_at
we can order by id
(we'll open an issue on that case). For the moment I want to fix the build