google / google/oss-fuzz

[infra] Builds can use multiple pools for even more parallelism

Open
#8,873 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
12.6k
Forks
2.9k
Avg merge
2d 2h
Merged PRs (30d)
62

Description

We currently have a 400 concurrent build limit per private pool. We have 700 projects and 3 kinds of builds (fuzzing, coverage, introspector)
We can pretty easily use different pools for different kinds of build, this should make trial builds even faster!

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by locating the private-pool and build scheduling configuration, then determine how fuzzing, coverage, and introspector builds are assigned to pools. Done means the three build kinds can use separate pools and trial builds gain the intended parallelism.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.