Handling ZeroDivisionError

[andrea-pasquale]

Closes #733

Checklist:

• Reviewers confirm new code works as expected.
• Tests are passing.
• Coverage does not decrease.
• Documentation is updated.
• Compatibility with Qibo modules (Please edit this section if the current pull request is not compatible with the following branches).
  • Qibo: master
  • Qibolab: main
  • Qibolab_platforms_qrc: main

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 97.22%. Comparing base (aad9f40) to head (4336866).
Report is 10 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #842      +/-   ##
==========================================
- Coverage   97.26%   97.22%   -0.04%     
==========================================
  Files         106      106              
  Lines        7855     7860       +5     
==========================================
+ Hits         7640     7642       +2     
- Misses        215      218       +3     

Flag	Coverage Δ
unittests	97.22% <50.00%> (-0.04%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
...aracterization/two_qubit_interaction/chsh/utils.py	82.35% <50.00%> (-17.65%)	⬇️

[GabrielePalazzo]

Should we log a message displaying that there was some kind of error in the division?

[andrea-pasquale]

Good point, I don't expect this to ever happen on hardware. Only with the dummy it happens.