<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>5255</bug_id>
          
          <creation_ts>2013-09-23 14:59:29 +0000</creation_ts>
          <short_desc>Provide access to tasks executable output in Toaster</short_desc>
          <delta_ts>2023-12-14 04:28:31 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>Toaster</product>
          <component>toaster</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>ACCEPTED</bug_status>
          <resolution></resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>GUI design pending   </status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>Future</target_milestone>
          
          <blocked>5254</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="Belen Barros Pena">belen.barros.pena</reporter>
          <assigned_to name="Toaster default assignee">toaster</assigned_to>
          <cc>alexandru.c.georgescu</cc>
    
    <cc>alexandru.damian</cc>
    
    <cc>belen.barros.pena</cc>
    
    <cc>bogdanx.a.voiculescu</cc>
    
    <cc>david.reyna</cc>
    
    <cc>jose.perez.carranza</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>New (Never tested)</cf_regression_type>
          
          <cf_docchange>No (bug/feature does not impact docs)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>37069</commentid>
    <comment_count>0</comment_count>
    <who name="Belen Barros Pena">belen.barros.pena</who>
    <bug_when>2013-09-23 14:59:29 +0000</bug_when>
    <thetext>source_url in the tasks table does not return any information</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>38857</commentid>
    <comment_count>1</comment_count>
    <who name="Cristiana Voicu">cristiana.voicu</who>
    <bug_when>2013-11-18 13:17:31 +0000</bug_when>
    <thetext>As Alex said, this field should be renamed to file_name, and is the name of the file where the task is defined</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>38859</commentid>
    <comment_count>2</comment_count>
    <who name="Cristiana Voicu">cristiana.voicu</who>
    <bug_when>2013-11-18 13:18:45 +0000</bug_when>
    <thetext>*** Bug 5190 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>39236</commentid>
    <comment_count>3</comment_count>
    <who name="Alexandru Damian">alexandru.damian</who>
    <bug_when>2013-12-05 10:59:01 +0000</bug_when>
    <thetext>
Field name changed to file_name.

In review on toaster/master.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>39295</commentid>
    <comment_count>4</comment_count>
    <who name="Belen Barros Pena">belen.barros.pena</who>
    <bug_when>2013-12-09 14:12:12 +0000</bug_when>
    <thetext>(In reply to comment #3)
&gt; Field name changed to file_name.
&gt; 
&gt; 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</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>39296</commentid>
    <comment_count>5</comment_count>
    <who name="Alexandru Damian">alexandru.damian</who>
    <bug_when>2013-12-09 14:21:43 +0000</bug_when>
    <thetext>This issue is a bit more complex than appeared at this moment. Citing Paul&apos;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&apos;t going to be able to effectively reflect how our task functions came
to be - they&apos;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&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>39298</commentid>
    <comment_count>6</comment_count>
    <who name="Alexandru Damian">alexandru.damian</who>
    <bug_when>2013-12-09 14:23:03 +0000</bug_when>
    <thetext>*** Bug 5254 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40004</commentid>
    <comment_count>7</comment_count>
    <who name="Belen Barros Pena">belen.barros.pena</who>
    <bug_when>2014-01-23 11:30:17 +0000</bug_when>
    <thetext>After speaking with RP, it looks like we&apos;ll try to give users access to the task executable output. While working on the local use case, we&apos;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&apos;ll provide access to the information.

This effectively means that the starting line information should disappear from the task details page.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40327</commentid>
    <comment_count>8</comment_count>
    <who name="Belen Barros Pena">belen.barros.pena</who>
    <bug_when>2014-02-13 12:02:34 +0000</bug_when>
    <thetext>We are going to try RP&apos;s suggestion, but we won&apos;t get to it in 1.6. Moving to 1.7</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>48510</commentid>
    <comment_count>9</comment_count>
    <who name="Ionut Chisanovici">ionutx.chisanovici</who>
    <bug_when>2015-02-03 15:54:53 +0000</bug_when>
    <thetext>Also, appears in 1.8 M2 RC2, commit: 22c38e2d8a058619e3d05534b5e830b750aa4241</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>48516</commentid>
    <comment_count>10</comment_count>
    <who name="Belen Barros Pena">belen.barros.pena</who>
    <bug_when>2015-02-03 16:49:26 +0000</bug_when>
    <thetext>This is not implemented, so we shouldn&apos;t be testing this at the moment.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>50652</commentid>
    <comment_count>11</comment_count>
    <who name="Belen Barros Pena">belen.barros.pena</who>
    <bug_when>2015-04-30 14:47:33 +0000</bug_when>
    <thetext>*** Bug 4624 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>54423</commentid>
    <comment_count>12</comment_count>
    <who name="Elliot Smith">elliot.smith</who>
    <bug_when>2015-09-22 08:58:16 +0000</bug_when>
    <thetext>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 &quot;Future&quot;. Please could we either move this bug to the correct milestone, or have it removed from the test run?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>54425</commentid>
    <comment_count>13</comment_count>
    <who name="Belen Barros Pena">belen.barros.pena</who>
    <bug_when>2015-09-22 09:26:46 +0000</bug_when>
    <thetext>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&apos;s kind of irrelevant: this bug should not be part of the test run.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>