WIP: Expose bug in FlyingEdges

There appears to be some conditions where compute pass 4 of FlyingEdges
does not properly update all of the values in InterpolationEdgeIds,
which can cause failures when you later try to use these ids for edge
interpolation.

The error is most noticible on debug builds of Windows, which initialize
the bytes in allocated arrays with 0xCD. This is a negative number in
2's complement, which is an obviously invalid id. You should be able to
replicate this behavior by editing FlyingEdges.h around line 170 to
initialize sharedState.InterpolationEdgeIds to a bunch of negative
numbers.

I think the problem is related to defining 2 or more isovalues. That
seems to be when the error occurs. Maybe arrays are not getting windowed
correctly.
37 jobs for !2036 with expose-flying-edges-bug in 207 minutes and 28 seconds (queued for 4 seconds)
latest merge request
Name Stage Failure
failed
test:ubuntu1804_clang8 Test
No job log
failed
test:ubuntu1804_gcc7 Test
No job log
failed
test:ubuntu1804_gcc9 Test The script exceeded the maximum execution time set for the job
No job log
failed
test:ubuntu1604_clang5 Test
No job log
failed
test:ubuntu1604_gcc48 Test
No job log
failed
test:rhel8 Test
No job log
failed
test:rhel8_test_centos7 Test
No job log
failed
test:centos7_gcc48 Test
No job log