K-ballo changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar.cct.lsu.edu | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | Buildbot: http://rostam.cct.lsu.edu/ | Log: http://irclog.cct.lsu.edu/
<gnikunj[m]>
hkaiser: yt?
<gnikunj[m]>
hkaiser: when you see. I created resiliency APIs over kokkos executors that work for the void return type. I also created a separate executor that you can use with async to get the same result. I've tested it to work for HPX kokkos backend. I'll be testing it for CUDA backend today. Will keep you updated ;)
<hkaiser>
gnikunj[m]: cool!
<hkaiser>
progress!
<gnikunj[m]>
:D
hkaiser has quit [Quit: bye]
bita has joined #ste||ar
bita has quit [Ping timeout: 246 seconds]
<gonidelis[m]>
k-ballo: i have this branch A where is yet to get merged and provides some facilities that i need for my other branch B. is it safe to rebase B on A?
hkaiser has joined #ste||ar
<k-ballo[m]>
gonidelis: define "safe"?
diehlpk has joined #ste||ar
diehlpk has quit [Changing host]
diehlpk has joined #ste||ar
diehlpk has quit [Remote host closed the connection]
diehlpk has joined #ste||ar
diehlpk has joined #ste||ar
diehlpk has quit [Changing host]
diehlpk has quit [Ping timeout: 264 seconds]
<gonidelis[m]>
k-ballo: what happens if A gets merged and then I want to merge B?
<k-ballo[m]>
you'd probably want to rebase from master after A gets merged