Actions
Bug #745
closedLDV-core failed, making it look like a compile error
Start date:
01/28/2011
Due date:
% Done:
0%
Estimated time:
Detected in build:
1ac3689
Platform:
Published in build:
ccd16baedd855e27dc9598ac99d0911a3dfc567c
Description
I launched verification of a kernel's subdirectory with the following command:
LDV_MAX_RCVS=2 LDV_DEBUG=20 ldv-manager envs=linux-2.6.37.tar.bz2 kernel_driver=1 drivers=drivers/media/ "rule_models=29_1 37_1 43_1" name=test_702
It finished successfully, but the resultant report claimed that there was a build failure, which actually appeared a LDV-core error:
ldv-core: INFO: Successfully waited for command id "95" from "/anthill/stuff/ldv_fri_27/work/current--X--drivers/media/--X--test_702linux-2.6.37--X--29_1--X--37_1--X--43_1/linux-2.6.37/csd_deg_dscv/95" watcher: INFO: Called watcher: /anthill/stuff/ldv_fri_27/toolset/ldv-core/../watcher/ldv-watcher unpack /anthill/stuff/ldv_fri_27/work/current--X--drivers/media/--X--test_702linux-2.6.37--X--29_1--X--37_1--X--43_1/linux-2.6.37/csd_deg_dscv/95/task_input W, [2011-01-28T04:38:21.687398 #2406] WARN -- : Fake unpack! watcher: INFO: Watcher returns 0, waitpid: 0 ldv-core: NORMAL: Collect and process reports. ldv-core: NORMAL: Calling CSD reporter... no element found at line 4, column 0, byte 195 at /usr/lib/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/XML/Parser.pm line 187 at /anthill/stuff/ldv_fri_27/toolset/ldv-core/../build-cmd-extractor/cmd-stream-divider-reporter line 86 at /anthill/stuff/ldv_fri_27/toolset/ldv-core/../build-cmd-extractor/cmd-stream-divider-reporter line 86 watcher: INFO: Called watcher: /anthill/stuff/ldv_fri_27/toolset/ldv-core/../watcher/ldv-watcher success ldv-core 1 I, [2011-01-28T04:40:19.875450 #3347] INFO -- : Reported success for [["ldv-core", "1"]] watcher: INFO: Watcher returns 0, waitpid: 0 ldv-core: NORMAL: Creating BCE report... ldv-task: NORMAL: Calling LDV reporter. ldv-task-reporter: NORMAL: Report created successfully.
(the full console log is attached)
I'll launch it again (perhaps, what caused the problem was that I had occasionally killed one of the servers), and report if it doesn't reproduce.
Files
Actions