Automated Debugging

Dear Students,

You will find your score for Project 02 on your Personal Status page. We included feedback (download the .txt file) which reports the passed and failed tests (hidden tests have name `test_hidden_*`; unlike exercises, the hidden tests of projects will not be published).

The grading regulations were mentioned in the sheet (check it again when in doubt).

If you have any problems regarding your score, please contact us soon.

Dear Students,

You can find your points for Project 01 on your Personal Status page. We included feedback (download the .txt file) which reports the passed and failed tests. 

The points for Task 1 were given as follows:

- If you pass all public tests, you receive 50 points and pass the project.

- The 21 secret tests linearly map to the other 10 points, e.g., if you pass 15 tests, you receive seven points; if you pass eight tests, you receive 3.5 points.

 

The points for Task 2 were given based on how well you identified the faulty location for a subject (the higher the index in the rank, the better) and how unique you identified the location based on how many locations have the same suspiciousness and how many locations are ranked higher. For the index, we also considered the suspiciousness (if available); if two locations have the same suspicion, they have the same index. We calculated a score for 11 subjects (identification x uniqueness) and mapped the average for all subjects linearly to 40 points.

 

Contact us if there is something wrong with the reported errors so we will double-check them.

Dear Students,

We have uploaded a sample solution for Exercise 09, you can find it in the category Solutions under Information > Material. You can find your points for this exercise on your Personal Status page.

If you didn't receive 10 points (full mark), you will find a feedback (download the .txt file) which reports the errors. When in doubt, run your implementation on the test case included in the solution sheet (see the comments for the names of the test cases) and compare your outputs with the expected outputs produced by us. Contact us if there is something wrong in the reported errors so we will double check them.

Dear Students,

We have uploaded a sample solution for Exercise 08, you can find it in the category Solutions under Information > Material. You can find your points for this exercise on your Personal Status page.

If you didn't receive 10 points (full mark), you will find a feedback (download the .txt file) which reports the errors. When in doubt, run your implementation on the test case included in the solution sheet (see the comments for the names of the test cases) and compare your outputs with the expected outputs produced by us. Contact us if there is something wrong in the reported errors so we will double check them.

Dear Students,

We have uploaded a sample solution for Exercise 07, you can find it in the category Solutions under Information > Material. You can find your points for this exercise on your Personal Status page.

If you didn't receive 10 points (full mark), you will find a feedback (download the .txt file) which reports the errors. When in doubt, run your implementation on the test case included in the solution sheet (see the comments for the names of the test cases) and compare your outputs with the expected outputs produced by us. Contact us if there is something wrong in the reported errors so we will double check them.

Dear Students,

We have uploaded a sample solution for Exercise 06, you can find it in the category Solutions under Information > Material. You can find your points for this exercise on your Personal Status page.

If you didn't receive 10 points (full mark), you will find a feedback (download the .txt file) which reports the errors. When in doubt, run your implementation on the test case included in the solution sheet (see the comments for the names of the test cases) and compare your outputs with the expected outputs produced by us. Contact us if there is something wrong in the reported errors so we will double check them.

Dear Students,

We have published Project 02. You can find it under Information > Material.

The Zip file contains the required files for this exercise. The sheet.pdf includes the tasks you should try to solve.

We ask you to submit your solutions via the CMS on your Personal Status page. You have time until 21. March 2023 23:59 to upload your solutions as a Zip file. Note that we cannot evaluate delayed submissions.

Dear Students,

We have published Exercise 09. You can find it under Information > Material. Please read the chapter Repairing Code Automatically for this exercise.

The Zip file contains the required files for this exercise. The sheet.pdf includes the tasks you should try to solve.

We ask you to submit your solutions via the CMS on your Personal Status page. You have time until 17. Feb 2023 23:59 to upload your solutions as a Zip file. Note that we cannot evaluate delayed submissions.

Dear Students,

We have uploaded a sample solution for Exercise 02, you can find it in the category Solutions under Information > Material. You can find your points for this exercise on your Personal Status page.

 

The solution package includes:

1. A reference implementation (idb.py)

2. The test function (evaluate_02_func.py)

3. The testcases and some explanations on how we grade your code (testcases.py)

 

If you didn't receive 10 points (full mark), you will find a feedback (download the .txt file) which reports the errors. When in doubt, test your implementation against the test commands (provided in the solution package) and compare that with the expected outputs produced by the reference implementation. Contact us if there is something wrong in the reported errors so we will double check them.

Dear Students,

We have published Exercise 08. You can find it under Information > Material. Please read the chapter Debugging Performance Issues for this exercise.

The Zip file contains the required files for this exercise. The sheet.pdf includes the tasks you should try to solve.

We ask you to submit your solutions via the CMS on your Personal Status page. You have time until 03. Feb 2023 23:59 to upload your solutions as a Zip file. Note that we cannot evaluate delayed submissions.

Dear all,

At CISPA and Saarland University, we constantly aim to improve our courses – including "Automated Debugging". Now it's time for you to provide feedback! Please use the following links to provide your course assessment:

• Automated Debugging (lectures)
• Automated Debugging (exercises)

The evaluation is only open for a few days, so do not delay.

Looking forward to hearing from you,

Andreas + Marius + Paul

Dear Students,

We have published Exercise 07. You can find it under Information > Material. Please review and read the chapters Reducing Failure-Inducing Inputs and Generalizing Failure Circumstances for this exercise.

The Zip file contains the required files for this exercise. The sheet.pdf includes the tasks you should try to solve.

We ask you to submit your solutions via the CMS on your Personal Status page. You have time until 27. January 2023 23:59 to upload your solutions as a Zip file. Note that we cannot evaluate delayed submissions.

Happy new year, everyone! This is to remind you that on Tuesday, January 3 (= tomorrow)

• we do have an in-presence lecture (as usual at 16:15 at CISPA)
• but we also provide a remote alternative via Zoom

The latter might be particularly useful, as most other courses are online-only this week, and you may prefer attending from home.

To participate via Zoom, go to the course Web site

https://cms.cispa.saarland/debug_2223/

and choose Information -> Zoom from the top-level menu.

Looking forward to seeing you (in real life or virtual),

Andreas Zeller and the Automated Debugging Team

Dear Students,

Hello everyone,

Professor Zeller has fallen sick and will be absent for the week.

• Today's lecture will be given by Marius Smytzek instead. The topic will be Statistical Debugging. Professor Zeller is expected back next week; his topics will be Reducing Failure-Inducing Inputs and Isolating Failure-Inducing Changes, two applications of delta debugging.
• Professor Zeller's condition also has delayed finalizing the exercise sheets and project descriptions that we know you are waiting for. The good news is with Zeller's recovery, all of these should be in your hands by the end of this week. Stay tuned!

We sincerely apologize for the inconvenience. Stay healthy, stay safe, and see you soon!

The Automated Debugging Team – Andreas, Marius, and Paul

 

 

 

Dear Students,

We have published Exercise 02. You can find it under Information > Material. Please read the chapter on How Debuggers Work for this exercise.

The Zip file contains the required files for this exercise. The sheet.pdf includes the tasks you should try to solve.

We ask you to submit your solutions via the CMS on your Personal Status page. You have time until 30. November 2022 23:59 to upload your solutions as a Zip file. Note that we cannot evaluate delayed submissions.