Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Listing tests issue in Cirrus CI with latest Avocado #3457

Open
clebergnu opened this issue Jul 13, 2022 · 0 comments
Open

Listing tests issue in Cirrus CI with latest Avocado #3457

clebergnu opened this issue Jul 13, 2022 · 0 comments
Assignees
Labels

Comments

@clebergnu
Copy link
Contributor

As it can be seen in this Cirrus CI job:

python3 -m avocado -V list --vt-save-config=/tmp/config --vt-type=$VT_TYPE -- boot | tee /tmp/list
No python imaging library installed. Screendump and Windows guest BSOD detection are disabled. In order to enable it, please install python-imaging or the equivalent for your distro.
Virsh executable not set or found on path, virsh module will not function normally
No python imaging library installed. PPM image conversion to JPEG disabled. In order to enable it, please install python-imaging or the equivalent for your distro.
Type Test Tag(s)
Resolver             Reference Info
avocado-instrumented boot      File "boot" does not end with ".py"
avocado-vt           boot      Unsupported kind of runnable: avocado-vt
python-unittest      boot      File "boot" does not end with ".py"
exec-test            boot      File "boot" does not exist or is not a executable file
tap                  boot      File "boot" does not exist or is not a executable file
TEST TYPES SUMMARY
==================
test $(wc -l < /tmp/list) -eq 1

It fails to produce a list of the 'boot' test(s), with a very weird message that at first sight, should only be given while attempting to run an avocado-vt test (and not during resolution).

@clebergnu clebergnu added the bug label Jul 13, 2022
@clebergnu clebergnu self-assigned this Jul 13, 2022
clebergnu added a commit to clebergnu/avocado-vt that referenced this issue Jul 13, 2022
This is a workaround for the fact that current Avocado will look for
the runner script while doing resolution (creating Runnables) because
it will populate the Runnable configuration with the "used
configuration" for that kind of runner.

If a change in Avocado will be needed is TBD, but this takes care of
the broken resolution in the CI environment.

Reference: avocado-framework#3457
Signed-off-by: Cleber Rosa <[email protected]>
clebergnu added a commit to clebergnu/avocado-vt that referenced this issue Jul 13, 2022
This is a workaround for the fact that current Avocado will look for
the runner script while doing resolution (creating Runnables) because
it will populate the Runnable configuration with the "used
configuration" for that kind of runner.

If a change in Avocado will be needed is TBD, but this takes care of
the broken resolution in the CI environment.

Reference: avocado-framework#3457
Signed-off-by: Cleber Rosa <[email protected]>
clebergnu added a commit to clebergnu/avocado-vt that referenced this issue Jul 13, 2022
This is a workaround for the fact that current Avocado will look for
the runner script while doing resolution (creating Runnables) because
it will populate the Runnable configuration with the "used
configuration" for that kind of runner.

If a change in Avocado will be needed is TBD, but this takes care of
the broken resolution in the CI environment.

Reference: avocado-framework#3457
Signed-off-by: Cleber Rosa <[email protected]>
clebergnu added a commit to clebergnu/avocado-vt that referenced this issue Jul 13, 2022
This is a workaround for the fact that current Avocado will look for
the runner script while doing resolution (creating Runnables) because
it will populate the Runnable configuration with the "used
configuration" for that kind of runner.

If a change in Avocado will be needed is TBD, but this takes care of
the broken resolution in the CI environment.

Reference: avocado-framework#3457
Signed-off-by: Cleber Rosa <[email protected]>
clebergnu added a commit to clebergnu/avocado-vt that referenced this issue Jul 14, 2022
This is a workaround for the fact that current Avocado will look for
the runner script while doing resolution (creating Runnables) because
it will populate the Runnable configuration with the "used
configuration" for that kind of runner.

If a change in Avocado will be needed is TBD, but this takes care of
the broken resolution in the CI environment.

Reference: avocado-framework#3457
Signed-off-by: Cleber Rosa <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant