| Summary: | elapsed_time value null for tasks with outcome=0 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Toaster | Reporter: | Ionut Chisanovici <ionutx.chisanovici> | ||||
| Component: | toaster | Assignee: | Jessica <jessica.zhang> | ||||
| Status: | RESOLVED NOTABUG | QA Contact: | Ionut Chisanovici <ionutx.chisanovici> | ||||
| Severity: | normal | ||||||
| Priority: | Medium | CC: | alexandru.damian, belen.barros.pena, bluelightning, cristiana.voicu | ||||
| Version: | 1.7 | ||||||
| Target Milestone: | 1.8 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
I can see instances of executed tasks with elapsed time 0, but the buildstats for those tasks seem to report elapsed time 0, so Toaster seems to be reporting the right thing. We should probably change this test: if the reported elapsed time for the task is 0, but this matches buildstats, Toaster is doing the right thing and there is no problem there. If the reported elapsed time for the task is 0 but buildstats reports something different, then there is a problem in Toaster. Closed as the issue is not related to the field itself but to this bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=6864 Cheers, Ionut C |
Created attachment 2167 [details] toaster_db Hi, Elapsed_time value missing for task execute true and outcome=0 Commit: 5367855fe56db0c09b8fa7bb423b9de18d11eecc select * from orm_task where id=2048; build_id = 1 work_directory = cpu_usage = 0 task_executed = 1 disk_io = 2632 line_number = 0 path_to_sstate_obj = sstate_checksum = d039571f6e3873926e6c8c8e287669c1 source_url = order = 515 elapsed_time = logfile = recipe_id = 55 task_name = do_fetch message = outcome = 0 id = 2048 sstate_result = 0 script_type = 0 Attached the toaster db. Cheers, Ionut C