[
https://issues.apache.org/jira/browse/DAFFODIL-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson reopened DAFFODIL-2612:
-------------------------------------
While attempting to verify that the specified tests no longer fail with
LANG=en_US.US-ASCII received numerous "CLI test may be hanging, see
DAFFODIL-2751 for possible causes" messages.
After adding {{{}Thread.dumpStack(){}}}, per Steve L, to the
daffodil-cli/src/test/scala/org/apache/daffodil/cli/cliTest/Util.scala file the
following stack trace was output after each hanging message:
CLI test may be hanging, see DAFFODIL-2751 for possible causes
java.lang.Exception: Stack traceliTest.TestCLIDebugger 1315s
at java.base/java.lang.Thread.dumpStack(Thread.java:1380)
at org.apache.daffodil.cli.cliTest.Util$.runCLI(Util.scala:278)
at
org.apache.daffodil.cli.cliTest.TestCLIDebugger.test_CLI_Debugger_utf16_encoding(TestCLIDebugger.scala:734)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
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.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.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
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.junit.runner.JUnitCore.run(JUnitCore.java:137)
at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
at com.novocode.junit.JUnitTask.execute(JUnitTask.java:64)
at sbt.TestRunner.runTest$1(TestFramework.scala:153)
at sbt.TestRunner.run(TestFramework.scala:168)
at
sbt.TestFramework$$anon$3$$anonfun$$lessinit$greater$1.$anonfun$apply$1(TestFramework.scala:336)
at
sbt.TestFramework$.sbt$TestFramework$$withContextLoader(TestFramework.scala:296)
at
sbt.TestFramework$$anon$3$$anonfun$$lessinit$greater$1.apply(TestFramework.scala:336)
at
sbt.TestFramework$$anon$3$$anonfun$$lessinit$greater$1.apply(TestFramework.scala:336)
at sbt.TestFunction.apply(TestFramework.scala:348)
at sbt.Tests$.$anonfun$toTask$1(Tests.scala:436)
at sbt.std.Transform$$anon$3.$anonfun$apply$2(Transform.scala:47)
at sbt.std.Transform$$anon$4.work(Transform.scala:69)
at sbt.Execute.$anonfun$submit$2(Execute.scala:283)
at sbt.internal.util.ErrorHandling$.wideConvert(ErrorHandling.scala:24)
at sbt.Execute.work(Execute.scala:292)
at sbt.Execute.$anonfun$submit$1(Execute.scala:283)
at
sbt.ConcurrentRestrictions$$anon$4.$anonfun$submitValid$1(ConcurrentRestrictions.scala:265)
at sbt.CompletionService$$anon$2.call(CompletionService.scala:65)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
Steve believed and verified that "Newer versions of sbt essentially ignore LANG
and forces UTF-8 by default, so special options must be set to override it."
The Daffodil test machine is using sbt version 1.2.8.
> Integration tests fail with non UTF-8 LANG
> ------------------------------------------
>
> Key: DAFFODIL-2612
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2612
> Project: Daffodil
> Issue Type: Bug
> Components: CLI, Debugger
> Affects Versions: 3.2.1
> Reporter: Steve Lawrence
> Assignee: Steve Lawrence
> Priority: Minor
> Fix For: 3.5.1
>
>
> The CLI debugger sometimes outputs non-ascii characters when outputting a hex
> dump. Two integration tests checks for these non-ascii characters:
> *
> org.apache.daffodil.debugger.TestCLIdebugger.test_3258_CLI_Debugger_infodata
> *
> org.apache.daffodil.debugger.TestCLIdebugger.test_CLI_Debugger_utf16_encoding
> With LANG set to an ASCII encoding, those non-ascii characters are output as
> question marks, and the integration tests fail. To reproduce, run the
> following
> {code:java}
> $ export LANG=en_US.US-ASCII
> $ sbt IntegrationTest/test{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
