Skip to content
This repository has been archived by the owner on Oct 3, 2019. It is now read-only.

Ps/test with postgres too #23

Merged
merged 19 commits into from
Oct 18, 2018
Merged

Ps/test with postgres too #23

merged 19 commits into from
Oct 18, 2018

Conversation

Pastromhaug
Copy link
Contributor

@Pastromhaug Pastromhaug commented Oct 18, 2018

I removed tests with py35, djangomaster, and pypy3 to shrink the build matrix. Yes, these could be set up to have "allowed failures", but I still chose to remove them because Travis is throttling our builds which makes development on these libraries a pain. Includin extra builds is exacerbating that problem for very little benefit.

@@ -36,6 +35,5 @@ def test_available_for_processing_queryset(self):
tasks = SNSTask.objects.available_for_processing()
self.assertEquals(list(tasks), [
task_ready_past,
task_ready,
task_ready_now,
])
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test became broken when we switched from ordering by auto-id to ordering by visible_after. Mysql just happened to continue returning objects in the same order, but postgres is not.

@Pastromhaug Pastromhaug merged commit 3076a0e into master Oct 18, 2018
@Pastromhaug Pastromhaug deleted the ps/test-with-postgres-too branch October 18, 2018 20:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants