fiotest reports results for wrong target

[mwasilew]

There are cases when results are reported for wrong target. Example:

$ fioctl targets tests 11
NAME   STATUS  ID                                    CREATED AT                     DEVICE
----   ------  --                                    ----------                     ------
sleep  PASSED  5fa31aa3-1134-4e39-ab61-4a814272c7a0  2021-01-28 15:17:20 +0000 UTC  milosz-rpi3-01
sleep  PASSED  04d1f6ec-5ae6-4a5b-be08-2f31c4011af5  2021-01-28 15:17:20 +0000 UTC  milosz-rpi3-01
ltp    PASSED  c692cd82-416f-4efc-a01b-f570eb5b697f  2021-01-28 15:17:20 +0000 UTC  bbb-01

$ fioctl targets tests 14
NAME    STATUS   ID                                    CREATED AT                     DEVICE
----    ------   --                                    ----------                     ------
ltp     PASSED   1382f453-2125-4e14-ba8d-ab70cf097682  2021-01-28 15:17:20 +0000 UTC  milosz-rpi3-01
sleep   PASSED   745c74ea-9519-44b3-a7d2-28e828b634a7  2021-01-28 15:17:20 +0000 UTC  milosz-rpi3-01
sleep   PASSED   23891a17-985a-4806-95c4-2c758e926b78  2021-01-28 15:17:20 +0000 UTC  milosz-rpi3-01
reboot  RUNNING  72650424-4102-4785-84a1-b8ca53573f55  2021-01-28 15:17:20 +0000 UTC  milosz-rpi3-01
reboot  RUNNING  7a588536-1202-4fc3-9b8e-dc71cb6c0d05  2021-01-28 15:25:52 +0000 UTC  bbb-01

$ fioctl targets tests 11 c692cd82-416f-4efc-a01b-f570eb5b697f
Name:      ltp
Status:    PASSED
Created:   2021-01-28 15:17:20 +0000 UTC
Completed: 
Device:    bbb-01
Artifacts:
	 console.log

TEST RESULT    STATUS
-----------    ------
abs01          PASSED
atof01         PASSED
float_bessel   PASSED
float_exp_log  PASSED
float_iperb    PASSED
float_power    PASSED
float_trigo    PASSED
fptest01       PASSED
fptest02       PASSED
nextafter01    PASSED

This shows that 'math' tests were executed. They're reported under target 11 while they were only enabled on target 14 with this commit:
https://source.foundries.io/factories/milosz-rpi3/containers.git/commit/?id=33a27f1595b12463e2c16248889f24c148fdbd9c

My suspicion is that 'reboot' is the culprit here.