Open leet4tari opened 3 months ago
0 tests 0 :white_check_mark: 0s :stopwatch: 0 suites 0 :zzz: 0 files 0 :x:
Results for commit 1fbc9ec0.
:recycle: This comment has been updated with latest results.
3 files 129 suites 38m 55s :stopwatch: 1 303 tests 1 303 :white_check_mark: 0 :zzz: 0 :x: 3 904 runs 3 904 :white_check_mark: 0 :zzz: 0 :x:
Results for commit 1fbc9ec0.
:recycle: This comment has been updated with latest results.
Still have a dependancy on ring v0.16
, which does not support linux-risv64 nor windows-arm64.
ring v0.16.20
└── trust-dns-proto v0.23.2
└── trust-dns-client v0.23.2
└── tari_p2p v1.0.0-pre.15
Switching to rebranded Hickory DNS when PR https://github.com/hickory-dns/hickory-dns/pull/2217 is merged, should drop the dependancy on ring v0.16
.
Progress update: PR - https://github.com/hickory-dns/hickory-dns/pull/2217 has been merged - awesome! Awaiting the next release of hickory-dns, which looks to be about to happen.
Currently been tracked in https://github.com/hickory-dns/hickory-dns/issues/2206
Once that is in place, we can further update and see what else needs work.
Description Progress toward builds for linux riscv64 and windows arm64, which currently fail on ring 0.16
Motivation and Context Add more build options
How Has This Been Tested? Builds locally, with updated deps, but still not rsicv/win-arm64 support. Docker arm64 breakage, still investigating.
What process can a PR reviewer use to test or verify this change?
Breaking Changes