[Refactor:Developer] Replace submitty_count#56
Draft
dagemcn wants to merge 3 commits into
Draft
Conversation
dagemcn
changed the title
dagemcn
changed the title
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
1 participant
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.
Please check if the PR fulfills these requirements:
What is the current behavior?
Fixes Submitty Issue#11784 - This one of the companion PRs to Submitty PR#12609.
The tutorial courses 04 - Python Static Analysis, 06 - Loop Types, and 07 - Loop Depth all use
submitty_countin their autograding configs. This command is being deprecated, so we should update it.What is the new behavior?
submitty_counthas been removed from04 - Python Static Analysisand06 - Loop Typesand replaced withsubmitty_count_tsin preparation for deprecation. For07 - Loop Depth, there was no equivalent functionality present insubmitty_count_tsso the testcase now just returns full credit no matter what is submitted.Other information?
This specific PR is not a breaking change. However, the other PRs accompanying this one are breaking PRs.
TODO: vagrant up with all companion PRs to test