-
Notifications
You must be signed in to change notification settings - Fork 110
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
Development flow #23
Comments
Looks cool, have you already tried it? G On 16/01/16 01:09, Antonin Portelli wrote:
###################################################### |
does indeed look cool -- I'll think about trying a little prototype (not grid) and see |
Will add to this issue, rather than file a new one. I've set up a Cron job on Cori to run nightly builds icpc-none-avx2 questions:
|
and p.s. annoyed at github -- they should provide continuous integration support; just lazy to |
There are other free providers, e.g. https://travis-ci.org/. EDIT: And it has GitHub hooks so that it only runs a new test when new commits are pushed. |
Please find below some random thoughts about a development workflow:
|
To answer your question RE Travis, I don't think there's any limitations for open source projects beyond "fair use" (see https://travis-ci.com/plans). Obviously if you're sucking up horrendous numbers of core hours for many different build configurations, then that may cause problems. I use it for pyQCD, though admittedly the number of files to compile is much smaller. EDIT: More info on how the Travis CI queue works here. |
Hi, Just an update about the source code development flow. I have tried Maybe a good way to discuss that would be to have a meeting once Guido is here in Edinburgh? |
I have a travis configured on g++-4.9 and AVX2. We can grow this to clang-3.8++, and also various SSE4, AVX, AVX2 I guess. We still need ICPC compiles, and the nightly at NERSC will remain in addition to Travis-CI hooks. |
I guess this issue is solved? |
I will add that the builds should be 2 times 24. We need a build for the single precision and one for the double in order to spot locations where an assumption on the precision is made that clashes with the general definition. I found one of these yesterday for example. |
I added double and single to the build and test. |
Hi,
Recently my attention was attracted to the following extension of git to manage the development flow of a project (features, stable/unstable branches, ...): http://danielkummer.github.io/git-flow-cheatsheet/
I thought it was worth considering it regarding the recent discussion and Guido's suggestion (which I completely support) of some form quality control and maybe milestones.
Let me know what you think.
The text was updated successfully, but these errors were encountered: