Skip to content

promqle2etest: Optional parallelization #179

@bwplotka

Description

@bwplotka

We might want to revisit the Run abstraction. Doing t.Run +t.Parallel deep nested functions can be confusing for Run callers as:

  • Every code that's put after Run will still be run before Run(!) execution.
  • Its not possible to perform logic AFTER Run (knowing when Run succeeded) - this is useful when you would like to test more things after Run e.g. Metadata API

See GoogleCloudPlatform/prometheus#246

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions