[GH-ISSUE #111] issue with concurrent test runs #106

Closed
opened 2026-02-26 09:35:43 +03:00 by kerem · 2 comments
Owner

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.

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.
kerem 2026-02-26 09:35:43 +03:00
  • closed this issue
  • added the
    task
    label
Author
Owner

@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 ...

<!-- gh-comment-id:30651538 --> @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 ...
Author
Owner

@ThomasWaldmann commented on GitHub (Dec 27, 2013):

seems to work now \o/

<!-- gh-comment-id:31258367 --> @ThomasWaldmann commented on GitHub (Dec 27, 2013): seems to work now \o/
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nsupdate.info-nsupdate-info#106
No description provided.