From 19a827f4803ee83586eec92337c435fb1179444e Mon Sep 17 00:00:00 2001
From: Colin Walters <walters@verbum.org>
Date: Wed, 23 Nov 2022 10:15:02 -0500
Subject: [PATCH] Test that CI successfully fails

I think a good pattern is to keep an open (draft) pull request
that *should* fail CI, and verify that it actually does.

It's surprisingly easily to e.g. have CI not actually test the
code.  In this case we have our "reverse dependency testing"
which patches the crate to use the local code, and that could
easily not work.
---
 src/imageproxy.rs | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/src/imageproxy.rs b/src/imageproxy.rs
index b780ef3..8cb8de7 100644
--- a/src/imageproxy.rs
+++ b/src/imageproxy.rs
@@ -380,6 +380,9 @@ impl ImageProxy {
         if fd.is_some() {
             return Err(anyhow!("Unexpected fd in finish_pipe reply"));
         }
+        if true {
+            anyhow::bail!("synthetic CI failure");
+        }
         Ok(r)
     }