Skip to content

Check Machine Type for Navier-Stokes Tests #15

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

Merged
merged 2 commits into from
Oct 20, 2015
Merged

Check Machine Type for Navier-Stokes Tests #15

merged 2 commits into from
Oct 20, 2015

Conversation

naveen-rn
Copy link

Made change to the CMake setup while building as well as for adding test
to the runtime list, for performing Navier-Stokes tests. The system setup or
the machine configuration type is identified before building and performing
Navier-Stokes tests. If the machine is identified to be a 64bit (x86-64) system,
the Navier-Stokes test is performed or else the case is omitted from the tests.

This change provides a hard-check, may be we need to add fine-grained checks
to see what are the different types of machines, which can be used for running
this test.

Made change to the CMake setup, for performing Navier-Stokes tests.
The system setup or the machine configuration is identified before
performing Navier-Stokes tests. If the machine is identified to be
a 64bit (x86-64) system, the Navier-Stokes test is performed or else
the case is omitted from the tests.

Signed-off-by: naveen-ravi <[email protected]>
check whether the system is a 32bit-64bit version even for building
the Navier-Stokes tests.

Signed-off-by: naveen-ravi <[email protected]>
rouson added a commit that referenced this pull request Oct 20, 2015
Check Machine Type for Navier-Stokes Tests
@rouson rouson merged commit ed3be7f into sourceryinstitute:master Oct 20, 2015
@finneyb finneyb mentioned this pull request Dec 6, 2015
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.

4 participants