Bug 5255 - Provide access to tasks executable output in Toaster
Summary: Provide access to tasks executable output in Toaster
Status: ACCEPTED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: Future
Assignee: Toaster default assignee
QA Contact:
URL:
Whiteboard: GUI design pending
: 4624 5190 5254 (view as bug list)
Depends on:
Blocks: 5254
  Show dependency tree
 
Reported: 2013-09-23 14:59 UTC by Belen Barros Pena
Modified: 2023-12-14 04:28 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: New (Never tested)
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 Belen Barros Pena 2013-09-23 14:59:29 UTC
source_url in the tasks table does not return any information
Comment 1 Cristiana Voicu 2013-11-18 13:17:31 UTC
As Alex said, this field should be renamed to file_name, and is the name of the file where the task is defined
Comment 2 Cristiana Voicu 2013-11-18 13:18:45 UTC
*** Bug 5190 has been marked as a duplicate of this bug. ***
Comment 3 Alexandru Damian 2013-12-05 10:59:01 UTC
Field name changed to file_name.

In review on toaster/master.
Comment 4 Belen Barros Pena 2013-12-09 14:12:12 UTC
(In reply to comment #3)
> Field name changed to file_name.
> 
> In review on toaster/master.

file_name is returning the .bb file or .inc file for the recipe the task applied to. 

However, field-name was supposed to be the path to the file executed for a task (i.e the Python or Shell script).

I am using toaster/master:f9b2c43dccff32047daf6979c8292088bea911e1
Comment 5 Alexandru Damian 2013-12-09 14:21:43 UTC
This issue is a bit more complex than appeared at this moment. Citing Paul's words from the review email (available on toaster@yoctoproject.org)

It occurs to me that the trouble with our initial model of a single file / line
is it isn't going to be able to effectively reflect how our task functions came
to be - they're really just a special case of variables and can thus be
prepended/appended in a number of different places to get the final function.
This kind of suggests that the history is what we ought to be using.


I'm gonna try a second solution - turning on variable history for all tasks and saving the variable history for the executed task function in a separate data structure. 

Moving the bug to ACCEPTED. Submitted patch now deleted.
Comment 6 Alexandru Damian 2013-12-09 14:23:03 UTC
*** Bug 5254 has been marked as a duplicate of this bug. ***
Comment 7 Belen Barros Pena 2014-01-23 11:30:17 UTC
After speaking with RP, it looks like we'll try to give users access to the task executable output. While working on the local use case, we'll show the path to the file where the executable output can be found. For the remote use case, it is to be defined how we'll provide access to the information.

This effectively means that the starting line information should disappear from the task details page.
Comment 8 Belen Barros Pena 2014-02-13 12:02:34 UTC
We are going to try RP's suggestion, but we won't get to it in 1.6. Moving to 1.7
Comment 9 Ionut Chisanovici 2015-02-03 15:54:53 UTC
Also, appears in 1.8 M2 RC2, commit: 22c38e2d8a058619e3d05534b5e830b750aa4241
Comment 10 Belen Barros Pena 2015-02-03 16:49:26 UTC
This is not implemented, so we shouldn't be testing this at the moment.
Comment 11 Belen Barros Pena 2015-04-30 14:47:33 UTC
*** Bug 4624 has been marked as a duplicate of this bug. ***
Comment 12 Elliot Smith 2015-09-22 08:58:16 UTC
This bug is one of those listed as causing failures here:
https://wiki.yoctoproject.org/wiki/WW38_-_2015-09-15_-_Full_Pass_1.9_M3.rc1#Test_Run_Summary_Report

But this bug is set for "Future". Please could we either move this bug to the correct milestone, or have it removed from the test run?
Comment 13 Belen Barros Pena 2015-09-22 09:26:46 UTC
Elliot is right: this feature has not been implemented. Future is its correct milestone. 

There must a field in the database for this that is not getting populated, and that could be causing the test failure. But that's kind of irrelevant: this bug should not be part of the test run.