-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
safer example runner #13084
Comments
cc @phlax |
hi @ronaldpetty apologies for this. I originally wrapped this test in a docker-in-docker container partly for this reason. the wrapper wasnt added to the ci pipeline - but im thinking to add at least some documentation to make it easy to run these tests in an isolated way |
Hi @phlax, not a problem, I am new here :).
Happy to help if you have something at some point! Maybe close for now?
…On Mon, Sep 14, 2020 at 11:29 AM phlax ***@***.***> wrote:
hi @ronaldpetty <https://github.com/ronaldpetty> apologies for this.
I originally wrapped this test in a docker-in-docker container partly for
this reason.
the wrapper wasnt added to the ci pipeline - but im thinking to add at
least some documentation to make it easy to run these tests in an isolated
way
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13084 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKTOY2X3W4TK2V7O7OQQTTSFZOJ5ANCNFSM4RLZIGJA>
.
|
lets keep it open until i add the relevant docs |
@ronaldpetty thinking about this further - im realising its an issue just running a single Im gonna PR so it prunes in ci as required, but not when you run individual tests |
That sounds right. I was digging into examples and still trying to see how
to run them.
…On Mon, Sep 14, 2020 at 11:50 AM phlax ***@***.***> wrote:
@ronaldpetty <https://github.com/ronaldpetty> thinking about this further
- im realising its an issue just running a single verify.sh script.
Im gonna PR so it prunes in ci as required, but not when you run
individual tests
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13084 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKTOY4A735LSNVUJZ3RHMTSFZQYVANCNFSM4RLZIGJA>
.
|
after testing this further, it turns out that the prune isnt required at all. |
Title: safer example runner
Description:
The text was updated successfully, but these errors were encountered: