tree fe9ef54026d869f6950664f342b72c4f2fcfbcda
parent 668c75d3bfb4102e23b71323b2c9ddc26bcfdf2b
author Mike Kruskal <mkruskal@google.com> 1792452308 -0700
committer Copybara-Service <copybara-worker@google.com> 1792452509 -0700

Fix two JSON conformance tests that did not test what they claim.

FloatFieldMinNegativeValue sent and expected 3.402823e+38, a copy of the
FloatFieldMaxPositiveValue value, so the most negative finite float was
never exercised.  RepeatedFieldWrongElementTypeExpectingStringsGotMessage
sent ["1", 2, "3", {"a": 4}], where the 2 is already a wrong element type
(the case ExpectingStringsGotInt covers), so a parser that rejects ints
but accepts an object for a string field passed it for the wrong reason.
Use -3.402823e+38 and "2" respectively.

Failure lists match on the recorded failure message, so the one entry
that records a message for FloatFieldMinNegativeValue is updated to the
new value.

PiperOrigin-RevId: 1002674327