https://bz.apache.org/bugzilla/show_bug.cgi?id=70266

            Bug ID: 70266
           Summary: test_107_frame_lengths.py intermittently fails with
                    AH03490 "scoreboard is full" under CI load
           Product: Apache httpd-2
           Version: 2.5-HEAD
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Core
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Observed on GitHub Actions CI ("mod_http2 w/nghttp2 1.68.0" job) while running
an unrelated PR (apache/httpd#838):

test/modules/http2/test_107_frame_lengths.py::TestFrameLengths::test_h2_107_01[99]
failed with:

AH03490: scoreboard is full, not at MaxRequestWorkers. Increase ServerLimit.

This looks like resource exhaustion on the shared CI runner (too many httpd
child processes/connections accumulated over a long-running job) rather than a
code defect in frame-length handling itself; the test parametrizes over many
frame-length values ([99] suggests a late iteration), which may be hitting a
ServerLimit/MaxRequestWorkers ceiling that's fine for a single run but marginal
when the runner is already under load from other jobs/tests.

I searched git history for prior fixes referencing "scoreboard is full",
"AH03490", or ServerLimit tuning tied to this specific test and found nothing -
this does not appear to be a previously-documented flake, unlike the related
test_proxy_beacon.py issue I filed separately (bug 70265) which does have prior
history.

Reporting this for visibility/investigation. I have lower confidence than usual
that this indicates an actual code bug (vs. CI environment sizing) and have not
proposed any fix.

CI run for reference: apache/httpd PR #838, "mod_http2 w/nghttp2 1.68.0" job.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to