Still send try job status even if test filter is used

This caused all CQ job to not show up on rietveld. Now that rietvelt supports
multiple try job per builder per patchset, this check is not useful anymore.

TBR=dpranke@chromium.org
BUG=
TEST=


Review URL: http://codereview.chromium.org/8895022

git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@113952 0039d316-1c4b-4281-b951-d872f2087c98

git_try.py

@@ -19,7 +19,7 @@ import git_cl
 def GetRietveldIssueNumber():
   try:
     return GIT.Capture(
-        ['config', 'branch.%s.rietveldissue' % GIT.GetBranch(None)])
+        ['config', 'branch.%s.rietveldissue' % GIT.GetBranch(None)]).strip()
   except subprocess2.CalledProcessError:
     return None
 
@@ -27,7 +27,7 @@ def GetRietveldIssueNumber():
 def GetRietveldPatchsetNumber():
   try:
     return GIT.Capture(
-        ['config', 'branch.%s.rietveldpatchset' % GIT.GetBranch(None)])
+        ['config', 'branch.%s.rietveldpatchset' % GIT.GetBranch(None)]).strip()
   except subprocess2.CalledProcessError:
     return None
 

trychange.py

@@ -785,11 +785,6 @@ def TryChange(argv,
       # If no bot is specified, either the default pool will be selected or the
       # try server will refuse the job. Either case we don't need to interfere.
 
-    # Prevent rietveld updates if we aren't running all the tests.
-    if options.testfilter is not None:
-      options.issue = None
-      options.patchset = None
-
     # Send the patch.
     if options.send_patch:
       # If forced.