Bug 6864 - message field for some tasks is empty
Summary: message field for some tasks is empty
Status: RESOLVED WONTFIX
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 1.7
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Alexandru Damian
QA Contact: Ionut Chisanovici
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-10-22 10:55 UTC by Ionut Chisanovici
Modified: 2014-10-22 15:54 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ionut Chisanovici 2014-10-22 10:55:18 UTC
Hi,

The message field for some tasks in orm_task is empty and this is causing some toaster selftest to fail.

select * from orm_task where id=1349;
          build_id = 1
    work_directory = 
         cpu_usage = 11.7
     task_executed = 1
           disk_io = 0
       line_number = 0
path_to_sstate_obj = 
   sstate_checksum = 3ae2716d849b54828a3a7c2fee658657
        source_url = 
             order = 210
      elapsed_time = 
           logfile = 
         recipe_id = 249
         task_name = do_unpack
           message = 
           outcome = 0
                id = 1349
     sstate_result = 0
       script_type = 0

For extracting the cpu_usage, elapsed_time and disk_io (toaster selftests), these tests are using the informations provided by the task message field for getting the task stats file path.
If the message field is empty then these tests will fail.

Cheers,
Ionut C
Comment 1 Alexandru Damian 2014-10-22 15:54:53 UTC
Not all task-related events come with a 'message' field from bitbake - this is why we don't have message fields for some of the tasks being run.

Furthermore, the message field isn't intended to be machine-readable, and the paths mentioned in those messages are intended for human usage.

I suggest that the tests lookup the buildstats file some other way.