-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add cross-compilation to CI #131
Conversation
bae69c2
to
bf179e9
Compare
c939c72
to
f4d8bdb
Compare
e85a8d7
to
e4bf9b8
Compare
Updates the README to use cargo target config instead of RUSTFLAGS to avoid setting the linker for ebpf in cargo-in-cargo.
e4bf9b8
to
b336e09
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. A couple of questions that could do answering, but nothing that should block this merging.
@@ -3,86 +3,111 @@ | |||
set -eux | |||
|
|||
TEMPLATE_DIR=$1 | |||
if [ -z "${TEMPLATE_DIR}" ]; then echo "template dir required"; exit 1; fi | |||
if [ -z "${TEMPLATE_DIR}" ]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What tool did you use to reformat the shell script?
Perhaps this is something we might consider adding to CI later to ensure changes are consistently formatted
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just used vscode and didn't investigate what it used under the hood.
@@ -205,8 +205,9 @@ async fn main() -> anyhow::Result<()> { | |||
program.attach("{{tracepoint_name}}")?; | |||
{%- endcase %} | |||
|
|||
let ctrl_c = signal::ctrl_c(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why has this changed? I'm assuming it has something to do with the expect script and how we issue Ctrl+C in the tests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure it matters, but I realized while debugging things that there was a subtle race here - we were logging "waiting for ..." before actually setting up the signal handler.
Updates the README to use cargo target config instead of RUSTFLAGS to
avoid setting the linker for ebpf in cargo-in-cargo.