mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[PR #2538] [MERGED] CI: Remove continue-on-error from steps #3123
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#3123
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/2538
Author: @divergentdave
Created: 10/29/2024
Status: ✅ Merged
Merged: 10/30/2024
Merged by: @djc
Base:
main← Head:david/ci-fix-clippy📝 Commits (2)
e6da9bcCI: Remove continue-on-error from steps47980b7Fix Clippy warning📊 Changes
2 files changed (+4 additions, -5 deletions)
View changed files
📝
.github/workflows/test.yml(+3 -3)📝
crates/proto/src/multicast/mdns_stream.rs(+1 -2)📄 Description
I noticed that there's currently a clippy warning on main, and CI is still passing because of a
continue-on-error: truesetting on the relevant step. This PR removes those lines, and addsif: success() || failure()to all subsequent steps. (This overrides the default ofif: success()) This achieves the same goal of not short-circuiting, and running as many checks as possible even if one fails, without accidentally ignoring earlier failures.The downside of this approach is that these later commands with
success() || failure()conditions will still run even if, for example, checking out the code or installing dependencies fails. This would create some extra error messages that would be confusing, but fixing that would require adding IDs to steps and writing more complicated conditions, and I don't think that would be worth it.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.