Project

General

Profile

Actions

Bug #7533

closed

paddles: Subsuites like upgrade:dumpling-x break paddles' parsing

Added by Zack Cerza about 10 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Actions #1

Updated by Zack Cerza about 10 years ago

  • Status changed from New to 4
  • Assignee changed from Zack Cerza to Sage Weil

Sage, what do you think about changing the field delimiter in run names from '-' to '_' - e.g. "teuthology_2014-02-23_23:02:27-upgrade:dumpling-x_firefly_testing_basic_plana" ? Can you think of things it would break?

Actions #2

Updated by Sage Weil about 10 years ago

  • Assignee changed from Sage Weil to Zack Cerza

Zack Cerza wrote:

Sage, what do you think about changing the field delimiter in run names from '-' to '_' - e.g. "teuthology_2014-02-23_23:02:27-upgrade:dumpling-x_firefly_testing_basic_plana" ? Can you think of things it would break?

I think this is fine. If we're really paranoid, we could also use a double __. As far as I know the only thing that parses this is pupito.

OTOH, if we put all of the constituent fields in the yaml, we could also shove them into the database table directly key off of that instead, and treat the string as just a unique id. But even then, _ probably improves readability.

Actions #3

Updated by Zack Cerza about 10 years ago

  • Priority changed from High to Normal
Actions #4

Updated by Zack Cerza about 10 years ago

Yeah, I'm now also thinking it would be best to not rely on parsing.

Actions #5

Updated by Zack Cerza about 10 years ago

  • Status changed from 4 to Closed

Closing this in favor of #8135

Actions

Also available in: Atom PDF