fix: use is_nan

[vil02]

Description

First of all: all the best for the new year (according to Gregorian calendar)!

This PR changes the tests of the log to use is_nan. This change makes the tests more direct (i.e. we really want to check that log returns nan and not that rust panics probably due to comparing two nan's.).

@mihaubuhai - please have a look.

Checklist:

• I ran bellow commands using the latest version of rust nightly.
• I ran cargo clippy --all -- -D warnings just before my last commit and fixed any issue that was found.
• I ran cargo fmt just before my last commit.
• I ran cargo test just before my last commit and all tests passed.
• I checked COUNTRIBUTING.md and my code follows its guidelines.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (c522e60) 94.52% compared to head (a4caf8a) 94.53%.
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #641   +/-   ##
=======================================
  Coverage   94.52%   94.53%           
=======================================
  Files         282      282           
  Lines       22606    22606           
=======================================
+ Hits        21369    21371    +2     
+ Misses       1237     1235    -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mihaubuhai]

Yes :))) Didn't crossed my mind to think this way, thank you for looking into it!!!

[siriak]

Looks good, thanks!