Skip to content

Conversation

@wking
Copy link
Member

@wking wking commented Aug 27, 2018

Cover these directories, which are new with openshift/installer#120.

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 27, 2018
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 27, 2018
@wking wking force-pushed the installer-lint-root-pkg-directory branch from 707920d to a69bc01 Compare August 27, 2018 18:30
Copy link
Contributor

@stevekuznetsov stevekuznetsov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor comments - other approaches may require fewer tweaks in the future.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not ./... ?

Copy link
Member Author

@wking wking Aug 27, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not ./... ?

We are currently leaning on Go's test framework for smoke tests. We may drop those soon in favor of more e2e-aws coverage (#1271 is groundwork for this expansion), but until then we need to keep this job out of tests/smoke. A white-list like this is one way to do that.

There may also be blacklist approaches, but I think we'd need to include find in our invocation if we wanted to do that. Or maybe leaning on your go list suggestion?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not go list -f '{{ .Dir }}' ./... ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not go list -f '{{ .Dir }}' ./... ?

Something like that could work, although:

$ sudo hack/go-lint.sh $(go list -f '{{ .Dir }}' ./...)
import "/home/trking/.local/lib/go/src/github.com/openshift/installer/cmd/openshift-install": cannot import absolute path
...

It works with .ImportPath:

$ sudo hack/go-lint.sh $(go list -f '{{ .ImportPath }}' ./...)

How do I encode that in YAML here? Something like:

      - image: quay.io/coreos/golang-testing
        env:
        - name: IS_CONTAINER
          value: "TRUE"
        command:
        - sh
        args:
        - -c
        - ./hack/go-lint.sh $(go list -f '{{ .ImportPath }}' ./...)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect that PodSpec would work, yes

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect that PodSpec would work, yes

Updated with a69bc01 -> aaa039c.

@wking wking force-pushed the installer-lint-root-pkg-directory branch from a69bc01 to aaa039c Compare August 27, 2018 23:32
@stevekuznetsov
Copy link
Contributor

/lgtm
Will need a rebase

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 28, 2018
Cover ./pkg/... (and, for go-lint, ./cmd/...).  These directories are
new with openshift/installer@4e92db8 (Merge pull request openshift#120 from
staebler/asset_graph_engine, 2018-08-24, openshift/installer#120).

There's no particular reason to not run the Go unit tests on ./cmd/...
But we're unlikely to have unit tests there, and the old tests
restricted themselves to ./installer/pkg/..., so I've stuck with that
pattern here.

Steve recommended using 'go list ...' to run the lint commands [1].
We just want something that will give us our Go directories without
dropping down into the vendor directories.

[1]: openshift#1289 (comment)
@wking wking force-pushed the installer-lint-root-pkg-directory branch from aaa039c to 8f82768 Compare August 29, 2018 00:03
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Aug 29, 2018
@wking
Copy link
Member Author

wking commented Aug 29, 2018

Rebased around #1265 with aaa039c -> 8f82768.

@stevekuznetsov
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 29, 2018
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stevekuznetsov, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@openshift-merge-robot openshift-merge-robot merged commit ea04d2d into openshift:master Aug 29, 2018
@openshift-ci-robot
Copy link
Contributor

@wking: Updated the following 2 configmaps:

  • ci-operator-openshift-installer configmap using the following files:
    • key master.json using file ci-operator/config/openshift/installer/master.json
  • job-config configmap using the following files:
    • key openshift-installer-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-presubmits.yaml
Details

In response to this:

Cover these directories, which are new with openshift/installer#120.

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.

@wking wking deleted the installer-lint-root-pkg-directory branch August 29, 2018 16:13
derekhiggins pushed a commit to derekhiggins/release that referenced this pull request Oct 24, 2023
* Fix path to .openshift_install_state.json

Signed-off-by: Christoph Stäbler <[email protected]>

* Add help where xinetd config parameters can be found

Signed-off-by: Christoph Stäbler <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants