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

Continuous Integration via Travis #110

Open
wants to merge 168 commits into
base: develop
Choose a base branch
from

Conversation

L30nardoSV
Copy link
Member

This PR aims to add a preliminary support of the Continuous Integration (CI) feature via Travis into AutoDock-GPU.

  1. Every commit triggers a set of automatic test on different systems featuring multi-core CPUs. This is so far limited to Ubuntu, but can be later extended to other Linux distributions, or even to macOS (depending on available support).

  2. Current configuration runs on the following Ubuntu distributions: Focal (20.04), Bionic (18.04), Xenial (16.04).

  • On Focal, four test cases are performed, namely NUMWI = { 1, 4, 8, 16 }.
  • On Bionic and Xenial, this is currently limited to only NUMWI = 1 for each distribution.
  1. Proposed tests are available within this run_test.sh script. Their length is limited to lower bounds (in terms of #molecules, #LGA runs, etc) in order finish testing in a reasonable amount of time (approx. 10 min for each case).

  2. All builds are listed here, while details of lastest build can be found here. Notice that running clinfo shows that only two CPU cores are available per system.

  3. Minor code clean-up on Makefiles.OpenCL and Makefile.Cuda.

Looking forward to your feedback.

…ith travis configuration needed for a travis/docker test
@L30nardoSV
Copy link
Member Author

I updated the PR so that CI is based on GitHub actions instead of Travis.

@atillack @diogomart @jeeberhardt, please have a look and provide feedback :)

@atillack
Copy link
Member

atillack commented Jan 3, 2022

@L30nardoSV That's great - thank you. I think the only thing missing now is to automatically compare the test run results against reference values (+/- 0.3 kcal/mol maybe) and use it :-)

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

Successfully merging this pull request may close these issues.

3 participants