-
Notifications
You must be signed in to change notification settings - Fork 177
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
ARM support for AWS Graviton v2, v3 #1556
Comments
@jjo if you still have the environment available could you test with Kepler v0.7.11? |
I had replicated this with a graviton node. Let me see if I can do it again with 0.7.11 |
awesome, lemme check and report back |
It feels like it gets further, but still crashes:
This is using a |
Running again with debug logs... |
Logs again with log level 5:
|
woOT!, running ok so far:
More details re:running instance:
|
Ahh geezz... Just realized I'm still running 0.7.10.. Sorry for the noise. Let me update and I'll let you know |
No worries I was about to say "those look like 0.7.10 logs" 🤣 |
Sorry for the short term panic! Good news! 0.7.11 is no longer crashing on my graviton node, too! |
Given that things aren't crashing I'm going to go ahead and close this one for now. |
Hey, just wanted to follow up on this thread. When you are saying no crashes, are y'all able to get information (valid sustainability metrics like power consumption, carbon emissions, etc.) from Kepler? Do they seem valid and how do the results look like? Thanks! |
What would you like to be added?
ARM support for AWS Graviton v2, v3
Why is this needed?
Expanding Kepler support to more ARM architectures will be very beneficial, else we'd be subsetting our energy observability features to x64 -only, especially for commonly used architectures in some cloud providers: for AWS these are GravitonV2 for the
𝑥6g...
(c6g
,m6g
, etc) and GravitonV3 for𝑥7g...
(c7g
,m7g
, etc).Worth noting previous issue at #482 (comment).
I tried deploying
kepler-0.7.10
on anm6g
instance with below details:It crashed with the below log tail (full log at https://0x0.st/XTMr.txt):
/cc @nikimanoledaki
The text was updated successfully, but these errors were encountered: