PLEASE NOTE: the upgrades to this server,, have not yet been completed.
Hopefully the changes will be completed on THURSDAY 8th December.
Web-based programs, such as csmarks, cssubmit, and the help fora, will be unavailable at some time on Thursday 8th.
  It's UWAweek 49


This forum is provided to promote discussion amongst students enrolled in Open Source Tools and Scripting.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

How do I ask a good question?
Displaying selected article
Showing 1 of 564 articles.
Currently 6 other people reading this forum.

 UWA week 22 (1st semester, study break) ↓
SVG not supported

Login to reply

12:59pm Thu 2nd Jun, Daniel S.

Hi all, I'm midway through marking assignment 2. While most submissions have been very good, there are a few that run poorly or not at all. If you receive a mark that you do not agree with ("it works fine on my machine!"), please do the following before requesting a re-mark: 1. Copy your code and the input text files (attached) into Docker container. 2. Take a screenshot showing the output of the following commands in the Docker container: ls pwd whoami bash style_cmp sample1.txt bash style_cmp sample1.txt sample2.txt Bear in mind that we are each marking 60+ assignments. We can make simple troubleshooting changes, but we do not have time to fix complicated or tricky problems. In terms of execution time, your code should really be able to run all the tests in under 20 seconds. I've seen plenty of good submissions run under 10 seconds. If you still think we got something wrong, or the automarker missed something, please include the screenshot from step 2 in your email. Clearly state which tests you think we got wrong and include screenshots of the correct output (again, this should all be done in the Docker container).

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  1:17AM Sep 14 2022
Privacy policy