Skip to content

Move h1_stream variables, to make thread usage more explicit #504

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.

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

Merged
merged 2 commits into from
Mar 10, 2025

Conversation

graebm
Copy link
Contributor

@graebm graebm commented Mar 8, 2025

Some cleanup before embarking on major plumbing...

While developing HTTP/1, we stumbled into the pattern of grouping variables under thread_data or synced_data, so it was more explicit how they should be accessed. But we never moved ALL the variables into the proper groups. We had a TODO about this. Now it is TODONE.

Also: Fix some flaky integration tests by accepting any "2xx" status-code, not just literal "200. I observed these tests failing when they sometimes got 202, instead of 200: h2_sm_acquire_stream & h2_sm_acquire_stream_multiple_connections. But I applied the same fix to any other test I found that strictly checked for 200.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@codecov-commenter
Copy link

codecov-commenter commented Mar 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.41%. Comparing base (84e8b41) to head (30e40ed).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #504      +/-   ##
==========================================
- Coverage   79.43%   79.41%   -0.02%     
==========================================
  Files          27       27              
  Lines       11617    11618       +1     
==========================================
- Hits         9228     9227       -1     
- Misses       2389     2391       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

I observed this when the following tests got 202, instead of literal 200: h2_sm_acquire_stream & h2_sm_acquire_stream_multiple_connections where

But applying the same fix in a few other tests that strictly check for "200"
@graebm graebm merged commit 23f62ee into main Mar 10, 2025
40 checks passed
@graebm graebm deleted the h1-thread-data branch March 10, 2025 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants