-
-
Notifications
You must be signed in to change notification settings - Fork 663
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
Release 1.15.0 changed behavior of --skip="" #780
Closed
CecileRobertMichon opened this issue
Mar 16, 2021
· 2 comments
· Fixed by kedacore/http-add-on#102, shogo82148/goa-v1#102, kedacore/keda#1677, pivotal-cf/brokerapi#145 or evryfs/github-actions-runner-operator#216
Closed
Release 1.15.0 changed behavior of --skip="" #780
CecileRobertMichon opened this issue
Mar 16, 2021
· 2 comments
· Fixed by kedacore/http-add-on#102, shogo82148/goa-v1#102, kedacore/keda#1677, pivotal-cf/brokerapi#145 or evryfs/github-actions-runner-operator#216
Comments
thanks for reporting this @CecileRobertMichon - i'll push out a fix and cut a new patch version today. |
fixed in v1.15.2 |
This was referenced Mar 16, 2021
This was referenced Mar 17, 2021
build(deps): bump github.com/onsi/ginkgo from 1.15.1 to 1.15.2
cloudfoundry/cloud-service-broker#206
Merged
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before release 1.15,
--skip=""
would result in no tests being skipped (and only tests that match the--focus
flag to run). Now,--skip=""
causes all tests to be skipped.I suspect it might be caused by this recent change: #736
Before:
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api-provider-azure/1216/pull-cluster-api-provider-azure-e2e-full/1371635147035643904
After:
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/directory/pull-cluster-api-provider-azure-e2e-full/1371598441024589824
from testing kubernetes-sigs/cluster-api-provider-azure#1216
The text was updated successfully, but these errors were encountered: