IPDSnelting issueshttps://git.scc.kit.edu/groups/IPDSnelting/-/issues2022-01-17T16:18:59+01:00https://git.scc.kit.edu/IPDSnelting/mjtest/-/issues/11Mjtest fails with Python 3.102022-01-17T16:18:59+01:00uxwluMjtest fails with Python 3.10@gp1285 mjtest crashes when run with Python 3.10. Example output:
```
ERROR:tests:At test case 'AocDay01.0.inputc'
Traceback (most recent call last):
File "/home/i_al_istannen/Programming/Uni/comprak-tools/mjtest/mjtest/test/tests.py",...@gp1285 mjtest crashes when run with Python 3.10. Example output:
```
ERROR:tests:At test case 'AocDay01.0.inputc'
Traceback (most recent call last):
File "/home/i_al_istannen/Programming/Uni/comprak-tools/mjtest/mjtest/test/tests.py", line 195, in _run_test_case
ret = test_case.run()
File "/home/i_al_istannen/Programming/Uni/comprak-tools/mjtest/mjtest/test/exec_tests.py", line 148, in run
out, err, rtcode = self.env.run_command("./a.out", timeout=timeout, input_bytes=input_bytes)
File "/home/i_al_istannen/Programming/Uni/comprak-tools/mjtest/mjtest/environment.py", line 190, in run_command
return execute([cmd] + list(args), timeout=timeout or self.timeout, input_bytes=input_bytes)
File "/home/i_al_istannen/Programming/Uni/comprak-tools/mjtest/mjtest/util/shell.py", line 123, in execute
(out, err, returncode) = exc.run()
File "/home/i_al_istannen/Programming/Uni/comprak-tools/mjtest/mjtest/util/shell.py", line 99, in run
self._run_process()
File "/home/i_al_istannen/Programming/Uni/comprak-tools/mjtest/mjtest/util/shell.py", line 80, in _run_process
self.proc = subprocess.Popen(self.cmd,
File "/usr/lib/python3.10/subprocess.py", line 966, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.10/subprocess.py", line 1843, in _execute_child
raise child_exception_type(err_msg)
subprocess.SubprocessError: Exception occurred in preexec_fn.
----------------------------------------
```https://git.scc.kit.edu/IPDSnelting/mjtest-tests/-/issues/3Semantic tests with incorrect syntax2021-11-21T00:40:33+01:00ucywgSemantic tests with incorrect syntaxThere are currently a number of semantic test that are already syntactically invalid (and should thus either be removed or moved to syntax):
- UseOfNullAsType4.invalid.mj
- UseOfNullAsType3.invalid.mj
- UseOfNullAsType2.invalid.mj
- Use...There are currently a number of semantic test that are already syntactically invalid (and should thus either be removed or moved to syntax):
- UseOfNullAsType4.invalid.mj
- UseOfNullAsType3.invalid.mj
- UseOfNullAsType2.invalid.mj
- UseOfNullAsType1.invalid.mj
- MainMethodWithNoArgs.invalid.mj
- MainMethodReturningInt.invalid.mj
- DeclarationInCondition.invalid.mjuxroguxroghttps://git.scc.kit.edu/IPDSnelting/mjtest-tests/-/issues/1File naming and hierarchy convention2021-11-05T23:20:20+01:00uxwluFile naming and hierarchy convention## Motivation
Looking at the existing PRs people seem to have different ideas for how to structure and name their test files. Unifying this would make the test suite a bit easier to read and understand.
## Technical constraints
The test...## Motivation
Looking at the existing PRs people seem to have different ideas for how to structure and name their test files. Unifying this would make the test suite a bit easier to read and understand.
## Technical constraints
The tests need to be in the subfolder for their corresponding phase, but the *names* of the file and *the subfolder* can apparently be chosen arbitrarily:
> The test cases must have unique names (in each mode folder) and can also be placed into sub folders
## Ideas
- Top-Level subfolders for valid/invalid programs
- Group tests by the subsystem they try to exploit (not really relevant for the lexer, but e.g. `parser/expressions` or `parser/declarations`, ...).
- Use `-` instead of camel case
- lowercase everything
- \<here be dragons or whatever else you suggest>https://git.scc.kit.edu/IPDSnelting/mjtest-tests/-/issues/2Developer access for all lab participants2021-10-28T16:20:41+02:00uxrogDeveloper access for all lab participantsuxroguxroghttps://git.scc.kit.edu/IPDSnelting/pflichtenheft/-/issues/2Rote Einfärbung der ID Von Funktionalen Anforderungen, Kriterien und ähnlichem2021-05-10T10:11:00+02:00uyxxqRote Einfärbung der ID Von Funktionalen Anforderungen, Kriterien und ähnlichemWenn der Titel eines Musskriteriums (das selbe bei eigentlich allen anderen Anforderungs- und Kriteriums-Typen) zu lange ist und der "Nicht implementiert" Text (oder ein vergleichbarer Text) angezeigt wird und nicht mehr in die Zeile pas...Wenn der Titel eines Musskriteriums (das selbe bei eigentlich allen anderen Anforderungs- und Kriteriums-Typen) zu lange ist und der "Nicht implementiert" Text (oder ein vergleichbarer Text) angezeigt wird und nicht mehr in die Zeile passt, also umbrochen wird, dann Färbt sich die ID der Anforderung Rot. Hier ist ein Beispiel:
![photo_2021-05-08_18-47-42](/uploads/f94b58b5ee7cd7ee5f175c047ba0a71a/photo_2021-05-08_18-47-42.jpg)https://git.scc.kit.edu/IPDSnelting/pflichtenheft/-/issues/1pflichtenheft package: hyperref springt nicht zum richtigen Label2019-12-20T10:21:24+01:00ubsxipflichtenheft package: hyperref springt nicht zum richtigen Labelhyperref springt nicht zum entsprechenden rdflabel sondern meistens weiter (oft bis zur `\section`)
Kann relativ einfach gefixt werden in dem eine `\phantomsection` vor den rdflabels hinzugefügt wird bei den entsprechenden Kommandos.
V...hyperref springt nicht zum entsprechenden rdflabel sondern meistens weiter (oft bis zur `\section`)
Kann relativ einfach gefixt werden in dem eine `\phantomsection` vor den rdflabels hinzugefügt wird bei den entsprechenden Kommandos.
Vergleiche https://tex.stackexchange.com/questions/41280/ieeeeqnarray-vs-hyperref-reference-jumps-to-the-beginning-of-the-sectionhttps://git.scc.kit.edu/IPDSnelting/mjtest/-/issues/9Add infinite loop tests for compile mode2019-01-28T16:15:17+01:00ufeblAdd infinite loop tests for compile modeTesting for infinite loops using the file ending `.inf.java` or `.inf.mj` is currently only done in the `compile-firm` and not in the `compile` mode.
Adding the `JavaInfiniteLoopTest` to the `compile` TestMode would allow us to test tha...Testing for infinite loops using the file ending `.inf.java` or `.inf.mj` is currently only done in the `compile-firm` and not in the `compile` mode.
Adding the `JavaInfiniteLoopTest` to the `compile` TestMode would allow us to test that our backend does keep infinite loops.https://git.scc.kit.edu/IPDSnelting/mjtest/-/issues/6`all` crasht bei `compile-only`2019-01-22T16:45:15+01:00uqddy`all` crasht bei `compile-only`uqddyuqddyhttps://git.scc.kit.edu/IPDSnelting/mjtest/-/issues/7In `big/` werden nur Tests ohne Eingabe ausgeführt2019-01-21T21:14:33+01:00uqddyIn `big/` werden nur Tests ohne Eingabe ausgeführtuqddyuqddyhttps://git.scc.kit.edu/IPDSnelting/molki/-/issues/1In `big/` werden nur Tests ohne Eingabe ausgeführt2019-01-21T18:51:18+01:00uqddyIn `big/` werden nur Tests ohne Eingabe ausgeführtuqddyuqddyhttps://git.scc.kit.edu/IPDSnelting/molki/-/issues/2`--all` crasht bei `compile`2019-01-21T18:50:38+01:00uqddy`--all` crasht bei `compile`uqddyuqddyhttps://git.scc.kit.edu/IPDSnelting/mjtest/-/issues/3MJTest ignores .java.out files2019-01-17T10:37:51+01:00uieknMJTest ignores .java.out filesAs the title implies, MJTest seems to ignore .java.out files. Instead it just tests whether the compiled program has the same output as the equivalent javac-compiled program.As the title implies, MJTest seems to ignore .java.out files. Instead it just tests whether the compiled program has the same output as the equivalent javac-compiled program.https://git.scc.kit.edu/IPDSnelting/mjtest/-/issues/5`exec` CLI argument should error or be removed2019-01-15T17:28:14+01:00qa2270`exec` CLI argument should error or be removedAs far as I understand, the `exec` mode is only there for internal reasons, but does not actually run any tests. It should therefore not be exposed to the user. If that is not possible, it should either report an error or fall back to wh...As far as I understand, the `exec` mode is only there for internal reasons, but does not actually run any tests. It should therefore not be exposed to the user. If that is not possible, it should either report an error or fall back to what the user presumably wanted, which is the `compile` mode.uqddyuqddyhttps://git.scc.kit.edu/IPDSnelting/mjtest/-/issues/4Provide for binary input files2018-12-18T08:41:51+01:00qa2270Provide for binary input filesThe current hot-fix for files with broken UTF-8 broke binary input files (i.e. input files which are not valid UTF-8). We should go over all the I/O and replace `str` with `bytes` and vice versa where necessary.The current hot-fix for files with broken UTF-8 broke binary input files (i.e. input files which are not valid UTF-8). We should go over all the I/O and replace `str` with `bytes` and vice versa where necessary.qa2270qa2270https://git.scc.kit.edu/IPDSnelting/mjtest/-/issues/1Support compile only tests2018-11-26T12:44:23+01:00uqddySupport compile only testsSupport tests that only need to compile, without being actually executable.Support tests that only need to compile, without being actually executable.https://git.scc.kit.edu/IPDSnelting/mjtest/-/issues/2Compile successful semantic tests with `--compile(-firm)`2018-11-26T12:44:23+01:00rp1446Compile successful semantic tests with `--compile(-firm)`Every test that passes the `--semantic` phase can also serve as a `--compile` or `--compile-firm` test where the runtime behavior is unspecified.
Specifically, these tests may have undefined behavior, so it doesn't even make sense to ru...Every test that passes the `--semantic` phase can also serve as a `--compile` or `--compile-firm` test where the runtime behavior is unspecified.
Specifically, these tests may have undefined behavior, so it doesn't even make sense to run the resulting executable. Yet, they might provoke crashes in the middle- or back-end, so it could still be worthwhile to test them.
Not sure what the resulting mode should be called; `compile` is already taken.
This subsumes #1, which proposes an entire new test category for this kind of testing. This proposal allows reuse of all semantic tests for this test category.