Local/Remote Execution environment

[partouf]

First working version

This is part 1 of many for #6379

Changed in this PR:

• Move User Executable Execution into it's own independent thing
• Stored some extra things in buildResult so execution can work without knowledge of the compiler
• Be able to use a Hash and some JSON to execute

This so that later:

• We can add and use a Remote Execution Environment that pushes to a remote machine instead of directly executing (queues etc, see [REQUEST]: Remote execution on different architectures #6379)
• The remote machine and architecture can run the executable and return the results

Will comment out the API Endpoint before merging of course

[partouf]

Took more refactoring then I had hoped, but I'm happy with the end-result

[partouf]

How I tested this:

1. Build executable with regular CE with debug on
2. Copy paste the hash for the cached executable (123abc_exec hash)
3. Use the hash on script below:

#!/bin/sh

get_post_json() {
	cat <<'EOF'
{
	"ExecutionParams": {
		"args": ["Hello", "args!"],
		"stdin": "Hello stdin!",
		"runtimeTools": [
			{
				"name": "env",
				"options": [
					{
					"name": "PETE",
					"value": "Hello123"
					}
				]
			},
			{
				"name": "heaptrack",
				"options": [
					{
						"name": "details",
						"value": "stderr"
					},
					{
						"name": "graph",
						"value": "yes"
					}
				]
			}
		]
	}
}
EOF
}

POSTJSON=$(get_post_json)

echo $POSTJSON | jq

curl -s "http://127.0.0.1:10240/api/localexecution/$1" -H "Accept: application/json" -H "Content-type: application/json" -d "$POSTJSON" | jq

[mattgodbolt]

...will comment out the API endpoint

Maybe make it a configuration option (default off, naturally).

[mattgodbolt]

Remarkably little change to get this I see (mostly code motion), nice work. Discussing more in person.

[mattgodbolt]

Nice

[partouf]

Breaks Heaptrack Graph in Cmake + Execution https://godbolt.org/staging/z/zz6M7TWqx
(works on prod)

[partouf]

F# execution broken https://godbolt.org/staging/z/W3nazK8oc

[partouf]

Breaks Heaptrack Graph in Cmake + Execution https://godbolt.org/staging/z/zz6M7TWqx (works on prod)

The artifacts here moved from the root of the result object to execResult

This is not super-wrong and it might be better in case of situations where you want both build and execution artifacts.

So I'll add a thing to the frontend instead of changing it back.

[partouf]

fixed the broken things

[dkm]

Not really sure if there's anything to test here... but still, this is live :)

[partouf]

Not really sure if there's anything to test here... but still, this is live :)

Thanks! (technically it should just not break anything :) and I've tested it well enough that I'm not expecting any issues)