Hello,
I’ve had several instances during my developments where Cypress tests fail (on the test routes/integration/bluetooth/discover/BluetoothDiscover.js)
I feel like it’s random 
Should I create an issue?
https://github.com/GladysAssistant/Gladys/actions/runs/968893531
@cicoub13 Are you rebased on the latest version of master?
I changed the timeouts to stop having this kind of error on the CI, and since then I haven’t had any problems. I did this very recently, so you need to be up to date with master!
Hi @cicoub13, in the end my last changes didn’t do anything, I have the same problem as you, the Cypress tests around Bluetooth fail randomly.
I disabled the Bluetooth tests for now because it was blocking.
@AlexTrovato if you have any idea what’s going on! 
Hello, I suggest skipping the test while I look into this.
Yes that’s what I did in the meantime I investigated a bit, and what’s strange is that locally I have the impression that the Bluetooth integration is not really mocked when it runs locally (whereas I thought the integration was supposed to be mocked?) so it’s not easy to have the same conditions as the CI
I see in your PR prect-cli v3 that Cypress execution is under Node 12, not 14, this might be related.
Bluetooth is mocked, but with this predicate:
Bluetooth is not available by default on the execution machine
So only tests where Bluetooth « works » are mocked.
I will try to complete the tests to take into account cases where Bluetooth is available/works on the execution machine.
That’s something else, it’s a more recent PR!
We’ve had Bluetooth issues for a while on all PRs, even when it was on Node 12.
Ok! Indeed, locally on my machine, Bluetooth is functional. However, this doesn’t explain why it doesn’t work on the CI (where Bluetooth is not supposed to work).