[Dashboard] Fix regex for complex story names

[Dashboard] Fix regex for complex story names

Arguments quoting in the command line used for bisect jobs is not
interpreted correctly, causing issues in particular with --story-filter
argument values with spaces or other special characters in them.

To play it safe, while the underlying issue is fixed, we only keep from
story names safe characters (alphanumeric ascii) and replace all others
with match-any-character regex dots.

BUG=chromium:662472
,catapult:#2967

Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/b3ab8eaabeea5a812819a8f7b6c08559136f34ce

[perezju, 2016-11-07 13:56:37]

perezju@chromium.org changed reviewers:
+ sullivan@chromium.org

[perezju, 2016-11-07 13:56:37]

Annie, please have a look. This is more like a quick workaround, while I get
some more time to investigate the underlying issue (i.e. why bisect and or infra
scripts do not interpret quoting correctly).

[sullivan, 2016-11-07 14:39:35]

The CQ bit was checked by sullivan@chromium.org

[sullivan, 2016-11-07 14:39:35]

lgtm

Thanks Juan! I'll push this when it lands, let me know if you need any
additional debugging help.

[commit-bot: I haz the power, 2016-11-07 14:39:44]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-07 14:42:13]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-11-07 14:42:14]

Try jobs failed on following builders:
  Catapult Presubmit on master.tryserver.client.catapult (JOB_FAILED,
https://build.chromium.org/p/tryserver.client.catapult/builders/Catapult%20Pr...)

[sullivan, 2016-11-07 14:44:24]

Description was changed from

==========
[Dashboard] Fix regex for complex story names

Arguments quoting in the command line used for bisect jobs is not
interpreted correctly, causing issues in particular with --story-filter
argument values with spaces or other special characters in them.

To play it safe, while the underlying issue is fixed, we only keep from
story names safe characters (alphanumeric ascii) and replace all others
with match-any-character regex dots.

BUG=662472,catapult:#2967
==========

to

==========
[Dashboard] Fix regex for complex story names

Arguments quoting in the command line used for bisect jobs is not
interpreted correctly, causing issues in particular with --story-filter
argument values with spaces or other special characters in them.

To play it safe, while the underlying issue is fixed, we only keep from
story names safe characters (alphanumeric ascii) and replace all others
with match-any-character regex dots.

BUG=chromium:662472,catapult:#2967
==========

[sullivan, 2016-11-07 14:44:27]

The CQ bit was checked by sullivan@chromium.org

[commit-bot: I haz the power, 2016-11-07 14:44:34]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-07 14:59:51]

Description was changed from

==========
[Dashboard] Fix regex for complex story names

Arguments quoting in the command line used for bisect jobs is not
interpreted correctly, causing issues in particular with --story-filter
argument values with spaces or other special characters in them.

To play it safe, while the underlying issue is fixed, we only keep from
story names safe characters (alphanumeric ascii) and replace all others
with match-any-character regex dots.

BUG=chromium:662472,catapult:#2967
==========

to

==========
[Dashboard] Fix regex for complex story names

Arguments quoting in the command line used for bisect jobs is not
interpreted correctly, causing issues in particular with --story-filter
argument values with spaces or other special characters in them.

To play it safe, while the underlying issue is fixed, we only keep from
story names safe characters (alphanumeric ascii) and replace all others
with match-any-character regex dots.

BUG=chromium:662472,catapult:#2967

Committed:
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...
==========

[commit-bot: I haz the power, 2016-11-07 14:59:52]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...

[sullivan, 2016-11-07 15:05:30]

This is live on the perf dashboard. Should we re-run bisects blocked on bug
662472?

[perezju, 2016-11-07 15:41:11]

On 2016/11/07 15:05:30, sullivan wrote:
> This is live on the perf dashboard. Should we re-run bisects blocked on bug
> 662472?

Yes! Hopefully they should run with no issues now.