Challenge Overview
Project Overview
TopCoder is in an effort to upgrade the language versions used by TopCoder Competition Engine, which is used for Single Round Matches (SRMs) and Marathon Matches.
Before we move ahead to use the upgraded language versions for real problems, we have to evaluate that the upgrade does not raise any security issues and properly support the new features introduced by the new version.
The scope of this contest is to evaluate Python 2.6.6.
Contest Objective
The goal of this competition is to clearly identify the limitations of the upgrade to Python 2.6.6.
Things to test in the current competetion are:
- All new features introduced in the new versions (http://docs.python.org/dev/whatsnew/2.6.html) can be properly supported
- Old features in the current production are still supported, Python 2.4.3 is used in current production.
- No security issues raised by the upgrade. For security issues, I mean the potential way to used up memory, disk spaces, optential way to read other sensitive information, like other submitters solution etc.
How to Test
A small Marathon Match contest is live at http://community.topcoder.com/longcontest/?module=ViewActiveContests, You can write your code and test verify that.
How You Will Be Paid
IMPORTANT: The prize structure for this contest is different from normal. In ADDITION to the first and second place prizes, the following prizes are also offered:
- $50 for each missing language feature in SRM and MM
- $150 for each bug related to security. For example, viewing a competitors submission, reading the file system, taking control of the machine in some way.
- $300 for each bug that can can bring down the tester/compiler or the entire system.
- The PM and Copilot are the final arbiters of all prizes.
- Total prize purse for the contest is capped at $3000.
Contest Guidelines
The guidelines for this contest are given below:
- As issues are identified they need to be logged in JIRA.
- Issues must include clear description about the problem, sample solution to reproduce, and expected vs. actual results in order to be counted.
- First competitor to find an issue gets credit, duplicates will not be counted.
- Reviewers will accept, reject or mark the issues as duplicate.
- Please DO take a look at the reported bugs, duplicated bugs cost your work time and the reviewer's time.
Important Notice:
You must also be the first person to report the issue and submit it while submission phase is open. JIRA will allow you to file issues before and after the submission phase, but these will NOT be counted.
Bug Report Process
Bug Report Format
For each report of a limitation or bug, we need the following information:
- Clear description about the problem
- Sample Solution to reproduce
- Screen shots (if applicable)
- Expected results after the bug is fixed
- Current results, before the bug is fixed
Important Notice:
- If you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. Also, make sure your bug reports are reasonably general.
- If you submit the same bug that is seen in multiple screens, for instance, you will likely only get credit for the original bug report. The others will all be closed as duplicates.
Ticket Logging
You will log your tickets here: https://apps.topcoder.com/bugs/browse/TCADEBH and when creating a bug you MUST select the Python component. Bugs will not be counted if a selection is not made.
Scoring
The Scoring guidelines followed for the contest are given below:
- For scoring, the submitter with the most accepted bugs will win. The submitter with the second most accepted bugs will receive second place.
- For submitters who submit but don't take first or second, if they submit bugs that aren't covered in the first or second place submission, they will receive $5 for each unique bug reported up to a maximum of the 2nd place prize.
Important Notice:
If two submitters submit the same bug report, the submitter who submitted the report first into JIRA will get credit for the bug. The second submitter will not.
Tips
Some of the tips helpful for the contest are:
- Submitting what is obviously the same issue multiple times with small variations will only annoy the reviewer that has to sort through all the issues and will only count as one issue anyway. If it's less obvious if it is the same issue or not, use your best judgment and the reviewers will do the same.
- Put an eye on the issues being submitted by other members to minimize the time you may be spending on duplicate efforts. Knowing what has already been reported will allow you to better focus your time on finding yet undiscovered issues.
- Double check your steps to reproduce and test cases to make sure they are clear. Make sure your steps include creation of any necessary data.
Final Submission Guidelines
Submission Deliverables
You need report your issues in JIRA. Please submit a text file contains the bugs you reported to OR.
Final Submission
- For each member, the final submission should be uploaded to the Online Review Tool.
- You must not include any identifying information, such as your handle, in your submission. Your submission should be anonymous and you will be scored down in screening for not complying.