-
Notifications
You must be signed in to change notification settings - Fork 99
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
Change name of yaml-cpp to yamlcpp (trilinos/Trilinos#12710) #2099
Change name of yaml-cpp to yamlcpp (trilinos/Trilinos#12710) #2099
Conversation
Status Flag 'Pre-Test Inspection' - - This Pull Request Requires Inspection... The code must be inspected by a member of the Team before Testing/Merging |
Status Flag 'Pre-Test Inspection' - SUCCESS: The last commit to this Pull Request has been INSPECTED by label AT: PRE-TEST INSPECTED! Autotester is Removing Label; this inspection will remain valid until a new commit to source branch is performed. |
Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: KokkosKernels_PullRequest_CUDA11_CUDA11_LayoutRight
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_GCC930_Light_Tpls_GCC930_Tpls_CLANG13CUDA10
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_GNU1021
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_GNU1021_Light_LayoutRight
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_Tpls_GNU1021
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_Tpls_INTEL19_solo
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_CLANG1001_solo
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_A64FX_Tpls_ARMPL2110
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_A64FX_GCC1020
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_VEGA90A_ROCM560
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_VEGA90A_Tpls_ROCM560
Jenkins Parameters
Using Repos:
Pull Request Author: bartlettroscoe |
@bartlettroscoe thanks for submitting the PR and apologies for the need to resolve conflicts (luckily it wasn't too messy in this case, bu still problematic). I appreciate your feedback and the info you shared, I wish I had an immediate answer to prevent this but recognize we need to work toward making this less of a headache (maybe as we eventually move toward using kokkos-kernels as a tpl this may become a bit easier? I'm not sure...) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Status Flag 'Pull Request AutoTester' - Jenkins Testing: all Jobs PASSED Pull Request Auto Testing has PASSED (click to expand)Build InformationTest Name: KokkosKernels_PullRequest_CUDA11_CUDA11_LayoutRight
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_GCC930_Light_Tpls_GCC930_Tpls_CLANG13CUDA10
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_GNU1021
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_GNU1021_Light_LayoutRight
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_Tpls_GNU1021
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_Tpls_INTEL19_solo
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_CLANG1001_solo
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_A64FX_Tpls_ARMPL2110
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_A64FX_GCC1020
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_VEGA90A_ROCM560
Jenkins Parameters
Build InformationTest Name: KokkosKernels_PullRequest_VEGA90A_Tpls_ROCM560
Jenkins Parameters
|
Status Flag 'Pre-Merge Inspection' - SUCCESS: The last commit to this Pull Request has been INSPECTED AND APPROVED by [ ndellingwood ]! |
Status Flag 'Pull Request AutoTester' - Pull Request MUST BE MERGED MANUALLY BY Project Team - This Repo does not support Automerge |
@ndellingwood, occasional conflicts are to be expected when making changes on separate branches that live apart for many months. This is just par for the course. (And the nature of the file
I don't think that would help much because Trilinos would need its own copy of the KokkosKernels repo to be able to make spot changes for Trilinos. The only thing that would improve this is if Kokkos and KokkosKerenls put out more frequent releases. |
I guess the only way to avoid this type of issue would be to mark that we have no dependencies on TriBITs managed TPLs and do the whole TPL management internally in Kokkos Kernels. That way there would not be any interactions and conflicts anymore. This might be something to think about in the future if we move to a more TPL model for KK |
A trivial conflict in a file is not a reason to do that. If KokkosKerenls finds its own dependencies it can find different/incompatible ones from the other packages. |
We already need to do our own TPL management anyway since we can build outside of Trilinos. The only issue for us would be to make sure that our TPLs are not seen by the rest of Trilinos. |
If there are TPLs used only directly by KokkosKernels and are not used directly by any other packages, then that is fine. But if there are TPLs that are also directly used by other packages, then you open the problem of multiple calls to find_package() finding different/incompatible TPLs (depending on other arguments passed to find_package()). |
@ndellingwood
Matches the changes made in Trilinos PR:
yaml-cpp
toyamlcpp
trilinos/Trilinos#12710NOTE: I created these commits using
git format-patch
andgit am
to move the commits from the Trilinos to the kokkos-kernels repo (by apply them on top of the base snapshot commit 9af9fa2 and then rebased on top of 'develop'. (I had to fix a merge conflict incmake/Dependencies.cmake
because of changes on both sides of those branches but they are trivial changes.)