1 |
Hi all, |
2 |
|
3 |
*Summary:* |
4 |
|
5 |
Last week's plans: |
6 |
1) Loop over commands in the build process for multiple implementations. |
7 |
2) Add more mpi implementation's versions to the overlay, testing with |
8 |
mpi-providers |
9 |
3) Adjust libraries/binaries installations globally. This will later be for |
10 |
mpi-dependent things only |
11 |
|
12 |
I have split this work into two different versions- one which emulates |
13 |
multibuild and one which exports src_* in a more normal fashion. I did this |
14 |
considering multibuild is more complex to fully understand, and that it may |
15 |
be a better course of action to start with a more normal src_* procedure, |
16 |
then add multibuild functionality as needed. |
17 |
|
18 |
Next week's plan: |
19 |
1) Successfully export src_* and test with mpich. |
20 |
2) Continue testing against mpi-providers and adding more versions of |
21 |
openmpi and mpich to the overlay. |
22 |
3) Continue adding to wiki/README as functionality is added. Will talk to |
23 |
mentors about other means of documentation as well. |
24 |
|
25 |
*Day-by-day breakdown:* |
26 |
|
27 |
*Monday's Goals:* |
28 |
|
29 |
Complete loop to repeat commands per selected implementation. |
30 |
Work in progress. Currently using a multibuild-like system, needs further |
31 |
testing with mpi implementations. |
32 |
|
33 |
Implement src_* per abi, per mpi implementation. |
34 |
|
35 |
Further discussion needed. The main question here- how will users be |
36 |
interacting with this eclass? I was thinking something along the lines of |
37 |
${implementation}_foreach_version to find the correct range of versions |
38 |
that need to be installed. Perhaps this could be its own function that acts |
39 |
globally among all implementations, and pulls the existing Portage tree |
40 |
versions to find ones that need to be installed. I'll bring this up in the |
41 |
IRC. |
42 |
|
43 |
|
44 |
|
45 |
*Tuesday's Goals:* |
46 |
|
47 |
I will be taking the most of the day off due to an upcoming data science |
48 |
exam on Wednesday. Work will continue on Wednesday as normal, with hours |
49 |
shifted to reach over 35 hours for the week. However, I will likely be |
50 |
asking questions in the IRC. I mainly want to clarify design tomorrow. |
51 |
|
52 |
|
53 |
*Wednesday's Goals:* |
54 |
|
55 |
Fix everything that is currently broken in the overlay. Repoman among other |
56 |
things. Get master to a stable testing point again. |
57 |
Complete. I am still investigating the "partial QA payment" warnings, and |
58 |
still need to look into fortran uses in different gcc versions. |
59 |
Improvements were made to the point where testing can continue. |
60 |
|
61 |
Mail about mpi-select design. Make revisions and additions accordingly. |
62 |
Awaiting response. I was intending on sending this much earlier than I did |
63 |
because I ended up working much later than intended. |
64 |
|
65 |
Add to wiki. |
66 |
|
67 |
Work in progress. I updated it to match the README, which is minimal. Next |
68 |
steps are to add instructions/guidance using proper wiki formatting. |
69 |
|
70 |
|
71 |
|
72 |
*Thursday's Goals:* |
73 |
|
74 |
Test new eclass with different versions of different implementations (i.e. |
75 |
multilib vs. no multilib, fortran vs. no fortran, etc.) |
76 |
|
77 |
Work in progress. With such varied testing there are still many errors to |
78 |
be fixed. These will be apart of tomorrow's work. |
79 |
|
80 |
|
81 |
Ask more questions regarding 2nd eclass as needed. Add to eclass based on |
82 |
design responses. |
83 |
|
84 |
Completed, again rather late. I hope to continue this dialogue more in our |
85 |
weekly meeting. The current dialogue has been very helpful- it has given me |
86 |
a lot more to research today. |
87 |
|
88 |
|
89 |
Update wiki to use better formatting to better explain things (i.e. code |
90 |
blocks) |
91 |
|
92 |
Incomplete. As we are discussing new ways of doing things and clarifying |
93 |
design choices, I thought it would be best to postpone the wiki overhaul |
94 |
until more resolutions have been agreed upon. I'm planning on getting |
95 |
enough info to overhaul the wiki tomorrow. |
96 |
|
97 |
|
98 |
*Friday's Goals:* |
99 |
|
100 |
Further clarify user-end execution in IRC chat. Modify eclass to properly |
101 |
support make.conf MPI_TARGETS editing as needed. |
102 |
Incomplete. I failed to set up a meeting. I will try to do this earlier, as |
103 |
I know differing time zones make things less convenient. My Thursdays and |
104 |
Fridays are preferable for meetings, as I do not have to leave for class |
105 |
these days. |
106 |
|
107 |
Test & edit mpi-select to the point where it is more stable for various |
108 |
openmpi and mpich versions. Add any working versions to the overlay. |
109 |
Complete. Worth noting- I have been testing against mpi-providers rather |
110 |
than mpi-select. mdpi-select needs to have more functionality in order to |
111 |
warrant bringing something else into the overlay from a successful test. |
112 |
|
113 |
Finally overhaul the wiki based on current discussions :) |
114 |
Complete. Will be adding to this as time moves on, of course. |
115 |
|
116 |
|
117 |
|
118 |
Thanks, |
119 |
Michael |