<?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>9881</bug_id>
          
          <creation_ts>2016-07-05 21:09:11 +0000</creation_ts>
          <short_desc>patchtest-oe: check patch&apos;s subject length</short_desc>
          <delta_ts>2017-12-06 17:02:47 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Yocto Project Subprojects</classification>
          <product>Patchwork/Patchtest</product>
          <component>Patchtest</component>
          <version>2.1</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium+</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>2.2 M2</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Leonardo Sandoval Gonzalez">leonardo.sandoval.gonzalez</reporter>
          <assigned_to name="Leonardo Sandoval Gonzalez">leonardo.sandoval.gonzalez</assigned_to>
          <cc>bluelightning</cc>
    
    <cc>sgw</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</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>63660</commentid>
    <comment_count>0</comment_count>
    <who name="Leonardo Sandoval Gonzalez">leonardo.sandoval.gonzalez</who>
    <bug_when>2016-07-05 21:09:11 +0000</bug_when>
    <thetext>Long subjects should be avoided, so the suite must trigger an assertion if length is &gt; MAX. MAX should be an general or open-embedded standard (80?)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>64276</commentid>
    <comment_count>1</comment_count>
    <who name="Leonardo Sandoval Gonzalez">leonardo.sandoval.gonzalez</who>
    <bug_when>2016-07-21 16:26:47 +0000</bug_when>
    <thetext>This check is already implemented on the patchtest-oe suite. The max length set is 80. There are two ways to validate this test:

1. Manual 
    1.1 Create a patch with git-format-patch and on the created patch, increase the message summary length to more that 80 chars.
    1.2 clone patchtest and patchtest-oe (right now these are not public), follow patchtest-oe setup instructions
    1.3 run the following cmd:
        cat $newpatch | patchtest - --test-dir $path-to-patchtest-oe/tests/mbox/subject
    1.4 expected output: you should see the FAIL on the particular testid

2. Selftest

   2.1 follow step 1.2, the run the following cmd:
       cd $patchtest-oe/selftest; ./selftest
   2.2 expected output: no output should be seen on console</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>