Skip to content

Multi pipeline capture tests are misleading #501

Open

Description

@ranj063

When running the multi pipeline tests for capture, the test picks all the possible capture devices and if thats less than the max count allowed, the remaining ones are filled up with playback pipelines. That is a bit misleading. This becomes a different test than just multiple-pipeline-capture then. Not sure if multiple-pipeline-playback does something similar.

If the number of capture pipelines are less than max count, the test should process with just those.

Activity

  1. marc-hb commented on Nov 10, 2020

    @marc-hb
    Collaborator

    If the number of capture pipelines are less than max count, the test should process with just those.

    This sounds like a simple enough change, could you do it? Warning: it could conflict with some work in progress in this file, notably #497. Maybe wait until #497 is done. Also : good habit to have a quick look at shellcheck -x output before starting to code.

  2. ranj063 commented on Nov 10, 2020

    @ranj063
    ContributorAuthor

    This sounds like a simple enough change, could you do it? Warning: it could conflict with some work in progress in this file, notably #497. Maybe wait until #497 is done. Also : good habit to have a quick look at shellcheck -x output before starting to code.

    The change is simple but I dont want to lose the current multiple-pipeline-capture test either. it is a perfectly valid test with multiple-pipeline-playbackandcapture test. So we should keep this and create a new test for a simple multi capture test

  3. marc-hb commented on Nov 11, 2020

    @marc-hb
    Collaborator

    cc: @fredoh9

    So we should keep this and create a new test for a simple multi capture test

    I just put multiple-pipeline-playback and multiple-pipeline-capture side by side for the first time and realized the unbelievable amount of copy/paste/diverge :-(

  4. plbossart commented on Nov 17, 2020

    @plbossart
    Member
  5. assigned and unassigned on Nov 17, 2020
  6. marc-hb commented on Nov 18, 2020

    @marc-hb
    Collaborator

    The second, APL_UP2_NOCODEC failure is a test regression I just introduced in #497, apologies and tentative fix in #521. Please help review.

    The BSW_CYAN_MAX98090 looks different.

  7. marc-hb commented on Jun 22, 2023

    @marc-hb
    Collaborator

    @ranj063 , was this fixed by @fredoh9 in commit 41c1427? If yes then please close.

  8. added
    P2Critical bugs or normal features
    on Jun 22, 2023
  9. marc-hb commented on Jan 2, 2024

    @marc-hb
    Collaborator

    @ranj063 , good to close?

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

    P2Critical bugs or normal featurestype:enhancementNew framework feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions