Pin the other direction of the moved overflow boundary

The vendored range check moved in both directions, and only the direction that
starts refusing values had a test. Cover the quiet one: filling an int8 tensor with
127.5 used to be refused and now stores 127.

Test Plan:
Compiled the real header from before and after this change into the same probe and
ran both. Before: 127.5 into int8 and 255.5 into uint8 both report overflow, and 2^63
into int64 is accepted. After: the first two are accepted and 2^63 overflows. So the
boundary moved both ways, and the case added here fails against the previous header
rather than passing either way.

Placed in this file rather than the shared macro because the macro expands into eight
suites, and several of them reach the scalar through a path that rejects a fractional
value before any range check, where the case would not measure what it claims.

Author: pytorchbot

kernels/test/op_full_test.cpp

@@ -84,6 +84,19 @@ ET_FORALL_REALHBF16_TYPES(GENERATE_TEST)
 
 GENERATE_SCALAR_OVERFLOW_TESTS(OpFullOutTest)
 
+// The other half of the boundary change: 127.5 used to be refused for an int8
+// tensor and now truncates to 127.
+TEST_F(OpFullOutTest, CharTensorFractionalScalarTruncates) {
+  TensorFactory<ScalarType::Char> tf;
+  std::vector<int32_t> sizes = {2, 2};
+  std::vector<int64_t> sizes_int64_t(sizes.begin(), sizes.end());
+  auto aref = IntArrayRef(sizes_int64_t.data(), sizes_int64_t.size());
+  Tensor out = tf.zeros(sizes);
+
+  op_full_out(aref, 127.5, out);
+  EXPECT_TENSOR_EQ(out, tf.full(sizes, 127));
+}
+
 TEST_F(OpFullOutTest, HalfSupport) {
   TensorFactory<ScalarType::Half> tf;