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
Extract dependency graph for package in stack #2784
base: develop
Are you sure you want to change the base?
Conversation
As discussed in #2783, this forms the basis for an alternative approach where we map all the easyconfigs in the software directory to a graph with (something like):
This results in a depgraph for the entire installed software stack. The resulting file is too huge to deal with directly so I wrote a script that can extract all the software that depends (directly or indirectly) on a certain module:
and makes a specific dot file for that software. You call it with
|
I made a set of updates to the script that leverages this:
|
Here are the timings to generate the graph for the current set of 2018b easyconfigs:
|
LGTM. But I think the script is where the real usefulness of this arises. Does it make sense to include it in https://github.com/easybuilders/easybuild-framework/tree/master/easybuild/scripts ? |
@ocaisa Can we come up with a test that verifies that we allow pre-existing edges now? |
I tried but I can't create a trigger this (at least based on the test easyconfigs). I'll take another look again soon |
This is required for building a depgraph for an entire installation tree