-
Notifications
You must be signed in to change notification settings - Fork 579
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
Python drivers #5800
Python drivers #5800
Conversation
Because the PR testing will have it and fail if we don't
I had previously sorted the key set to avoid order mismatches between python 2/3. Fort whatever reason the tests showed AttributeError: 'KeysView' object has no attribute 'sort' in python 3 - likely a different point version.
1) the cuda environment included a 'module swap' which was incorrectly set up and now works. 2) the shell driver script was not passing the arguments needed to the Test section. It was in fact never moved to use the python.
Remove old Test.sh script Correct executable bit on new Test.py script
Correct path to subproject list Add cmake to python testing module list
Load python before the Merge/Test scripts - the default version is that old Correct path for cuda compilers so the nvcc wrapper can find them
Turns out the entire dictionary is constructed every time.
Add missing mpich2 module to intel configuration Move environemnt print-out to try and debug the cuda build
Just loading the second one does not guarantee we will get what we want downstream (path order controls)
The environmental changes map is built on python start up. The test was seeting the CC and FC values before that rather than at module load as the real runs will. This modifies the test and code to match what will actually occur.
It looks like the path is not getting upodated but instead replaced when modifying the environment. Since I know this works in testing and on all the other builds I am guessing that the old version of python that ride defaults to is the issue.
This turned out to be the issue for the ride jobs - I was adding in path before loading modules and then the map update overwrote all the changes with the initial path. It did not show on other systems because they were not manually adding paths.
The previous shell scripts had unloaded the seme-python module then added path and pythonpath directly as the sierra python modules are not working for the trilinos entity. I was attempting to fix that as it would be simpler, but it looks like that is a no-go on the cloud nodes at this time.
And by checking that this comes through I should help avoid regressioooon to the issue that caused the CUDA failures.
Status Flag 'Master Merge AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Using Repos:
Pull Request Author: prwolfe |
Status Flag 'Master Merge AutoTester' - Jenkins Testing: 1 or more Jobs FAILED Note: Testing will normally be attempted again in approx. 15 Mins. If a change to the PR source branch occurs, the testing will be attempted again on next available autotester run. Pull Request Auto Testing has FAILED (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.8.4 # 4351 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_intel_17.0.1 # 4174 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.9.3_SERIAL # 2612 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_7.2.0 # 2436 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_cuda_9.2 # 2013 (click to expand)
|
Status Flag 'Master Merge AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Using Repos:
Pull Request Author: prwolfe |
Status Flag 'Master Merge AutoTester' - Jenkins Testing: 1 or more Jobs FAILED Note: Testing will normally be attempted again in approx. 15 Mins. If a change to the PR source branch occurs, the testing will be attempted again on next available autotester run. Pull Request Auto Testing has FAILED (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.8.4 # 4354 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_intel_17.0.1 # 4177 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.9.3_SERIAL # 2615 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_7.2.0 # 2439 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_cuda_9.2 # 2016 (click to expand)
|
I missed this during the transition to python and jhux found the issue in trilinos#5789
The python tests for this branch failed when attempting to build everything because most TPL's are turned off. The odd part is that the old system did not have such a bypass and worked fine - I'm not su8re how. This just writes the packageEnables.cmake file directly if needed and bypasses the shell script.
Status Flag 'Master Merge AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Using Repos:
Pull Request Author: prwolfe |
Status Flag 'Master Merge AutoTester' - Jenkins Testing: 1 or more Jobs FAILED Note: Testing will normally be attempted again in approx. 15 Mins. If a change to the PR source branch occurs, the testing will be attempted again on next available autotester run. Pull Request Auto Testing has FAILED (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.8.4 # 4364 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_intel_17.0.1 # 4188 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.9.3_SERIAL # 2625 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_7.2.0 # 2449 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_cuda_9.2 # 2026 (click to expand)
|
Status Flag 'Master Merge AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Using Repos:
Pull Request Author: prwolfe |
Status Flag 'Master Merge AutoTester' - Jenkins Testing: 1 or more Jobs FAILED Note: Testing will normally be attempted again in approx. 15 Mins. If a change to the PR source branch occurs, the testing will be attempted again on next available autotester run. Pull Request Auto Testing has FAILED (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.8.4 # 4367 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_intel_17.0.1 # 4191 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_4.9.3_SERIAL # 2628 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_gcc_7.2.0 # 2452 (click to expand)
Console Output (last 100 lines) : Trilinos_pullrequest_cuda_9.2 # 2029 (click to expand)
|
After merging #5814 all the issues I found on develop should be resolved. I am going to force push this so dev -> master will run again. |
These changes have been in develop for a bit (8/24/2019 at about 9:00 am) and will not merge into master via the attester due to bootstrapping issues in the top level sh script. This will need to be careful considered and then for pushed to get dev->master testing back on track.