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

Support wait-for-data timeout #237

Merged
merged 3 commits into from
Oct 19, 2021
Merged

Conversation

mtojek
Copy link
Contributor

@mtojek mtojek commented Oct 19, 2021

What does this PR do?

Why is it important?

Checklist

Related issues

@mtojek mtojek self-assigned this Oct 19, 2021
@elasticmachine
Copy link

elasticmachine commented Oct 19, 2021

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2021-10-19T16:16:32.603+0000

  • Duration: 4 min 41 sec

  • Commit: 3683122

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@mtojek mtojek requested a review from jsoriano October 19, 2021 12:54
@@ -8,3 +8,7 @@ spec:
properties:
skip:
$ref: "./../skip.spec.yml#/definitions/skip"
wait_for_data_timeout:
description: Short explanation for why test has been skipped.
Copy link
Member

Choose a reason for hiding this comment

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

Umm, this description is unrelated? 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

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

My bad, copied this structure from the "skip" definition.

@@ -8,3 +8,7 @@ spec:
properties:
skip:
$ref: "./../skip.spec.yml#/definitions/skip"
wait_for_data_timeout:
description: Short explanation for why test has been skipped.
type: string
Copy link
Member

Choose a reason for hiding this comment

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

Q: Are types defined somewhere? Would it be possible to define a duration type for this strings?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Unfortunately not, these are parts of the JSON schema, not really a Go type.

I think we could improve it with semantic validation (parse its format).

@mtojek mtojek requested a review from jsoriano October 19, 2021 16:17
@mtojek mtojek merged commit bae3059 into elastic:master Oct 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants