framecpp_verify bug
I was running framecpp_verify on a bunch of old GEO files:
vsmarchive# framecpp_verify --verbose /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10
That status says:
One or more pieces of the filename meta data is invalid.
which I'd thought might be because the file was renamed to change it's frametype from RDS_C01_L3 to G1_RDS_C01_L3 (but I tried on a GEO file that hadn't been renamed /archive/frames/S5/L3/GEO/G-RDS_C01_L3-8343/G-RDS_C01_L3-834361320-60.gwf and it also returns status 10, so I guess not?). But it gets weird if I just run that same command on that same file over and over again:
vsmarchive# while /bin/true^Jdo^Jif framecpp_verify --verbose /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf^Jthen^Jbreak^Jfi^Jdone /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 10 /archive/frames/A5/L3/GEO/G-G1_RDS_C01_L3-9150/G-G1_RDS_C01_L3-915040380-60.gwf 0 vsmarchive#
The number of iterations needed to make it exit status 0 is highly variable (over 600 is my largest so far).
I tried this on a copy of a recent h(t) file that I intentionally corrupted so that framecpp_verify would return 1 and was unable to get it to return 0 after over 600 tries, but it was a lot slower to process than the GEO file, so it might be a matter of how long I was willing to wait.