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.

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

Unable to add header via error during TlsWrkStressDocker test on remote CI #2266

Open
EvgeniiMekhanik opened this issue Oct 18, 2024 · 1 comment · May be fixed by #1955
Open

Unable to add header via error during TlsWrkStressDocker test on remote CI #2266

EvgeniiMekhanik opened this issue Oct 18, 2024 · 1 comment · May be fixed by #1955
Assignees
Labels
Milestone

Comments

@EvgeniiMekhanik
Copy link
Contributor

EvgeniiMekhanik commented Oct 18, 2024

Describe the issue
t_stress.test_stress.TlsWrkStressDocker.test_concurrent_connections fails on remote CI with
ERROR: Unable to add via: header to msg [00000000e2b9b6a4]

To Reproduce
Steps to reproduce the behavior.

  • run t_stress.test_stress.TlsWrkStressDocker.test_concurrent_connections on remote CI
  • nonidempotent.test_nonidempotent.NotRetryNonIdempotentH1Test.test on CI with TCP segmentation

Version or commit hash
Tempesta FW 717cbd0 (current master also)
tempesta-test 9a4a485344767239f82bb9fb7b2e10b2d1e96648 (current master also)

@krizhanovsky krizhanovsky added this to the 0.8 - Beta milestone Oct 18, 2024
@EvgeniiMekhanik
Copy link
Contributor Author

EvgeniiMekhanik commented Oct 18, 2024

The problem occurs because after calling tfw_http_msg_del_hbh_hdrs hm->crlf->skb points on invalid skb. Should be fixed #1955

@EvgeniiMekhanik EvgeniiMekhanik linked a pull request Oct 18, 2024 that will close this issue
@krizhanovsky krizhanovsky modified the milestones: 0.8 - Beta, 0.9 - LA Oct 18, 2024
@const-t const-t linked a pull request Jan 23, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants