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

TRT-1834: initial version of openshift-tests-extension #2

Merged
merged 2 commits into from
Oct 2, 2024

Conversation

stbenjam
Copy link
Contributor

@stbenjam stbenjam commented Sep 5, 2024

Initial implementation of openshift/enhancements#1676.

Requires enhancements to our forked ginkgo openshift/onsi-ginkgo#15

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 5, 2024
@openshift-ci openshift-ci bot requested review from deads2k and jupierce September 5, 2024 20:47
Copy link

openshift-ci bot commented Sep 5, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stbenjam

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 5, 2024
cmd/example-tests/main.go Outdated Show resolved Hide resolved
cmd/example-tests/types.go Outdated Show resolved Hide resolved
@stbenjam stbenjam changed the title [wip] Basic example POC [wip] Implementation of enhancement Sep 24, 2024
pkg/cmd/cmdlist/list.go Outdated Show resolved Hide resolved
@stbenjam stbenjam changed the title [wip] Implementation of enhancement TRT-1834: Implementation of enhancement Sep 30, 2024
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 30, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 30, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 30, 2024

@stbenjam: This pull request references TRT-1834 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

Initial implementation of openshift/enhancements#1676.

Requires enhancements to our forked ginkgo openshift/onsi-ginkgo#15

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 openshift-eng/jira-lifecycle-plugin repository.

@stbenjam
Copy link
Contributor Author

stbenjam commented Oct 1, 2024

/hold

Want to clean up commit history before we merge anything

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 1, 2024
Dockerfile Outdated Show resolved Hide resolved
Dockerfile Outdated Show resolved Hide resolved
hack/go-lint.sh Outdated Show resolved Hide resolved
pkg/cmd/cmdrun/run.go Outdated Show resolved Hide resolved
pkg/extensions/extension.go Outdated Show resolved Hide resolved
pkg/extension/registry.go Outdated Show resolved Hide resolved
pkg/extension/extensiontests/types.go Outdated Show resolved Hide resolved
pkg/extension/extensiontests/spec.go Outdated Show resolved Hide resolved
Name string `json:"name"`
Lifecycle Lifecycle `json:"lifecycle"`
Duration int64 `json:"duration"`
StartTime *time.Time `json:"startTime"`
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we marshal into a format bigquery can ingest directly without parsing; e.g. 2020-06-02 23:57:12.120174 UTC. In the ultimate aggregated format output from origin, I think we would want it in the directly ingestible format. Changing between timezones and date formats between run-tests and the aggregated format could confuse end-users.

Copy link
Contributor Author

@stbenjam stbenjam Oct 2, 2024

Choose a reason for hiding this comment

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

Hopefully I did this right, it matches your format:

{
    "name": "[sig-testing] openshift-tests-extension should support passing tests",
    "lifecycle": "blocking",
    "duration": 1,
    "startTime": "2024-10-02 17:33:50.089649 UTC",
    "endTime": "2024-10-02 17:33:50.091001 UTC",
    "result": "passed",
    "output": "",
    "error": "",
    "details": null
  },

pkg/extension/extensiontests/spec.go Outdated Show resolved Hide resolved
@stbenjam stbenjam force-pushed the example branch 2 times, most recently from 685e661 to ddd291f Compare October 2, 2024 16:13
@stbenjam stbenjam changed the title TRT-1834: Implementation of enhancement TRT-1834: initial version of openshift-tests-extension Oct 2, 2024
Vendoring the deps since our openshift golang image wants it.
@jupierce
Copy link
Contributor

jupierce commented Oct 2, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 2, 2024
@stbenjam
Copy link
Contributor Author

stbenjam commented Oct 2, 2024

/hold cancel

@stbenjam
Copy link
Contributor Author

stbenjam commented Oct 2, 2024

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 2, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit cabe07f into openshift-eng:main Oct 2, 2024
1 check passed
@stbenjam stbenjam deleted the example branch October 2, 2024 19:45
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants