NestedLoopsProg: Wrong Return Value [Crosstesting]

[jvf]

Some combinations return the wrong exitcode (139 instead of 29).

Example Stack Trace:

java.lang.AssertionError: Exit code doesn't match: expected:<29> but was:<139>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at swp_compiler_ss13.crosstest.AbstractCrosstest.test(AbstractCrosstest.java:108)

Affected Test: NestedLoopProgTest, with the following module combinations: [3: LexerJb->ParserJb->SemanticAnalyserJb->IntermediateCodeGeneratorImpl->LLVMBackend] [7: LexerJb->ParserJb->SemanticAnalyser->IntermediateCodeGeneratorImpl->LLVMBackend] [11: LexerJb->ParserImpl->SemanticAnalyserJb->IntermediateCodeGeneratorImpl->LLVMBackend] [15: LexerJb->ParserImpl->SemanticAnalyser->IntermediateCodeGeneratorImpl->LLVMBackend] [19: LexerImpl->ParserJb->SemanticAnalyserJb->IntermediateCodeGeneratorImpl->LLVMBackend] [23: LexerImpl->ParserJb->SemanticAnalyser->IntermediateCodeGeneratorImpl->LLVMBackend] [27: LexerImpl->ParserImpl->SemanticAnalyserJb->IntermediateCodeGeneratorImpl->LLVMBackend] [31: LexerImpl->ParserImpl->SemanticAnalyser->IntermediateCodeGeneratorImpl->LLVMBackend]

Because some combinations do not terminate (see #46), a modified test setup is needed to reproduce the errors. The modified test setup can be found in the nestedloops branch. The results of the modified tests can be found here.

[fub-frank]

It's highly probable this duplicates #46

[jvf]

fixed by fix for #46