You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error that is provided is not reproducible on a local machine running Ubuntu Focal (20.04). If you installed erlang with apt on a fresh VPS. Specifically check lines 1064 to 1072 in the Travis job.
Linking the erl_interface is not an issue on any Debian or Darwin OS. If others could confirm, that would be great so we can debug this problem further.
Solution
For the time being, I've outright removed Travis CI from the project in the PR: #284
1. Build Kite
In the future we may want to look into an alternative. Build Kite may be a good solution as we get to setup and deploy our own machine to run CI tests.
In order to actually get this resolved, we would most definitely have to post an issue in the Travis CI forums as this type library linking issue can only be resolved by debugging and fixing their VM setup.
The text was updated successfully, but these errors were encountered:
Problem
I've been tinkering with Travis CI for a fair bit. And, quite frankly, I'm a bit confused as to why it refuses to compile on a Travis VM.
The following is the build script I used to compile the project with Travis:
You can review the logs for the failed compilation here: https://travis-ci.org/github/TheLoneRonin/arweave/jobs/752327803
The error that is provided is not reproducible on a local machine running Ubuntu Focal (20.04). If you installed
erlang
withapt
on a fresh VPS. Specifically check lines 1064 to 1072 in the Travis job.Linking the
erl_interface
is not an issue on any Debian or Darwin OS. If others could confirm, that would be great so we can debug this problem further.Solution
For the time being, I've outright removed Travis CI from the project in the PR: #284
1. Build Kite
In the future we may want to look into an alternative. Build Kite may be a good solution as we get to setup and deploy our own machine to run CI tests.
https://buildkite.com/
2. Post an issue in the Travis CI forums
In order to actually get this resolved, we would most definitely have to post an issue in the Travis CI forums as this type library linking issue can only be resolved by debugging and fixing their VM setup.
The text was updated successfully, but these errors were encountered: