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: Add valgrind run #17725

Merged
merged 1 commit into from
Dec 17, 2019
Merged

ci: Add valgrind run #17725

merged 1 commit into from
Dec 17, 2019

Conversation

maflcko
Copy link
Member

@maflcko maflcko commented Dec 11, 2019

Fixes #17460

@fanquake fanquake added the Tests label Dec 11, 2019
@maflcko maflcko mentioned this pull request Dec 11, 2019
@maflcko
Copy link
Member Author

maflcko commented Dec 11, 2019

A failing travis build was https://travis-ci.org/bitcoin/bitcoin/builds/623456054

export TEST_RUNNER_EXTRA="p2p_segwit.py" # Only run one test for now. TODO enable all and bump timeouts
export RUN_FUNCTIONAL_TESTS=true
export GOAL="install"
export BITCOIN_CONFIG="--enable-zmq --with-incompatible-bdb --with-gui=no CC=clang CXX=clang++" # TODO enable GUI
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we be testing with this flag --with-incompatible-bdb set to true? Is there are reason that we can't use the correct version of berkleydb here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can use the bdb package from depends or from the Ubuntu package manager. The package manager doesn't come with the bdb version we want, so --with-incompatible-bdb is needed. Switching to ./depends is possible, but shouldn't matter, as we ignore leaks and memory issues in dependencies anyway. They need to be dealt with upstream.

@DrahtBot
Copy link
Contributor

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Conflicts

Reviewers, this pull request conflicts with the following ones:

  • #12134 (Build previous releases and run functional tests by Sjors)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

@maflcko
Copy link
Member Author

maflcko commented Dec 16, 2019

Anything left to do here?

@practicalswift
Copy link
Contributor

ACK facb416

Very nice!

@instagibbs
Copy link
Member

concept ACK!

maflcko pushed a commit that referenced this pull request Dec 17, 2019
facb416 ci: Add valgrind run (MarcoFalke)

Pull request description:

  Fixes #17460

ACKs for top commit:
  practicalswift:
    ACK facb416

Tree-SHA512: 55396e548a76f976d7b7170b68bc5f93cfd44656162267172f66db7eb549699a2a22d3b1bb0d5f180fe0697931939e652c8cdb86b435e81e7ce572485798009d
@maflcko maflcko merged commit facb416 into bitcoin:master Dec 17, 2019
@maflcko maflcko deleted the 1911-ciValgrind branch December 17, 2019 16:48
sidhujag pushed a commit to syscoin/syscoin that referenced this pull request Dec 17, 2019
facb416 ci: Add valgrind run (MarcoFalke)

Pull request description:

  Fixes bitcoin#17460

ACKs for top commit:
  practicalswift:
    ACK facb416

Tree-SHA512: 55396e548a76f976d7b7170b68bc5f93cfd44656162267172f66db7eb549699a2a22d3b1bb0d5f180fe0697931939e652c8cdb86b435e81e7ce572485798009d
sidhujag pushed a commit to syscoin-core/syscoin that referenced this pull request Nov 10, 2020
facb416 ci: Add valgrind run (MarcoFalke)

Pull request description:

  Fixes bitcoin#17460

ACKs for top commit:
  practicalswift:
    ACK facb416

Tree-SHA512: 55396e548a76f976d7b7170b68bc5f93cfd44656162267172f66db7eb549699a2a22d3b1bb0d5f180fe0697931939e652c8cdb86b435e81e7ce572485798009d
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Dec 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Run tests in memory sanitizer
6 participants