Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Trivial
-
Resolution: Won't Fix
-
Affects Version/s: Current Version
-
Fix Version/s: None
-
Component/s: OIOIOI
-
Labels:None
Description
If the package has input generator, why don't we just generate tests if someone submits a solution to this problem? The tests can be cached for example for one day or something and then removed.
We have to be sure that generator is deterministic (generate tests twice during package processing), we can also keep md5 of tests if needed.
This should solve a lot of problems with memory.
We have to be sure that generator is deterministic (generate tests twice during package processing), we can also keep md5 of tests if needed.
This should solve a lot of problems with memory.
Activity
- All
- Comments
- History
- Activity
- Transitions
- Commits
Connect your code to JIRA
Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.
Git & Mercurial in the cloud
Collaborate across unlimited private code repositories.
Git behind the firewall
Manage and collaborate on Git repositories behind a firewall.
Browse and search code
Browse, search, and track source code repositories.
