[Testing:Plagiarism] Test remaining tokenizers #44
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the current behavior?
The C, Java, and Python tokenizers are currently broken and thus, no tests have been written for them. The primary source of the issue is a lack of installed dependencies on Submitty and outdated python versions listed in data.json.
What is the new behavior?
This PR fixes the afflicted tokenizers and adds tests for them. In addition, the installation of all dependencies necessary to run Lichen has been moved into the
install_lichen.shscript. A list of python dependencies has been made inrequirements.txt. After this PR, all of the supported tokenizers will be working and will be fully tested.Fixes Submitty/Submitty#6611
Fixes Submitty/Submitty#2134