Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Prevent corpus explosion in tiny projects #4672

Open
jonathanmetzman opened this issue Feb 6, 2025 · 0 comments
Open

Prevent corpus explosion in tiny projects #4672

jonathanmetzman opened this issue Feb 6, 2025 · 0 comments

Comments

@jonathanmetzman
Copy link
Collaborator

Tiny projects have been run too much since the batch switch. This is leading to corpus explosion which prevent pruning from running. A vicious cycle.
jonathanmetzman added a commit that referenced this issue Feb 6, 2025
@jonathanmetzman
Try to fix corpus explosion issue through scheduling: #4672
006e0df 
A bug in the scheduling code made smaller projects run way too often.
This has caused corpus explosions.

Fix this
jonathanmetzman added a commit that referenced this issue Feb 6, 2025
@jonathanmetzman
Try to fix corpus explosion issue through scheduling: #4672
1da6699 
A bug in the scheduling code made smaller projects run way too often.
This has caused corpus explosions.

Fix this
jonathanmetzman added a commit that referenced this issue Feb 6, 2025
@jonathanmetzman
Try to fix corpus explosion issue through scheduling: #4672 (#4673)
cd64679 
A bug in the scheduling code made smaller projects run way too often.
This has caused corpus explosions.

Fix this, don't accidentally ignore the project weight.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jonathanmetzman