[LU-7627] Lustre sanity tests 130b, 130c, 130d, and 130e have a faulty comparison that causes them to fail

Duplicate — Mon, 29 May 2017 05:21:34 +0000

Test 130c-130e failures are all the same coding issue, where a comparison is done on two hex numbers without prefacing them with '0x' so that they are treated as hex:
test 130b:
7178 if (( $frag_lun != $last_lun )); then
should be
7178 if (( 0x$frag_lun != 0x$last_lun )); then
test 130c:
7227 if (( $frag_lun != $last_lun )); then
should be:
7227 if (( 0x$frag_lun != 0x$last_lun )); then
test 130d:
7282 if (( $frag_lun != $last_lun )); then
should be
7282 if (( 0x$frag_lun != 0x$last_lun )); then
test 130e:
7336 if (( $frag_lun != $last_lun )); then
should be
7336 if (( 0x$frag_lun != 0x$last_lun )); then

Tests 130[bcde] failed because numbers parsed with leading zeros
treated as octal number so there is error value too great for base
when parsed lun id greater than 0007 value,

Whamcloud Community JIRA

[LU-7627] Lustre sanity tests 130b, 130c, 130d, and 130e have a faulty comparison that causes them to fail