Submitting the Assignment

Files

You may not modify the signature of any methods or classes that we provide to you, but you're free to add helper methods.

You should make sure that all code you modify belongs to files with TODO(proj5) comments in them (e.g. don't add helper methods to DataBox). A full list of files that you may modify follows:

• src/main/java/edu/berkeley/cs186/database/recovery/ARIESRecoveryManager.java

Make sure that your code does not use any static (non-final) variables - this may cause odd behavior when running with maven vs. in your IDE (tests run through the IDE often run with a new instance of Java for each test, so the static variables get reset, but multiple tests per Java instance may be run when using maven, where static variables do not get reset).

Gradescope

Once all of your files are prepared in your repo you can submit to Gradescope through GitHub the same way you did for Project 0.

Submitting via upload

If your GitHub account has access to many repos, the Gradescope UI might time out while trying to load which repos you have available. If this is the case for you, you can submit your code directly using via upload. You can zip up your source code with python3 zip.py --assignment proj5 and submit that directly to the autograder.

Partners

Only one partner has to submit, but please make sure to add the other partner to the Gradescope submission. Slip minutes will be calculated individually. For example, if partner A has 10 slip minutes remaining and partner B has 20 slip minutes remaining and they submit 20 minutes late, partner A will be subject to the late penalty (1/3 off partner A's score) while partner B will have 0 remaining slip minutes and no late penalty applied to partner B's score.

Grading

• 60% of your grade will be made up of tests released to you (the tests that we provided in database.recovery.TestRecoveryManager).

• 40% of your grade will be made up of hidden, unreleased tests that we will run on your submission after the deadline.