Skip to content

Decide how/when to test various feature flags #166

New issue
New issue
Closed as duplicate
Closed as duplicate
Decide how/when to test various feature flags#166
Labels
A-infraConcerns infrastructure rather than core functionality
Milestone
v0.2.0

Description

@marosset
marosset
opened on Jan 27, 2025

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. github-actions
    added
    S-needs-triageThe issue has not yet been reviewed.
    on Jan 27, 2025
  2. syntactically
    added
    S-confirmedBug is verified or proposal seems reasonable
    A-infraConcerns infrastructure rather than core functionality
    and removed
    S-needs-triageThe issue has not yet been reviewed.
    on Jan 28, 2025

  3. syntactically commented on Jan 29, 2025

    @syntactically
    syntactically
    on Jan 29, 2025
    Member

    I think this is encompassed/duplicated by #180?

  4. syntactically
    closed this as a duplicateof Improve testing architecture #180 on Jan 29, 2025
  5. danbugs
    modified the milestones: Backlog, v0.2.0 on Mar 4, 2025
  6. danbugs
    added
    lifecycle/duplicate
    and removed
    S-confirmedBug is verified or proposal seems reasonable
    on Apr 9, 2025
  7. danbugs
    added this to Hyperlight Milestoneson Apr 23, 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

    A-infraConcerns infrastructure rather than core functionality

    Type

    No type

    Projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions