Fuzz test & Fix callVariant

[zhuchcn]

Description

Update fuzz test history. 63'742 finished with all match.

I'm now running fuzz test on a F32 with 28 threads, but still it always fails after a while because OOM. The memory usage may get spiked for certain cases, and if multiple fuzz test case running simultaneously all need high memory, it may just fail. No plan to fix this so I'll just let it run and fail and update the history log along the way.

Closes #798

Checklist

• [X] This PR does NOT contain PHI or germline genetic data. A repo may need to be deleted if such data is uploaded. Disclosing PHI is a major problem.
• [X] This PR does NOT contain molecular files, compressed files, output files such as images (e.g. .png, .jpeg), .pdf, .RData, .xlsx, .doc, .ppt, or other non-plain-text files. To automatically exclude such files using a .gitignore file, see here for example.
• [X] I have read the code review guidelines and the code review best practice on GitHub check-list.
• [X] The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)]-[brief_description_of_branch].
• [X] I have added the major changes included in this pull request to the CHANGELOG.md under the next release version or unreleased, and updated the date.
• [X] All test cases passed locally.

[lydiayliu]

That's like single fuzztests requiring more than ~2-3G of memory? Wouldn't be unheard of, I've seen graph memory usage climb to 15G above baseline of loading reference files XD

[zhuchcn]

Yeah it does seem a little high. It could also be bruteForce that is using a lot of memory. bruteForoce is very slow for sure.