-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
BMPServer in topotests should not pkill -f bmpserver
#17465
Labels
triage
Needs further investigation
Comments
pguibert6WIND
pushed a commit
to pguibert6WIND/frr
that referenced
this issue
Nov 20, 2024
Multiple BMP tests can run in parallel but, when one instance ends, it kills the BMP server process of all BMP tests. Save the PID of a BMP server and only kill it at the end. Link: FRRouting#17465 Fixes: 875511c ("topotests: add basic bmp collector") Signed-off-by: Louis Scalbert <[email protected]>
Merged
pguibert6WIND
pushed a commit
to pguibert6WIND/frr
that referenced
this issue
Nov 21, 2024
Multiple BMP tests can run in parallel but, when one instance ends, it kills the BMP server process of all BMP tests. Save the PID of a BMP server and only kill it at the end. Link: FRRouting#17465 Fixes: 875511c ("topotests: add basic bmp collector") Signed-off-by: Louis Scalbert <[email protected]>
pguibert6WIND
pushed a commit
to pguibert6WIND/frr
that referenced
this issue
Nov 25, 2024
Multiple BMP tests can run in parallel but, when one instance ends, it kills the BMP server process of all BMP tests. Save the PID of a BMP server and only kill it at the end. Link: FRRouting#17465 Fixes: 875511c ("topotests: add basic bmp collector") Signed-off-by: Louis Scalbert <[email protected]>
pguibert6WIND
pushed a commit
to pguibert6WIND/frr
that referenced
this issue
Nov 27, 2024
Multiple BMP tests can run in parallel but, when one instance ends, it kills the BMP server process of all BMP tests. Save the PID of a BMP server and only kill it at the end. Link: FRRouting#17465 Fixes: 875511c ("topotests: add basic bmp collector") Signed-off-by: Louis Scalbert <[email protected]>
pguibert6WIND
pushed a commit
to pguibert6WIND/frr
that referenced
this issue
Dec 2, 2024
Multiple BMP tests can run in parallel but, when one instance ends, it kills the BMP server process of all BMP tests. Save the PID of a BMP server and only kill it at the end. Link: FRRouting#17465 Fixes: 875511c ("topotests: add basic bmp collector") Signed-off-by: Louis Scalbert <[email protected]>
pguibert6WIND
pushed a commit
to pguibert6WIND/frr
that referenced
this issue
Dec 2, 2024
Multiple BMP tests can run in parallel but, when one instance ends, it kills the BMP server process of all BMP tests. Save the PID of a BMP server and only kill it at the end. Link: FRRouting#17465 Fixes: 875511c ("topotests: add basic bmp collector") Signed-off-by: Louis Scalbert <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The bmpServer shutdown does a
pkill -f bmpserver
which sayskill all processes with this name
. FRR topotests has multiple topotests that run at the same time, the topotests also currently has 2 tests which use the bmpserver. If they happen to be running at the same time and one test finishes before the other, the first test will kill the second tests bmpserver, thus causing it to not properly finish running.I repeatedly see bgp_bmp failing to run properly locally.
the failing test has this log bm1/bmpserver.log:
The exec.log has this at that time:
pkill is run at this time:
Version
How to reproduce
Run multiple bmp tests at the same time.
Expected behavior
one bmp test not to kill another bmp tests mojo
Actual behavior
mojo killed
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: