-
Notifications
You must be signed in to change notification settings - Fork 891
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
"multirust run" different syntax? #5
Comments
Ah, somewhere along the way I lost the |
Thanks! |
djc
added a commit
that referenced
this issue
Jun 18, 2024
# This is the 1st commit message: Port cli_inst_interactive to CliTestContext # The commit message #2 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #3 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #4 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #5 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #6 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #7 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #8 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #9 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #10 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #11 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #12 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #13 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #14 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #15 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #16 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #17 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #18 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #19 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #20 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #21 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #22 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #23 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #24 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #25 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #26 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #27 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #28 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #29 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #30 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #31 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #32 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #33 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #34 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #35 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #36 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #37 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #38 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #39 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext # The commit message #40 will be skipped: # fixup! Port cli_inst_interactive to CliTestContext
djc
added a commit
that referenced
this issue
Jun 18, 2024
# This is the 1st commit message: Port cli_misc to CliTestContext # The commit message #2 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #3 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #4 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #5 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #6 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #7 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #8 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #9 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #10 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #11 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #12 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #13 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #14 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #15 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #16 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #17 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #18 will be skipped: # fixup! Port cli_misc to CliTestContext # The commit message #19 will be skipped: # fixup! Port cli_misc to CliTestContext
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For example:
It looks like it's trying to interpret
stable
as the binary to run?The text was updated successfully, but these errors were encountered: