On May 2 test_030_run_sdntrace_for_stored_flows ended up failing due to a HTTP 409 The EVC already exists. The test suite TestE2ESDNTrace is still a bit flaky when it comes to resource creation. Originally it was reusing one EVC which is fine, and speed things up, overtime newer test cases started to create EVCs too, and this test suite isn't running a clean up on every test case. So, this really needs a overall refactoring to keep it coherent to avoid test flakiness.
cc'ing @gretelliz, this is low priority compared to the tasks your working on, I'll assign it to you since you're working with sdntrace_cp. If this can also be done then we can ship it too, otherwise it'll be in a next iteration, OK? Since you'll be already updating e2e tests anyway it's good to keep this on your radar.
On May 2
test_030_run_sdntrace_for_stored_flows
ended up failing due to a HTTP 409The EVC already exists.
The test suiteTestE2ESDNTrace
is still a bit flaky when it comes to resource creation. Originally it was reusing one EVC which is fine, and speed things up, overtime newer test cases started to create EVCs too, and this test suite isn't running a clean up on every test case. So, this really needs a overall refactoring to keep it coherent to avoid test flakiness.cc'ing @gretelliz, this is low priority compared to the tasks your working on, I'll assign it to you since you're working with
sdntrace_cp
. If this can also be done then we can ship it too, otherwise it'll be in a next iteration, OK? Since you'll be already updating e2e tests anyway it's good to keep this on your radar.