zig

commit 67ea47babdb891b7775b68683b232aa3c97ea012 (tree)
parent 663f0b399c5f4e2528a969fba6cd58d8f9784f5a
Author: Andrew Kelley <andrew@ziglang.org>
Date:   Fri,  6 Nov 2020 18:58:10 -0700

Revert "update runtime safety test case - unsigned-signed vector cast"

This reverts commit 663f0b399c5f4e2528a969fba6cd58d8f9784f5a.

The behavior appears to be inconsistent between running locally and on
the CI.

I suspect it could be based on what vector CPU features are available.

Diffstat:
M
test/runtime_safety.zig
 | 
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test/runtime_safety.zig b/test/runtime_safety.zig
@@ -89,7 +89,7 @@ pub fn addCases(cases: *tests.CompareOutputContext) void {
         \\const std = @import("std");
         \\const V = @import("std").meta.Vector;
         \\pub fn panic(message: []const u8, stack_trace: ?*@import("builtin").StackTrace) noreturn {
-        \\    if (std.mem.eql(u8, message, "integer cast truncated bits")) {
+        \\    if (std.mem.eql(u8, message, "attempt to cast negative value to unsigned integer")) {
         \\        std.process.exit(126); // good
         \\    }
         \\    std.process.exit(0); // test failed