Checklist for A2 Submissions

These instructions may change and get updated so check back and use the refresh button in your browser.
Some portions of the testing infrastructure that we make available to you and has been used successfully in the past seems to be failing and we will continue to work on it.

These are steps that are designed to help you successfully submit your assignment and to help you to see whether your code can be compiled and run successfully in the environment that we wil be using when we evaluate your assignment.

Many people/groups accidentally submit:

Code that doesn't compile in our test environment.
Code that doesn't work as it did on their system
Old code that was fixed but didn't make it into the submission
New code that breaks something

We hope that if you follow these steps will help (BUT NOT ENSURE) that you have a complete and proper submission.
You will not have an opportunity to resubmit after the deadline/slip days have passed or after the TAs find problems with the submission.

Only one member of the group should submit. You can submit as often as you like but be careful because ensuring that your submission compiles and runs properly can take some time (so leave a few hours). If different members of the same group submit, the last submission will be used.

Note that you now have 2 pages for the design document (instead of 1). This is to resolve the differences between the specification for the design document and the marking scheme.

     There will be two parts to the document.
     o The 1st part is to answer the 3 questions in the design section of the assignment.
     o The 2nd part is to describe the important aspects of
       the different system calls that are not covered by the 3 questions.
     
     The marking guide will remain unchanged. The TAs will read partt 1
     to get a flavour for your design and part 2 to fill in the remaining
     pieces. Then they will use the marking quideline as given.
     
     Think of it as:
       o The 3 questions are important things that they want to understand
         about your design (part 1).
       o The rest of the details that are missing will be filled in with
         part 2.

Double check the instructions for the assignment about what to submit!
Create and CHECK codeanswers2.pdf and place it in the directory where the cs350_submit command will be run.
Create and CHECK design2.pdf and place it in the directory where the cs350_submit command will be run.
Check in (commit) all changes that have been made that need to be included in the submission (by all group members).
Checkout or update all changes that are to be included in the submission (to get all changes from all group members)
Submit the assignment (!! this step must be done before moving to the next steps !!).
Do NOT remove the file os161kern.tgz (this will be needed for the later steps).
Ensure that the assignment builds correctly.
This step must be done by the same person (login id) as the person who submitted.
Note how to do this may need to change at some point
You can either use link on the assignments web page for a test compile or
use the script Test Submission Script ~cs350/bin/cs350_test_submit_a2.
NOTE: this Test submission script actually performs the test compile and the tests runs in the next step.
See the notes below about the Test Submission Script.
Ensure that the assignment runs as you expect it to.
This step must be done by the same person (login id) as the person who submitted.
Note how to do this may need to change at some point This is the part that hasn't worked as hoped so for now use:
the script Test submission script ~cs350/bin/cs350_test_submit_a2
If any of the last two steps fail. Make the necessary fixes and repeat from step 4 until done.

Notes on the ~cs350/bin/cs350_test_submit_a2 script.

This does not test forkbomb or any tests that require console input. These need to be tested separately outside of the control of a shell script.
It may need to be disabled at some point if the load on the machines becomes too heavy.
It assumes that you have $HOME/cs350-os161 in place and that your submission will be done using os161-1.11 in that directory.
Only run this on one of the fast Solaris machines. It takes way too long otherwise.
It started out as a set of instructions for you to follow but I eventually realized that in order to make sure the instructions were correct I needed to be able to execute them.
If things go wrong you will probably need to look at the script (it should be fairly readable) to see how it works.
It doesn't do any error checking.
You can look at the source code for the script. It should be reasonably easy to follow the steps.
If it doesn't work for you and you can't figure out why, you may want/need to just manually perform each step in the script to see where and why it is failing.