Interdependence of fuzz tests

[tavmem]

Note: the fuzz tests are in issue #468 If you run the content of fuzz-test 730 in k2.8, you get an error:

$ rlwrap -n ~/k2.8/k
K 2.8 2000-10-10 Copyright (C) 1993-2000 Kx Systems
Evaluation. Not for commercial use. 
\ for help. \\ to exit.
  `000!000-&1% 00 0
int error
`000!000-&1% 00 0
         ^
>

If you run the content of fuzz-test 730 in a fresh session of kona, you get seg fault:

$ rlwrap -n ~/kona/k
K Console - Enter \ for help
  `000!000-&1% 00 0
Segmentation fault (core dumped)
$

Use a fresh session of kona for each of these:

• if you run all fuzz tests, test 822 seg faults (test 730 does NOT seg fault)
• if you run only test 730, test 730 DOES seg fault
• if you run all tests beginning with test 62, test 730 does NOT set fault
• if you run only test 62 and 730, test 730 DOES seg fault
• if you run all tests beginning with test 63, test 730 DOES seg fault
• if you run only test 63 and 730, test 730 DOES seg fault
• if you run only tests 62, 63 and 730, test 730 DOES seg fault

There is some combination of tests, when run before test 730, causes test 730 not to seg fault. This interdependent result is a bug in kona. Looks like something is not getting reset in between each test.

[tavmem]

BTW: The inconsistent results seem to be caused by sometimes getting a wsfull condition. When wsfull, an error was thrown (and there was no seg fault). When no wsfull (yet), we got seg fault.