build system enhancements; make Travis do more stuffs #193

New issue

Open

opened 2018-08-20 18:19:19 +02:00 by BrannonKing · 4 comments

BrannonKing commented

2018-08-20 18:19:19 +02:00

(Migrated from github.com)

Includes:

Move "secrets" out of .travis.yml and into Travis variables.
Make the Windows run of the unit tests work. (It's now running with a Wine Docker image, which is working okay, but it's probably not ideal.)
Add in a run of the python integration tests and the fuzzy tests.
Can we use newer compilers with the older GLIBC?
Publish a debug build for Linux?
Validate the static linking as part of the build.
Produce a snap and flatpak output (with SHAs of them)
Report code complexity on all files with claim in the name.
Run the unit tests on Alpine and Fedora docker images.

Includes: 1. Move "secrets" out of .travis.yml and into Travis variables. 2. Make the Windows run of the unit tests work. (It's now running with a Wine Docker image, which is working okay, but it's probably not ideal.) 3. Add in a run of the python integration tests and the fuzzy tests. 4. Can we use newer compilers with the older GLIBC? 5. Publish a debug build for Linux? 6. Validate the static linking as part of the build. 7. Produce a snap and flatpak output (with SHAs of them) 8. Report code complexity on all files with claim in the name. 9. Run the unit tests on Alpine and Fedora docker images.

bvbfan commented

2018-08-30 15:29:41 +02:00

(Migrated from github.com)

For 4, i'm using 7.3 with boost 1.66, project is still not compilable without a patch (boost changes), but you should wait to upstream merge, i can help you on that point. Also build with different boost should be noted as 6, maybe, because it has some changes time to time.
For 3, 18.04 LTS will be good enough, i can make other script to build on non-Debian environment (as i use Arch, i perform autogen and configure by hand cause script is Ubuntu/Debian specific) or we can switch entirely on CMake, which will be good for all distros.

For 4, i'm using 7.3 with boost 1.66, project is still not compilable without a patch (boost changes), but you should wait to upstream merge, i can help you on that point. Also build with different boost should be noted as 6, maybe, because it has some changes time to time. For 3, 18.04 LTS will be good enough, i can make other script to build on non-Debian environment (as i use Arch, i perform autogen and configure by hand cause script is Ubuntu/Debian specific) or we can switch entirely on CMake, which will be good for all distros.

BrannonKing commented

2019-05-08 23:30:19 +02:00

(Migrated from github.com)

The functional tests should run as part of the "quality" stage of the build. It should run the test/functional/test_runner.py, test/lint/all, and test/util/*.py

BrannonKing commented

2019-05-13 23:24:36 +02:00

(Migrated from github.com)

find . -name '*.py' -exec sed -i "s/bitcoind/lbrycrdd/g" {} +
find . -name '*.py' -exec sed -i "s/BITCOIN/LBRYCRD/g" {} +
find . -name '*.py' -exec sed -i "s/bitcoin\.conf/lbrycrd\.conf/g" {} +

However, I think the second sed messes up the configure.ac correspondence.

A word of warning on the functional tests before I forget: I think that the vars in the config.ini.in correspond to vars in configure.ac . I ran through some of the functional tests today; I had to do quite a bit of bitcoin renaming and port updating (search 8332) to make it work. ``` find . -name '*.py' -exec sed -i "s/bitcoind/lbrycrdd/g" {} + find . -name '*.py' -exec sed -i "s/BITCOIN/LBRYCRD/g" {} + find . -name '*.py' -exec sed -i "s/bitcoin\.conf/lbrycrd\.conf/g" {} + ``` However, I think the second sed messes up the configure.ac correspondence.

BrannonKing commented

2020-03-25 20:46:14 +01:00

(Migrated from github.com)

At the moment, items 2, 3a, and 4 of the original list have been done.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#193

No description provided.