Repository navigation
ci(test): trial un-ignore of http-hardening module (#170) - #175
Merged
Merged
Conversation
…170) The built-in-server deadlock only ever manifested on the 2-vCPU GitHub runner; GitHub has since moved ubuntu-latest to 4 vCPU, and 400+ repro attempts (lab 1-core+load, real runner isolated, real runner 2-core recreated) never wedged. Remove the --ignore so the full suite runs the hardening file again, behind the --timeout=180 signal backstop (a wedge fails loudly in minutes, never a silent hang). If this stays green across several runs, the mitigation is retired and #170 closes as an environmental resolution. Signed-off-by: Andre van Zuydam <andrevanzuydam@gmail.com> Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-Authored-By: Tina4 <82961293+tina4stack@users.noreply.github.com>
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Trial to retire the #170 mitigation. Removes the --ignore of test_http_hardening_contract.py so the full suite runs it again (behind the --timeout signal backstop). Runners moved 2->4 vCPU, so the original deadlock trigger should be gone. If green across several re-runs, merge to retire the mitigation and close #170. Refs #170.
Signed-off-by: Andre van Zuydam andrevanzuydam@gmail.com