mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[PR #2663] [CLOSED] Add timeouts to some flaky tests #3219
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#3219
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?
📋 Pull Request Information
Original PR: https://github.com/hickory-dns/hickory-dns/pull/2663
Author: @divergentdave
Created: 12/9/2024
Status: ❌ Closed
Base:
main← Head:david/test-timeouts📝 Commits (1)
ddc579cAdd timeouts to some flaky tests📊 Changes
3 files changed (+60 additions, -27 deletions)
View changed files
📝
crates/proto/src/tests/udp.rs(+10 -9)📝
tests/integration-tests/tests/integration/name_server_pool_tests.rs(+38 -16)📝
tests/integration-tests/tests/integration/server_future_tests.rs(+12 -2)📄 Description
I noticed a couple recent test flakes where tests got stuck. This PR adds timeouts around some relevant futures, both in those tests and others with similar comments. This will at least fail quicker, and provide us some diagnostic information.
I had to change a few tests from
futures-executorto a current-thread Tokio runtime, since the former doesn't provide a timeout API, and the Tokiotimeout()function can't be called from outside of a Tokio runtime.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.