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

datree: test #84567

Closed
wants to merge 1 commit into from
Closed

datree: test #84567

wants to merge 1 commit into from

Conversation

chenrui333
Copy link
Member

test PR to reproduce datreeio/datree#160

relates to #84566

@chenrui333 chenrui333 added the CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. label Sep 3, 2021
@BrewTestBot BrewTestBot added the go Go use is a significant feature of the PR or issue label Sep 3, 2021
Signed-off-by: Rui Chen <rui@chenrui.dev>
@branchvincent
Copy link
Member

so they pass, and this is what I observe locally:

$ git -C $(brew --repo) checkout 6d2a2960fcdf5550fda796c67e283c98376ef607
$ git -C $(brew --repo homebrew/core) checkout d7ba094baa2de34a34e2fcbbb08ca7371955bfb1
$ brew install datree
$ brew test datree
==> Testing datree
==> /usr/local/Cellar/datree/0.9.0/bin/datree test /private/tmp/datree-test-20210902-40849-sas8y0/invalidK8sSchema.yaml 2>&1
==> /usr/local/Cellar/datree/0.9.0/bin/datree version
$ datree version
fatal error: unexpected signal during runtime execution
...

It has something to do with the environment in the test runner that does not reproduce this. I can even put a system "false" in the test block, run brew test --debug datree, drop into a shell and observe:

$ datree version
0.9.0

@chenrui333
Copy link
Member Author

Agree, looks like the CI did not catch anything with this commit, I have seen the same issue with datree and datree version

@branchvincent
Copy link
Member

got it, it's TERM=dumb that does not repro this:

$ env -i PATH="$PATH" TERM="dumb" datree version
0.9.0
$ env -i PATH="$PATH" datree version
fatal error: unexpected signal during runtime execution

@chenrui333
Copy link
Member Author

Nice find. That is why CI failed catching it!

@branchvincent
Copy link
Member

given that, i can't think of how we could have realistically caught this. can you?

@chenrui333
Copy link
Member Author

yeah, I dont have any further idea, I am gonna close this PR for now. (feel free to reopen if you feel fit)

@chenrui333 chenrui333 closed this Sep 3, 2021
@github-actions github-actions bot added the outdated PR was locked due to age label Oct 4, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 4, 2021
@chenrui333 chenrui333 deleted the datree-test branch December 18, 2022 06:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. go Go use is a significant feature of the PR or issue outdated PR was locked due to age
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants