Post Collect Telemetry Failed

[moficodes]

Hey There,

The post action failed with following error. Any idea what might be causing this?

[Workflow Telemetry] Getting process tracer result from file /home/runner/actions-runner/_work/_actions/catchpoint/workflow-telemetry-action/v1/dist/proc-tracer/proc-trace.out ...
Error: [Workflow Telemetry] Unable to report process tracer result
Error: [Workflow Telemetry] Error
Error: Error: ENOENT: no such file or directory, open '/home/runner/actions-runner/_work/_actions/catchpoint/workflow-telemetry-action/v1/dist/proc-tracer/proc-trace.out'
[Workflow Telemetry] Reporting all content ...
Error: [Workflow Telemetry] Resource not accessible by integration

@jmhbnz FYI.

[moficodes]

Update. The post actually worked. But the error is there. Is that expected?

[jmhbnz]

Looks like this could be related to #21.

[cpuguy83]

Came across this action and hit this.
Curious why not write to $GITHUB_STEP_SUMMARY?

[cpuguy83]

Oh yeah I guess it did actually write to the summary but hit this error.

[serkan-ozal]

Hi @moficodes, it seems that the problem is caused by failed process tracer eBPF program internally used by this action to trace process activities from kernel level. Are you using this action on a self hosted runner?

[serkan-ozal]

@moficodes is it also possible to run workflow with debug logs enabled and then share the debug logs?

[massongit]

workflow-telemetry-action/src/processTracer.ts

Lines 78 to 95 in f974e0c

	const child: ChildProcess = spawn(
	'sudo',
	[
	path.join(__dirname, `../proc-tracer/${procTracerBinaryName}`),
	'-f',
	'json',
	'-o',
	procTraceOutFilePath
	],
	{
	detached: true,
	stdio: 'ignore',
	env: {
	...process.env
	}
	}
	)
	child.unref()

I think the above code causes this error if we run this action with a ARM64 self hosted runner, since the binaries in https://github.com/catchpoint/workflow-telemetry-action/tree/master/dist/proc-tracer are for AMD64.

[massongit]

@serkan-ozal @rwxdash

workflow-telemetry-action/src/processTracer.ts

Lines 78 to 95 in f974e0c

	const child: ChildProcess = spawn(
	'sudo',
	[
	path.join(__dirname, `../proc-tracer/${procTracerBinaryName}`),
	'-f',
	'json',
	'-o',
	procTraceOutFilePath
	],
	{
	detached: true,
	stdio: 'ignore',
	env: {
	...process.env
	}
	}
	)
	child.unref()

Is it possible to build the binaries in https://github.com/catchpoint/workflow-telemetry-action/tree/master/dist/proc-tracer on ARM64 as well as AMD64 and switch them running above depending on the runner's architecture?

[massongit]

@serkan-ozal @rwxdash Is it possible for you to do #53 (comment) ?