Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Windows (without WSL) - config.yaml cannot resolve flows #2279

Closed
1 task done
Vidal-A opened this issue Jan 30, 2025 · 8 comments
Closed
1 task done

Windows (without WSL) - config.yaml cannot resolve flows #2279

Vidal-A opened this issue Jan 30, 2025 · 8 comments

Comments

@Vidal-A
Copy link

Vidal-A commented Jan 30, 2025

Is there an existing issue for this?

  • I have searched the existing issues and didn't find mine.

Steps to reproduce

  1. Put the config.yaml in the root directory.
  2. Add a flows section to the config.yaml
  3. Run "maestro test {root-directory}"

Config.yaml

flows:
  - "./scenario/wifi/*"

Actual results

When i use the windows version, from powershell:

Error message :

Flow inclusion pattern(s) did not match any Flow files

(Works on WSL)

About environment

WSL Maestro version : 1.39.9
Windows Maestro versions : 1.39.9
Windows 11.
Ubuntu 24.04.1 LTS

Maestro version

1.39.9

Copy link

linear bot commented Jan 30, 2025

@Vidal-A Vidal-A closed this as completed Jan 30, 2025
@Vidal-A
Copy link
Author

Vidal-A commented Jan 30, 2025

Error in my ticket, it doesn't work on either Linux or Windows, the issue is probably with my config.yaml. I consistently get "Flow inclusion pattern(s) did not match any Flow files:"

@jerone
Copy link

jerone commented Feb 2, 2025

Error in my ticket, it doesn't work on either Linux or Windows, the issue is probably with my config.yaml. I consistently get "Flow inclusion pattern(s) did not match any Flow files:"

I'm getting the same on Windows.
@Vidal-A Did you find a solution?

@Vidal-A
Copy link
Author

Vidal-A commented Feb 3, 2025

Error in my ticket, it doesn't work on either Linux or Windows, the issue is probably with my config.yaml. I consistently get "Flow inclusion pattern(s) did not match any Flow files:"

I'm getting the same on Windows. @Vidal-A Did you find a solution?

Yes, the issue ultimately comes from the Windows version. I necessarily have to go through WLS, which poses a problem for some teams. I shouldn't have closed the ticket ^^"
It is very important to specify the host on WLS, otherwise no commands will work.
maestro --host <local_ip> test scenario

Windows KO :
Image

Linux OK :
Image

If my config can help, Config.yaml in the scenario folder :

flows:
  - "sms_mms/*"
  - "wifi/*"
  - "browsing/*"

executionOrder:
  continueOnFailure: true
  flowsOrder:
    - init_browsing
    - 10.2.4
    - 10.1.2
    - 10.2.1
    - 10.2.2
    - 6.1.2
    - init_sms_mms
    - 5.1.1
    - 5.1.3
    - 5.1.4
    - 5.1.5
    - 5.1.6




@Vidal-A Vidal-A reopened this Feb 3, 2025
@jerone
Copy link

jerone commented Feb 3, 2025

I'm using Maestro without WSL, because funny enough, they removed the WSL requirement for installing and using Maestro on Windows recently: mobile-dev-inc/maestro-docs@b1ce863

@Vidal-A
Copy link
Author

Vidal-A commented Feb 3, 2025

Yes, me too, i use the 1.39.9, this windows version work fine, excepted for read and execute config.yaml.
With version 1.39.9, we should be able to do without WLS, but in practice, there are still some issues.

Probably a path parsing issue. If I have time, I will try to debug it.

@herval herval added the Maestro label Feb 3, 2025 — with Linear
@herval herval removed the Maestro label Feb 10, 2025
@JulienLeal
Copy link

I had the same issue

@Fishbowler Fishbowler changed the title Windows without WLS config.yaml issue Windows (without WSL) - config.yaml cannot resolve flows Feb 20, 2025
@Fishbowler
Copy link
Contributor

I've updated the ticket to reflect the proper state of this issue. Please shout up if I've misrepresented anything.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants