mirror of
https://github.com/nsupdate-info/nsupdate.info.git
synced 2026-04-25 16:45:55 +03:00
[GH-ISSUE #111] issue with concurrent test runs #106
Labels
No labels
bug
bug
duplicate
easy
easy
enhancement
enhancement
invalid
needs help
pull-request
scalability
security
task
urgent
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nsupdate.info-nsupdate-info#106
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ThomasWaldmann on GitHub (Dec 15, 2013).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/111
Originally assigned to: @ThomasWaldmann on GitHub.
quite some of our tests use the dns entry for "test.nsupdate.info" to do realistic tests (e.g. they update the IP there and then check via a lookup if the update worked).
problem: as all tests use same host, concurrent runs of the test suite cause conflicts / test failures because they all use the same dns entry.
with local py.test runs, this is usually no issue (they run sequentially by default), but on https://travis-ci.org/nsupdate-info/nsupdate.info are frequent test fails due to this.
@ThomasWaldmann commented on GitHub (Dec 16, 2013):
I have rewritten the tests to use a whole test zone instead of a test host and then use py.test fixture(s) to create random host names in there (and use fixture teardown to remove them again).
Locally, all tests work, but I currently see some strange test failures on travis-ci.org ...
@ThomasWaldmann commented on GitHub (Dec 27, 2013):
seems to work now \o/