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

WIP: Mirror alberto pr #2

Closed
wants to merge 4 commits into from

Conversation

ingvagabund
Copy link
Member

DO NOT MERGED, just for debugging purposes

@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jan 30, 2019
@ingvagabund
Copy link
Member Author

/test unit

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ingvagabund

If they are not already assigned, you can assign the PR to them by writing /assign @ingvagabund in a comment when ready.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ingvagabund
Copy link
Member Author

/test unit

@ingvagabund
Copy link
Member Author

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 30, 2019
@ingvagabund
Copy link
Member Author

/test unit

4 similar comments
@ingvagabund
Copy link
Member Author

/test unit

@ingvagabund
Copy link
Member Author

/test unit

@ingvagabund
Copy link
Member Author

/test unit

@ingvagabund
Copy link
Member Author

/test unit

@ingvagabund
Copy link
Member Author

Sometimes when I run the unit tests locally I see:

=== RUN   TestReconcile
E0130 15:09:25.997322   14974 controller.go:294] Unable to retrieve Machineset default/foo-74564b8d5f from store: MachineSet.machine.openshift.io "foo-74564b8d5f" not found
--- FAIL: TestReconcile (300.58s)
    machinedeployment_controller_test.go:146: timed out waiting reconcile error

I have suspicion there are no machinesets at all so the machine deployment actually does not lead to creation of machine sets. Still dunno why.

@ingvagabund
Copy link
Member Author

/test unit

1 similar comment
@ingvagabund
Copy link
Member Author

/test unit

@ingvagabund
Copy link
Member Author

/test unit

@ingvagabund
Copy link
Member Author

/test unit

…h MS is new/old

The CreationTimestamp is not always the referential value for comparision.
The time.Time.Before method does not always return true when it should.
Leading to new and old MSs to be selected in an oposite way.
Using the RevisionVersion for comparision is more precise and it solves
the case where CreationTimestamp fields of both MSs has the same value.

From observation the following machineset CreationTimestamps led to incorrect ordering of MSs:
item[0]: ResourceVersion:"78", CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:63684460660, loc:(*time.Location)(0x2cb5040)}}
item[1]: ResourceVersion:"82", CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:63684460661, loc:(*time.Location)(0x2cb5040)}}

Even though item[1]'s ext field has higher value than item[0]'s ext field,
item[1] was selected by time.Time.Before as old MS instead of new one.
@ingvagabund
Copy link
Member Author

/test unit

3 similar comments
@ingvagabund
Copy link
Member Author

/test unit

@ingvagabund
Copy link
Member Author

/test unit

@ingvagabund
Copy link
Member Author

/test unit

@ingvagabund
Copy link
Member Author

/refresh
/test unit

@ingvagabund
Copy link
Member Author

/test unit

@enxebre
Copy link
Member

enxebre commented Jan 31, 2019

/test all

@openshift-ci-robot
Copy link

@ingvagabund: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/unit 6867c29 link /test unit

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

@paulfantom paulfantom mentioned this pull request Feb 4, 2019
@enxebre
Copy link
Member

enxebre commented Feb 4, 2019

closing in favour of #7

@enxebre enxebre closed this Feb 4, 2019
@ingvagabund ingvagabund deleted the mirror-alberto-pr branch February 5, 2019 10:32
RadekManak pushed a commit to RadekManak/cluster-api that referenced this pull request Oct 31, 2024
* Introduce CEL for ClusterClass Variables

Signed-off-by: chaunceyjiang <[email protected]>

* feat: Implement CEL validation

* refactor: Add comments from previous code reviews

* chore: Generate CC manifest after fixing list type annotation (openshift#2)

* chore: Fix up CRD manifest

* fix: Pass through context to CEL funcs

* feat: Add CEL admission cost validation

* refactor: Add nolint to unbounded

* refactor: Fix up new func signature

* build: Fix up go mod for tools

* fixup! refactor: Apply review feedback

* fixup! build: Regenerate openapi spec

* fixup! refactor: Apply review feedback

* fixup! fix: Regenerate everything

* fixup! fix: Apply review feedback

* fixup! fix: More review feedback

* fixup! refactor: Address review feedback, especially re recursion

* fixup! fix: Check total cost

* fixup! refactor: Address review feedback - rename testCtx to ctx

* CEL: Various improvements (openshift#3)

* resolve compile issue after rebase

* Some more improvements (openshift#4)

---------

Signed-off-by: chaunceyjiang <[email protected]>
Co-authored-by: Jimmi Dyson <[email protected]>
Co-authored-by: Jimmi Dyson <[email protected]>
Co-authored-by: Stefan Büringer <[email protected]>
Co-authored-by: Stefan Bueringer <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants