From e2f32c72a7a6ad3b1ba971416d86c6eca1096a36 Mon Sep 17 00:00:00 2001
From: Antoni Boucher <bouanto@zoho.com>
Date: Tue, 17 Oct 2023 07:57:56 -0400
Subject: [PATCH] Ignore failing test

This test only fails with non-native 128-bit integers, but it will also
fail with native 128-bit integers if we copy/paste it so that it's
executed twice. Interestingly, wrapping the test in a loop won't make it
fail.
So, it could be due to stack space or unwinding in release mode.
Also, the test only fails with -O2:
../cargo.sh rustc --bin test-rust -- -O

It doesn't fail with -O3.
---
 doc/tests.md         | 5 +++++
 failing-ui-tests.txt | 1 +
 2 files changed, 6 insertions(+)
 create mode 100644 doc/tests.md

diff --git a/doc/tests.md b/doc/tests.md
new file mode 100644
index 00000000000..3ac993bc2fd
--- /dev/null
+++ b/doc/tests.md
@@ -0,0 +1,5 @@
+# Tests
+
+## Show the rustc command for UI tests
+
+Add ` --test-args "--verbose"` to `./x.py test`.
diff --git a/failing-ui-tests.txt b/failing-ui-tests.txt
index ed56a11a170..771da581295 100644
--- a/failing-ui-tests.txt
+++ b/failing-ui-tests.txt
@@ -71,3 +71,4 @@ tests/ui/lto/all-crates.rs
 tests/ui/async-await/deep-futures-are-freeze.rs
 tests/ui/closures/capture-unsized-by-ref.rs
 tests/ui/generator/resume-after-return.rs
+tests/ui/macros/rfc-2011-nicer-assert-messages/all-expr-kinds.rs