source_url in the tasks table does not return any information
As Alex said, this field should be renamed to file_name, and is the name of the file where the task is defined
*** Bug 5190 has been marked as a duplicate of this bug. ***
Field name changed to file_name. In review on toaster/master.
(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
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.
*** Bug 5254 has been marked as a duplicate of this bug. ***
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.
We are going to try RP's suggestion, but we won't get to it in 1.6. Moving to 1.7
Also, appears in 1.8 M2 RC2, commit: 22c38e2d8a058619e3d05534b5e830b750aa4241
This is not implemented, so we shouldn't be testing this at the moment.
*** Bug 4624 has been marked as a duplicate of this bug. ***
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?
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.