Details
-
Bug
-
Resolution: Done
-
P2: Important
-
None
-
production
-
None
Description
Sample build:
https://testresults.qt.io/coin/integration/qt3dstudio/qt3d-runtime/tasks/1523002838
This had test item for configuration "Windows 10 (msvc2017-x86_64)" stuck because mature-bear crashed. Heartbeat worked correctly and restarted the agent and it finished correctly.
However the log link is not correct:
It seems the gz header is located in two places in the file:
hexdump -C log.txt.gz | grep "1f 8b 08 00" -A 2 00000000 1f 8b 08 00 00 00 00 00 00 ff 24 c9 b1 0a 02 31 |..........$....1| 00000010 0c 06 e0 dd a7 f8 47 1d ec 25 b9 86 b4 79 0e c1 |......G..%...y..| 00000020 59 34 d4 c2 d9 0e 77 ef 8f a0 f3 f7 68 31 0e 17 |Y4....w.....h1..| -- 00003cd0 42 1d 4c e3 02 00 00 00 ff ff 1f 8b 08 00 00 00 |B.L.............| 00003ce0 00 00 00 ff 24 c9 31 0e c2 30 0c 05 d0 9d 53 fc |....$.1..0....S.| 00003cf0 11 06 d2 7c b7 a9 13 9f 03 89 19 81 15 22 95 64 |...|.........".d|
I used hex editor to remove everything before 0x3cda and the log file was functional again and showed the logs of the new build. That means the new gz file is simply appended to the old one.
Attachments
Issue Links
- is replaced by
-
QTQAINFRA-2192 Agent logging could be more robust
- Closed
- mentioned in
-
Page Loading...