search

devimur2021 / Sentiment-Based-Product-Recommendation-System

Sentiment based product recommendation system
0 stars 0 forks source link

GitHub does not provide support for linuxppc self hosted runner #1

Open devimur2021 opened 5 months ago

devimur2021 commented 5 months ago

GitHub does not provide support for linuxppc self hosted runner. Our products have support for powerpc, can you suggest how do we go about.

Here are couple of issue raised in community regarding support of powerpc.

Support for PowerPC and Z series CPU architectures · Issue #296 · actions/runner (github.com)

Support self-hosted runner on linux-ppc64le platform · Issue #2365 · actions/runner (github.com) (PR is raised for it but seems dead)

pmartindev commented 5 months ago

Hi @devimur2021, looks like I have access to the board now. Could you describe to me what kind of workflows you would be running on PowerPC runners? Could you provide some examples of what particular jobs you have that require PowerPC that can't be ran on other architectures? Is this for builds with compilation, integration testing, etc.

devimur2021 commented 5 months ago

Hi @pmartindev , we will build, run regression testing, Binary compatible OS testing on power PC

snps-davidla commented 5 months ago

Also Container builds, 3rdparty/OSS tool builds, etc.

Essentially everything.. we support our shrink-wrapped product deliveries on PPC platform for significant chip design customers like IBM who use our products to design chips like PPC.

pmartindev commented 5 months ago

Has the team tried installing the runner agent onto any PPC hosts? I would be curious what types of errors you would get? We've had customers install the agent on AWS Linux, and while it's not officially supported is still fully functional.

snps-davidla commented 5 months ago

How would we download it to install it?

We certainly would have tried that by now given the opportunity, but...

image

snps-davidla commented 5 months ago

Oh, I think I understand the disconnect.. It's not just a kernel/glibc compatibility issue, PowerPC is an entirely different CPU architecture. It would require a completely separate build to do anything at all.

The kinds of errors are "bad ELF interpreter" (trying to run a binary built for a different platform without emulation):

[synadmin@ppc64le_container actions-runner]$ ./config.sh --url https://snpsgithub-dev.internal.synopsys.com/snps-platform/ci-cd --token [...]
./config.sh: ./bin/Runner.Listener: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory
[synadmin@ppc64le_container actions-runner]$
pmartindev commented 5 months ago

Ah thanks for the context @snps-davidla, apologies I'm not familiar with PPC 😅 Have you tried any type of PPC emulation? Is that feasible for your workloads? I'm not sure what that space looks likes for PPC or if that is even possible, but just trying to understand what's feasible or not.

snps-davidla commented 5 months ago

There are potential workarounds we could implement with emulation, and from the linked issues we could probably manage to build dotnet core and the runner ourselves as well.

We're really looking for a supported solution though, something worthy of "Enterprise".

igorcosta commented 1 month ago

@snps-davidla I've tried to create a custom runner that supports CentOS, the biggest problem is relying on the triggering that CentOS does and the crontab might be an issue.

So, @devimur2021 I might have to default to the standard client for the local runner.

igorcosta commented 1 month ago

This is a major blocker for Synopsis for their SDLC cycle on internal software that are built on PowerPC.