-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Regression due to Large output redirect refactor #2935
Comments
shpalani
added a commit
to agarwalishita/ebpf-for-windows
that referenced
this issue
Nov 20, 2024
agarwalishita
pushed a commit
to agarwalishita/ebpf-for-windows
that referenced
this issue
Nov 20, 2024
agarwalishita
pushed a commit
to agarwalishita/ebpf-for-windows
that referenced
this issue
Nov 20, 2024
agarwalishita
pushed a commit
to agarwalishita/ebpf-for-windows
that referenced
this issue
Nov 20, 2024
agarwalishita
pushed a commit
to agarwalishita/ebpf-for-windows
that referenced
this issue
Nov 21, 2024
Can you provide an estimated time for the regression fix? |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Large output redirect refactor rewrote catch_output_redirect.hpp and introduced the following regression that is breaking other repositories that use catch2.
https://github.com/microsoft/ebpf-for-windows/actions/runs/10746638325/job/29808074945 is an example of a github run where nothing changed except the dependabot-generated update of catch2. The tests previously passed and started failing with this update.
The gist is that the test runs two threads concurrently, both of which are using catch2, resulting in
Expected behavior
Tests should pass without regressions.
Reproduction steps
Steps to reproduce the bug. Take the microsoft/ebpf-for-windows repository.
Verify that the tests pass before the upgrade using
.\netebpfext_unit.exe sock_addr_invoke_concurrent1 -d yes
.Upgrade catch2 to latest.
Notice that catch2 hits internal assertions when running
.\netebpfext_unit.exe sock_addr_invoke_concurrent1 -d yes
Platform information:
Windows
The text was updated successfully, but these errors were encountered: