hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar-group.org | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | This channel is logged: irclog.cct.lsu.edu
diehlpk_work has quit [Remote host closed the connection]
K-ballo has quit [Quit: K-ballo]
hkaiser_ has quit [Quit: Bye!]
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
Guest105 has joined #ste||ar
Guest105 has quit [Ping timeout: 256 seconds]
hkaiser has quit [Quit: Bye!]
hkaiser has joined #ste||ar
<gnikunj[m]>
hkaiser: I’m traveling this week and the next. I won’t be able to join today’s PMC meeting.
<gonidelis[m]>
gnikunj: have a good jump!
jbjnr[m] has quit [Quit: You have been kicked for being idle]
diehlpk_work has joined #ste||ar
hkaiser has quit [Ping timeout: 250 seconds]
hkaiser has joined #ste||ar
<gonidelis[m]>
hkaiser: seems like the 1.8 milestone prs list was complete already. do you usually add closed prs on the milestone on your own?
<gonidelis[m]>
seems like it
<gonidelis[m]>
so i should just skim over the prs for any miss
<BR23>
Are the set of tasks known beforehand or is it like various tasks can keep asking for a range lock and our scheduler should take a call dynamically?
<hkaiser>
BR23: uhh, that's a question for John Biddiscombe <john.biddiscombe@cscs.ch>, could you write an email, please (feel free to cc me)