# I found the BUG case that is causing several correct HWs to be marked wrong

 14 3 If the very last line of the code is a comment, it will bug out the grader. Try it. Many of us had a last line print test statements commented out. The following example will yield "Incorrect. Your procedure did not return the correct value." on submit. Remove the last comment or add an empty line after the comment and it will be marked correct. example from HW3.3: def product_list(p): if len(p)<1: return 0 product=1 for e in p: product*=e return product #bug it  asked 13 Mar '12, 21:58 Joesph Hoffm... 994●4●9●13 accept rate: 100% As tmcguire pointed out, it's not just comments. A tab in the very last line will give the following response on submit: "Incorrect. Your submission did not terminate." I seems like the grade code may be missing a carriage return before appending code. I should also note that this didn't appear to be a problem with HW2 (I didn't test HW1) (13 Mar '12, 22:36) Joesph Hoffm... I also got the: "Incorrect. Your submission did not terminate." but I didn't know why. I'll be checking for tabs next time! (13 Mar '12, 22:39) Stewart-1 Yes, I got that! A real pain. (13 Mar '12, 22:54) Douglas Finn... happenend to me too, but I'm enjoying the course, I don't care for the gradings anymore... it's a Beta, hope to help udacians find the bugs so if they go on production, they will not have any bugs. :) (13 Mar '12, 23:45) Juan Cruz

 1 I too had commented lines at the end of my code on 3.7 and 3.8. Once removed and upon re-submitting, my solutions were graded correct. I'm a bit frustrated that this has happened, and am sad to have those graded wrong despite my many hours of checking and re-checking to ensure that they were correct. That said, I am glad to know that they were indeed correct, and am proud that I was able to get them right (even though they were graded wrong). answered 13 Mar '12, 22:05 Joshua Herzf... 847●5●29
 0 Just deleted the last line from homework exercises graded incorrect, and sure enough, now they are correct. Well, at least I will not spend the night by pointless debugging, thanks :-) answered 13 Mar '12, 22:07 Pavel Brabec 535●2●19
 0 Thanks for the post! I just uncommented my "print function()" test cases in 3.3, 3.5, and 3.8 and they came back correct. My solution for 3.3 was an exact match for the answer and marked incorrect. It was driving me crazy. Great course, don't mind putting in the time, but this grading was very deflating. answered 13 Mar '12, 22:18 Gregory Hugh... 14●1●3
 0 My 3.8 was graded incorrect and I had a comment at the end. Deleting the comment made my submission correct, but the grade will remain incorrect of course. answered 13 Mar '12, 22:32 David Hubert 198●1●11
 0 I had a left tab after the code and it was graded incorrect. If I remove the last empty line, it is graded as correct. answered 14 Mar '12, 00:03
 0 same thing here. i left single line comments at the end of my code which caused it to be graded incorrectly. thought i was going nuts with so many missed points. anyway, now i know. hopefully they will be corrected. answered 14 Mar '12, 01:07
Question text:

Markdown Basics

• *italic* or _italic_
• **bold** or __bold__
• image?![alt text](/path/img.jpg "Title")
• numbered list: 1. Foo 2. Bar
• to add a line break simply add two spaces to where you would like the new line to be.
• basic HTML tags are also supported

×15,273
×2,216
×1,718
×515
×323