Everything is set up so you can start submitting ASST2.1, but there a couple things you need to do first, and a one thing you that is new this semester that you need to be aware of.
We’ve made some changes to the
/testbin/consoletest, which is the test you need to pass for ASST2.1. This change also required a
test161 change. So, you’ll need to:
- Merge the latest
OS/161upstream staff changes. There was a previous forum post explaining how to do this.
test161to version 1.3.1. There was also a previous forum post on how to update
Since there are changes to
consoletest, that test needs to be recompiled and installed. The easiest way to accomplish this is by running
bmake && bmake install from the top of your source directory.
Multipart Targets and Submitting ASST2.1
This year, ASST2 and ASST3 have been broken into multiple subtargets. For ASST2, you will be submitting ASST2.1 and ASST2.2. The testing and submission process is the same as ASST1. For ASST2.1, you can test using
test161 run asst2.1
and submit with
test161 submit asst2.1
The difference is, you will also receive a score for ASST2, which is made up of ASST2.1 and ASST2.2. The ASST2 metatarget is cumulative, and is what we use for the leaderboard.
For ASST2, the point breakdown is 20 points (ASST2.1) and 130 points (ASST2.2). When you submit ASST2.1, you will see an entry on test161.ops-class.org for both ASST2.1 (out of 20) and ASST2 (out of 150).
Good luck on ASST2!