-
-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
datree: test #84567
Conversation
Signed-off-by: Rui Chen <rui@chenrui.dev>
995680d
to
0755e21
Compare
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 $ datree version
0.9.0 |
Agree, looks like the CI did not catch anything with this commit, I have seen the same issue with |
got it, it's $ env -i PATH="$PATH" TERM="dumb" datree version
0.9.0
$ env -i PATH="$PATH" datree version
fatal error: unexpected signal during runtime execution |
Nice find. That is why CI failed catching it! |
given that, i can't think of how we could have realistically caught this. can you? |
yeah, I dont have any further idea, I am gonna close this PR for now. (feel free to reopen if you feel fit) |
test PR to reproduce datreeio/datree#160
relates to #84566