-
Notifications
You must be signed in to change notification settings - Fork 120
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
Change default of expectedFailuresList parameter #2793
base: main
Are you sure you want to change the base?
Change default of expectedFailuresList parameter #2793
Conversation
The expectedFailuresList parameter is used to define which tests are expected to fail so that they are not taken into consideration when marking the job's status. It is useful for specific scenarios, such as flaky tests, but we do not want every job to have this parameter by default. It should be used manually to make its intended use more explicit.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/6551732e947b4f6faf05fa02a6c2e1eb ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 56m 50s |
recheck Unrelated failure |
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/c2a07375d7934a7c8635d0a3aae39131 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 47m 52s |
I think this output is not what we are looking for: |
Did you want something like this: But I am wondering if jinja conditions work when defaults/main.yml is parsed. Apparently this passes the Yaml validators but I am not sure if ansible allows jinja conditions in defaults/main.yml
|
@kstrenkova try @frenzyfriday solution, or tune it a littlebit if that will not pass:
|
The expectedFailuresList parameter is used to define which tests are expected to fail so that they are not taken into consideration when marking the job's status. It is useful for specific scenarios, such as flaky tests, but we do not want every job to have this parameter by default. It should be used manually to make its intended use more explicit.