All tenancies get the first 3,000 OCPU hours and 18,000 GB hours per month for free for VM instances using the VM.Standard.A1.Flex shape, which has an Arm processor. For Always Free tenancies, this is equivalent to 4 OCPUs and 24 GB of memory.
It will just shutdown 2/3 of the way through the month
If you mean my scripts I don’t think so. It uses the same Cargo dependencies as the Marriage builds, but ensures you have the Ubuntu packages that you need and automates the steps to build and install the binaries.
You’re cross compiling, specifying a target, so that may affect the difference and override the build settings. If you’re on an arm processed you don’t need to do that, so that’s probably the difference.
Like, do these binaries work?
Specifically armv7 and aarch64.
I was busy helping someone installing manjaro linux on the raspberry at the time of writing the post and I’m going to sleep soon.
@dirvine said in another thread that there a a load of PRs incoming and not to waste our time on these latest releases. I read that as they are “releases” only in the sense that they are logical breakpoints in the fast-moving development process right now and of use only to monitor progress internally. I bet there is a much more elegant way of putting that…
I’ve been working on providing the builds for ARM. I’ve submitted a PR to resolve the issue raised by @folaht , so the Aarch64 build will be available shortly.
Since some people were asking, I just wanted to provide some info on these builds.
They’ve been built using the cross project, which very nicely uses Docker containers to wrap all the tedious configuration for cross compilation. In terms of testing, the sn_node ARM builds pass a large subset of the tests defined in the safe_network repo. Of the tests that didn’t pass, most of the failures were actually due to the configuration of the containers used by cross in the test run. We’ll definitely be able to fix those. The other tests that didn’t pass were ‘prop’ tests that are very CPU intensive and were just taking a very long time to run with the limited container resources.
There have been no tests on actual ARM hardware yet, but in the coming days, I’m going to test and run the builds on a Raspberry Pi 4.
If you please feedback any findings or issues with the builds in this thread, I’ll be happy to assist in any way I can. I’ll be checking the forum regularly from now on and look forward to hearing from anyone who’s interested.
Sure thing, it would help us a lot. So running baby fleming may bee too much for odroid, but we have not tried it yet. As we cut out more inefficiencies then it’s worth a try.
We are just updating cli etc. let’s see if @joshuef and @chriso have some input (although Josh is ODD today (supposed to be)) and Chris finished after midnight last night. So may be a wee while to reply.
Thanks for the feedback. I’ll see if I can reproduce this on my own Pi later today. I’ll definitely get back to you, but it may not be today. We’ll keep track of the issue.