Summary:
The breakage has been fixed, so bring back the manifest, but only the Linux one, because the Mac version is failing due to another issue.
Also to make it easier to debug issues on GitHub Actions separate out the dependencies build from Mononoke and rust-shed builds.
Reviewed By: krallin
Differential Revision: D21448412
fbshipit-source-id: 68d89c858d1692727a7fd66bca114920e6dfb4dc
Summary:
Due to the Mononoke LFS server only being available on FB's network, the tests
using them cannot run outside of FB, including in the github workflows.
Reviewed By: quark-zju
Differential Revision: D20698062
fbshipit-source-id: f780c35665cf8dc314d1f20a637ed615705fd6cf
Summary:
These were originally generated by getdeps, but since they
have been manually modified they are no longer regeneratable via
the getdeps tooling.
Simplify and just call the getdeps build rather than replicating
the discrete project fetches: they aren't required to break out
separately it just looks nice in the CI output--they will be fetched
on demand during the build anyway.
Reviewed By: simpkins
Differential Revision: D20660208
fbshipit-source-id: b6c63333e842d2bd1ba2fb574f8f082dcefef89e
Summary:
Ensure that we are referencing python3 in the paths
that we generate for the github actions workflows, and remove
some shebangs that influence how our internal linters process
the python code.
Reviewed By: fanzeyi
Differential Revision: D20659747
fbshipit-source-id: 6f300f8e91edf7701bb27babc7b1418958cf0a10
Summary:
Similar to the Mononoke CI, run tests on the open-source version of the Rust crates.
Crates that do not build are commented out with reasons.
`target-dir` is explicitly set so all crates share a single build cache.
This helps us capture issues with wrong versions specified in `Cargo.toml`, since
internally we use vendored crates, while externally `crates.io` is used.
Reviewed By: sfilipco
Differential Revision: D20376183
fbshipit-source-id: 8cf4df0c893c1119e07f950eaf398313e2efcc25
