Skip to content

Decide how/when to test various feature flags #166

Closed as duplicate
Closed as duplicate

Description

@marosset

Our just targets support running tests with no-default-features and also pass in sets of specific features but these options aren't utilized in our ci workflows.

We should evaluate options for periodically testing non-default sets of feature flags (possible during weekly / periodic jobs).

Activity

  1. added
    lifecycle/confirmedBug is verified or proposal seems reasonable
    area/infrastructureConcerns infrastructure rather than core functionality
    and removed on Jan 28, 2025
  2. syntactically commented on Jan 29, 2025

    @syntactically
    Member

    I think this is encompassed/duplicated by #180?

  3. modified the milestones: Backlog, v0.2.0 on Mar 4, 2025
  4. added
    lifecycle/duplicateThis issue is a duplicate of another issue
    and removed
    lifecycle/confirmedBug is verified or proposal seems reasonable
    on Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/infrastructureConcerns infrastructure rather than core functionalitylifecycle/duplicateThis issue is a duplicate of another issue

    Type

    No type

    Projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions