I'm having problems compiling, as testIssue537CaseSensitiveHexEscapeFullFile fails. I'm using:
- Windows 11 64bit
- Netbeans 16
- JDK1.8
The error I get is:
org.json.junit.XMLTest.testIssue537CaseSensitiveHexEscapeFullFile -- Time elapsed: 0.056 s <<< FAILURE!
org.junit.ComparisonFailure: values should be equal expected:<... sensitive CRP, IL-1[?])> but was:<... sensitive CRP, IL-1[╬▓])>
at org.junit.Assert.assertEquals(Assert.java:117)
at org.json.junit.Util.compareActualVsExpectedObjects(Util.java:93)
at org.json.junit.Util.compareActualVsExpectedJsonObjects(Util.java:52)
at org.json.junit.Util.compareActualVsExpectedObjects(Util.java:68)
at org.json.junit.Util.compareActualVsExpectedJsonArrays(Util.java:33)
at org.json.junit.Util.compareActualVsExpectedObjects(Util.java:74)
at org.json.junit.Util.compareActualVsExpectedJsonObjects(Util.java:52)
at org.json.junit.Util.compareActualVsExpectedObjects(Util.java:68)
at org.json.junit.Util.compareActualVsExpectedJsonObjects(Util.java:52)
at org.json.junit.XMLTest.testIssue537CaseSensitiveHexEscapeFullFile(XMLTest.java:923)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:316)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
This is using the latest version of the code. I have also gone back to previous releases and tried compiling them, as follows:
20220924 - success, no issues
20230227 - fails, but at a different test
I'm just wondering whether it's something to do with the mod in JSONTokener.java line 60, where a recent change now explicitly uses UTF-8?
I'm having problems compiling, as testIssue537CaseSensitiveHexEscapeFullFile fails. I'm using:
The error I get is:
This is using the latest version of the code. I have also gone back to previous releases and tried compiling them, as follows:
20220924 - success, no issues
20230227 - fails, but at a different test
I'm just wondering whether it's something to do with the mod in JSONTokener.java line 60, where a recent change now explicitly uses UTF-8?