Closed aescolar closed 1 year ago
CC @jori-nordic
@hermabe could you check it out? from a quick first pass, it seems like the problem is bt_eatt_reconfigure
getting called at the same time as the collision mitigation firing on the peripheral.
edit: the sequence of events that I can see is:
@jori-nordic has taken it
Describe the bug tests/bluetooth/bsim/host/att/eatt/tests_scripts/reconfigure.sh is too sensitive to the simulated device random seed. And fails/passes depending on either the random seeds or how many random draws the simulated device does.
Even though the test passes right now in CI, other changes in completely unrelated places in the code can and will cause the test to fail, causing very confused developers.
To Reproduce Steps to reproduce the behavior:
Apply this patch (this random seed causes a failure)
Expected behavior The testcase to not fail depending on unrelated random value changes.
Impact Failures in CI when changing unrelated code which use random numbers generation. I hit this issue when doing fully unrelated changes in another area of the code.
Logs and console output
Environment (please complete the following information):