You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PR workflow will perform both general and HTTP/3-specific (at least seemingly) tests, which leads to longer wait times and more potential errors.
Expected Behavior
The HTTP/3 module http_v3_module has started to be listed as a pre-build in OpenResty 1.27.1.1, so I guess it's already considered production-ready, which means that we no longer need to differentiate between HTTP/3 turned on and turned off, and they should be merged together into one set of tests.
Current Behavior
The PR workflow will perform both general and HTTP/3-specific (at least seemingly) tests, which leads to longer wait times and more potential errors.
Expected Behavior
The HTTP/3 module
http_v3_module
has started to be listed as a pre-build in OpenResty 1.27.1.1, so I guess it's already considered production-ready, which means that we no longer need to differentiate between HTTP/3 turned on and turned off, and they should be merged together into one set of tests.ref: https://openresty.org/en/ann-1027001001.html
The apisix-runtime with the special patch that APISIX relies on has of course been updated to 1.27.1.1, so this should not be a problem.
Error Logs
No response
Steps to Reproduce
No needs
Environment
apisix version
): devuname -a
): Not releatedopenresty -V
ornginx -V
): Not releatedcurl http://127.0.0.1:9090/v1/server_info
): Not releatedluarocks --version
): Not releatedThe text was updated successfully, but these errors were encountered: