Machine CL1 reset connection.

[c0nd3v]

This happens in Win10_2004x64.
Same thing happens also in Win10_1809x64 except it only resets the connection once.
Tested also Win2016x64 and it didn't have this problem.

Please let me know if there is anything else I can provide.

P.S After the machine resets the connection, everything is working properly

MyUserName@MyUserName-Virtual-Machine:~/HCK-CI/repos/AutoHCK.git$ bin/ns bin/auto_hck test -d MyDriverName -p Win10_2004x64 --driver-path /home/MyUserName/HCK-CI/MyDriverName

...

I, [2024-02-07T13:28:13.733190 #3408]  INFO -- : Loading device: e1000e
I, [2024-02-07T13:28:13.733589 #3408]  INFO -- : Initiating connection to studio
I, [2024-02-07T13:28:13.735386 #3408]  INFO -- : QemuMachine0002_CL01 started with PID 3458
I, [2024-02-07T13:28:13.735640 #3408]  INFO -- : Loading device: e1000e
I, [2024-02-07T13:28:23.296984 #3408]  INFO -- : Updating HCK filters
I, [2024-02-07T13:28:31.427751 #3408]  INFO -- : Creating pool
I, [2024-02-07T13:28:31.759473 #3408]  INFO -- : Creating project
I, [2024-02-07T13:28:31.973632 #3408]  INFO -- : Waiting for client CL1 to be recognized
I, [2024-02-07T13:28:37.312736 #3408]  INFO -- : Client CL1 recognized
I, [2024-02-07T13:28:37.312836 #3408]  INFO -- : Waiting for client CL1 initialization
I, [2024-02-07T13:29:02.702566 #3408]  INFO -- : Client CL1 initialized
I, [2024-02-07T13:29:02.702660 #3408]  INFO -- : Preparing client CL1...
I, [2024-02-07T13:29:02.702703 #3408]  INFO -- : Installing custom driver MyDriverName.inf in CL1
W, [2024-02-07T13:29:28.846918 #3408]  WARN -- : Tools action failure
   -- Machine CL1 reset connection.
W, [2024-02-07T13:29:28.846995 #3408]  WARN -- : Installing driver package on machine CL1 failed
I, [2024-02-07T13:29:38.847147 #3408]  INFO -- : Trying again to install driver package on machine CL1
W, [2024-02-07T13:30:05.003539 #3408]  WARN -- : Tools action failure
   -- Machine CL1 reset connection.
W, [2024-02-07T13:30:05.003625 #3408]  WARN -- : Installing driver package on machine CL1 failed
I, [2024-02-07T13:30:15.003785 #3408]  INFO -- : Trying again to install driver package on machine CL1
I, [2024-02-07T13:30:52.456145 #3408]  INFO -- : Looking for DVL logs
I, [2024-02-07T13:30:52.456268 #3408]  INFO -- : Configuring client CL1...
I, [2024-02-07T13:30:52.456305 #3408]  INFO -- : Moving CL1 to pool
I, [2024-02-07T13:30:52.740524 #3408]  INFO -- : Setting CL1 state to Ready
I, [2024-02-07T13:31:58.038308 #3408]  INFO -- : Searching for target MyDriverName Device (type 0) on CL1
I, [2024-02-07T13:31:58.219919 #3408]  INFO -- : Adding target MyDriverName Device on CL1 to project MyDriverName-Win10_2004x64
I, [2024-02-07T13:31:59.964152 #3408]  INFO -- : Applying microsoft's playlist
I, [2024-02-07T13:32:04.496473 #3408]  INFO -- : Tests results logs updated via the result uploader
I, [2024-02-07T13:32:07.494423 #3408]  INFO -- : Adding to queue: DF - InfVerif INF Verification (bbcc1b46-d0bf-46c8-85b4-2cd62df34a20)

[kostyanf14]

Hi @c0nd3v.

Thanks for your report. This is a known issue and unfortunately on the Windows side.

Does HCK-CI work normally after Machine CL1 reset connection ?

[c0nd3v]

@kostyanf14 Yes, everything working properly after that.