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
OTA-560: Improve developer-oriented docs #871
OTA-560: Improve developer-oriented docs #871
Conversation
6fa2a10
to
dfb8f22
Compare
/retest |
Makefile
Outdated
verify: verify-codegen | ||
.PHONY: update-codegen-crds update-codegen verify-codegen-crds verify-codegen verify | ||
.PHONY: update-codegen verify-codegen verify |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: dup verify-codegen
entries? Also, the pattern in the rest of the Makefile
appears to be a new .PHONY
entry after each target. I'm agnostic about whether we use that or a single large .PHONY
entry, but I'd rather not split between both patterns.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've just removed the codegen stuff entirely in a separate commit. The update-codegen
was just a tombstone and we do not use it in our CI jobs: https://github.com/openshift/release/blob/master/ci-operator/config/openshift/cluster-version-operator/openshift-cluster-version-operator-master.yaml
- Update `CONTRIBUTING.md` - Provide more convenience `Makefile` targets - Cleanup codegen `Makefile` targets - Move developer-facing content from `README.md` to `docs/dev/README.md`
The `update-codegen.sh` script is now a NOP, so we can remove it together with the script that checks its output, related `Makefile` targets and references from other helper scripts
dfb8f22
to
b3049c1
Compare
I'm not touching any code, so the unit test failure is very likely to be a flake, but it's a one that I've never seen before:
|
/test unit |
I'm not ignoring the flake, I'm looking if I can fix it in a separate PR |
/test e2e-agnostic-upgrade-into-change Azure flakes during cluster installation:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: petr-muller, wking The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
Looking at `Cache.Match()` implementation, the `c.Condition.Match()` on L133 can be called with `targetCondition=nil` and that seems to be intentional. In tests, `c.Condition` is a mock, which did not expect that pointer to be `nil` and dereferenced it, resulting in an occassional panic in tests like openshift#871 (comment). The fix stores the full pointer (its deepcopy to avoid sharing that memory) in the mock instead. I needed to restructure the tests a little to allow adding a nil parameter testcase
/hold cancel |
Looking at `Cache.Match()` implementation, the `c.Condition.Match()` on L133 can be called with `targetCondition=nil` and that seems to be intentional. In tests, `c.Condition` is a mock, which did not expect that pointer to be `nil` and dereferenced it, resulting in an occassional panic in tests like openshift#871 (comment). The fix stores the full pointer (its deepcopy to avoid sharing that memory) in the mock instead. I needed to restructure the tests a little to allow adding a nil parameter testcase
/override ci/prow/e2e-agnostic-upgrade-into-change this is a docs change |
@petr-muller: Overrode contexts on behalf of petr-muller: ci/prow/e2e-agnostic-upgrade-into-change In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@petr-muller: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Looking at `Cache.Match()` implementation, the `c.Condition.Match()` on L133 can be called with `targetCondition=nil` and that seems to be intentional. In tests, `c.Condition` is a mock, which did not expect that pointer to be `nil` and dereferenced it, resulting in an occassional panic in tests like openshift#871 (comment). The fix stores the full pointer (its deepcopy to avoid sharing that memory) in the mock instead. I needed to restructure the tests a little to allow adding a nil parameter testcase
CONTRIBUTING.md
Makefile
targetsMakefile
targetsREADME.md
todocs/dev/README.md
This is a companion PR to #869
I have omitted the
Installing CVO and operators in cluster
andUsing CVO to render the release-image locally
sections from the original README b/c I don't think these use-cases are too interesting when developing CVO. I have updated a section on building a custom release payload to build from an existing payload (instead if imagestream) and added a section that instructs how to inject such release payload to the cluster