-
Notifications
You must be signed in to change notification settings - Fork 242
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
Labels
Comments
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
As it can be seen in this Cirrus CI job:
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).The text was updated successfully, but these errors were encountered: