Skip to content
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

ci: The binary built during the release workflow is not working on the server #21

Closed
khorolets opened this issue Feb 17, 2022 · 2 comments
Assignees
Milestone

Comments

@khorolets
Copy link
Member

We assume there is some system dependency related to RocksDB that is not present in our CI build environment that causes the problems.

Also, the upgrade of RocksDB on nearcore side has been reverted, and perhaps we need to try the release after that in case there is any connection with wrong/missing dependency and our binary not working.

@khorolets khorolets self-assigned this Feb 17, 2022
@khorolets khorolets added this to the MVP Release milestone Feb 17, 2022
@frol
Copy link
Contributor

frol commented Feb 17, 2022

Also, the upgrade of RocksDB on nearcore side has been reverted, and perhaps we need to try the release after that in case there is any connection with wrong/missing dependency and our binary not working.

While that could have been an issue, given that the same near-lake code being compiled in another environment works fine, I feel that these might be unrelated.

@khorolets
Copy link
Member Author

Without any changes in this regard from the side of NEAR Lake, the release workflow produces the working binary. I've just testnet it on ci/release-check branch with TEST-0.0.0 release.

I'm closing it for now. We can reopen if needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants