-
Notifications
You must be signed in to change notification settings - Fork 43
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
Process trace not displaying #79
Comments
I'm having a look into why this isn't working I was looking into it this weekend and it seems the binaries use eBPF to plug into the linux kernel using something like this: I'll see if i can make a working ebpf based snooper and i will opensource it when i succeed and fork this project to use them. But i can't really give a deadline for this since its purely out of curiosity i try to implement this. I suspect ideally in a CI/CD platform something like Pyroscope or parca should be build in to do the profiling. But sadly the metrics out of github actions is very limited and its even hard to trace if your builds are slowing down. |
I've now made a process tracer which logs the commands in json to the output: https://github.com/borissmidt/proc-tracer But now i still have to test this thing on a github actions runner and update this repo to parse the output of the command. |
I've got it to work on a fork. |
Duplicate of: #71 |
Hi I have added this action with the following configuration:
And the job executes well and displays in the workflow summary. However the process trace doesn't display at all:
Any ideas on what I can try to fix? I have already tried setting a lower
proc_trace_chart_max_count
, but with no difference in result.The text was updated successfully, but these errors were encountered: