-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Send Jobs to Orca #275
Merged
blerner
merged 75 commits into
CodeGrade:master
from
williams-jack:feature/send-jobs-to-orca
Aug 12, 2024
Merged
Feature: Send Jobs to Orca #275
blerner
merged 75 commits into
CodeGrade:master
from
williams-jack:feature/send-jobs-to-orca
Aug 12, 2024
Conversation
This file contains 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
Location of generate_grading_job_metadata_table moved
fix: empty starter zip should not be added feat: docker file for junit grader
Feature: Handle Orca Response
…sons Feature: Grading Job Generation
Additionally, response URL is added in the grading_job
williams-jack
commented
Jul 29, 2023
* Move route to collection since no specific grade. * Fetch grade and grader spearately -- they should not take in id. * Process boolean, int and null from string.
chore: add experimental warning to use orca label
Status column should only indicate if the grader is supposed to use Orca; everything else is saved to a file. Additionally, no build key needed given that grade id can be specified in the url.
* Pushing grader builds to Orca, as well as the ability to retrigger this flow. * Statuses from Orca for both individual grading jobs and image builds. * UI for build logs and job build logs.
blerner
reviewed
Aug 3, 2024
refactor: unnecessary setting of optparse banner
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.
Problem
Bottlenose should be able to send a job to Orca with the requisite execution information, priority, response information, and more. It should then be able to take in a response, verify it is coming from the correct source, and then record its output to be compared to its current output later on.
Solution