aserio 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/
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
mcopik has joined #ste||ar
mcopik has quit [Client Quit]
EverYoung has joined #ste||ar
parsa has quit [Quit: Zzzzzzzzzzzz]
eschnett has joined #ste||ar
eschnett has quit [Client Quit]
eschnett has joined #ste||ar
EverYoung has quit [Ping timeout: 246 seconds]
<github>
[hpx] hkaiser created fixing_execution_parameters (+1 new commit): https://git.io/vdCrw
<github>
hpx/fixing_execution_parameters 05c00ee Hartmut Kaiser: Fixing problems with new execution parameters interface
Matombo444 has joined #ste||ar
jaafar has quit [Ping timeout: 258 seconds]
kisaacs has joined #ste||ar
Matombo444 has quit [Remote host closed the connection]
Matombo has quit [Ping timeout: 258 seconds]
diehlpk has joined #ste||ar
kisaacs has quit [Ping timeout: 258 seconds]
kisaacs has joined #ste||ar
kisaacs has quit [Ping timeout: 248 seconds]
jaafar has joined #ste||ar
kisaacs has joined #ste||ar
K-ballo has quit [Quit: K-ballo]
diehlpk has quit [Ping timeout: 240 seconds]
kisaacs has quit [Ping timeout: 248 seconds]
vamatya_ has quit [Ping timeout: 258 seconds]
parsa has joined #ste||ar
hkaiser has quit [Read error: Connection reset by peer]
parsa has quit [Quit: Zzzzzzzzzzzz]
jbjnr has joined #ste||ar
jaafar has quit [Ping timeout: 246 seconds]
<jbjnr>
I was really hoping master would be fixed when I woke up :(
<zao>
01:18:23 -- | Notice(github): hpx/master fed3fea Hartmut Kaiser: Stop-gap measure to make execution parameters compile for thread-executors...
<zao>
01:18:38 @hkaiser | heller: this should fix things for now ^^ - I will create a real fix through a PR
<zao>
jbjnr: That didn't do it, whatever _that_ was? :)
<jbjnr>
correct. it was another fail
<zao>
Might've been for diehl's stuff.
<zao>
Bummer.
<jbjnr>
no it was an attempt to fix the compilation errors. The dashboard is redder than a very red thing today. Terrible. We destroyed it.
<heller>
Not sure if Hartmut is aware of when the tutorial is going to happen
<jbjnr>
I made a fix. testing now
<jbjnr>
because I test my stuff before pushing to master!
<heller>
Go for it!
<jbjnr>
anyway heller - the problem is not just that one commit, it's the other couple before, and the merge of the branch a few days ago. We need to reset the master back a couple of days.
<heller>
And you know, you better not make inspect fail, that's the worst ;)
<heller>
Yes, I know
<jbjnr>
my fix does not fix everything :(
simbergm has joined #ste||ar
<heller>
:(
<heller>
jbjnr: first thing in doing when I get is to implement proper testing
<heller>
Circle taking 4 hours and not catching any real problems is just bad
<jbjnr>
"when I get" what?
<jbjnr>
hmm. time?
<jbjnr>
reset_thread_distribution is causing the trouble at the oment, but I've no idea where this is coming from
<jbjnr>
customization point for executors
kisaacs has quit [Ping timeout: 258 seconds]
<heller>
jbjnr: get back
kisaacs has joined #ste||ar
Matombo has joined #ste||ar
<jbjnr>
kisaacs: Are you the Kate Isaacs that works on Ravel?
kisaacs has quit [Ping timeout: 264 seconds]
<github>
[hpx] biddisco created cscs2017 (+32 new commits): https://git.io/vdC7j
<github>
hpx/cscs2017 459a043 Thomas Heller: Making Clang + CUDA work...
<github>
hpx/cscs2017 4302b4c Thomas Heller: Fixing ICE with nvcc
<github>
hpx/cscs2017 1ff0a9f Thomas Heller: Properly fixing NVCC builds...
<jbjnr>
just fyi heller that cscs2017 branch is the one that I am using at the moment for the tutorial
<heller>
jbjnr: OK. I think those are the tests that I broke
<heller>
Shouldn't matter too much for the short term.
<jbjnr>
ha! I knew it must have been your fault :)
<heller>
:p
<jbjnr>
stencil tutorials don't compile still.
<heller>
Ok, why not?
<jbjnr>
not got round to fixing them yet
<jbjnr>
customization points and hpx::util::unwrapped changes
<heller>
Might use some deprecated apis
<heller>
Right
<jbjnr>
that customization point commit has totally fucked everything.
<heller>
I'm deep into family time right now
<heller>
Yeah
<jbjnr>
enjoy
<heller>
We should just revert it...
<jbjnr>
lets hope hartmut can't sleep and gets up early.
<heller>
Yes ;)
<jbjnr>
hopefully his conscience will be keeping him awake!
<heller>
We just need better testing...
<heller>
A PR got merged which broke some tests (two weeks ago) nobody cared fixing it. More PRs get merged without even looking at buildbot anymore...
<github>
hpx/master a1a0e05 Hartmut Kaiser: Properly forward declare type
<jbjnr>
bin/hello_world -t2 --hpx:bind=balanced
<jbjnr>
hello world from OS-thread 1 on locality 0 hello world from OS-thread 1 on locality 0 hello world from OS-thread 0 on locality 0
<jbjnr>
three outputs for t2!
<hkaiser>
right
<jbjnr>
welcome to the world of weird
<hkaiser>
is this reproducible now?
<jbjnr>
not every time
<jbjnr>
but frequently
<hkaiser>
ok, will look today
<jbjnr>
I have no real idea what might have caused this, other than a race somewhere, but I have no suspicions about where
<hkaiser>
has to be a race
<jbjnr>
ok. there was a mutex around the used_pu_mask access at one point that I might have messed up during RP changes ... ???
<hkaiser>
works for me (tm) :/
<jbjnr>
same error on master for parallel algos
<hkaiser>
ok, I stop pushing to master now - will provide a properly tested fix
<jbjnr>
home/biddisco/src/hpx/hpx/traits/v1/is_executor_parameters.hpp:32:55: error: ‘is_executor_parameters’ in namespace ‘hpx::parallel::execution::detail’ does not name a template type
<jbjnr>
using is_executor_parameters = execution::detail::is_executor_parameters<T>;
<jbjnr>
good plan
<hkaiser>
jbjnr: where is that mutex problem you mentioned above?
<github>
hpx/cscs2017 2a8121c John Biddiscombe: Fix a couple of deprecated c++ features
<K-ballo>
WOW!
<K-ballo>
how did I never saw those?!
<K-ballo>
*see
<K-ballo>
beware with using namespace std::placeholders; at global scope, boost.bind may conflict
aserio1 has joined #ste||ar
aserio has quit [Ping timeout: 255 seconds]
aserio1 is now known as aserio
<zao>
One of my users beat HPX in waste of space today - MPI implementation pushed around 6.6 MiB/s of diagnostic output through Slurm and out onto Lustre.
<zao>
They pushed around 2.1 TiB of data before they noticed because quota command told them they were half full :)
jbjnr_ has joined #ste||ar
<jbjnr_>
K-ballo: that placeholders is a single example and I though it was safe there, but I can move it inside the scope block.
<K-ballo>
boost.bind defines its placeholders in the global namespace, so it's problematic if it were to get included
<K-ballo>
bad boost.bind
<zao>
Meanwhile, the twitter peanut gallery laughs at the verbosity of std::placeholders::, ignorant.
<hkaiser>
jbjnr_: the branch fixing_execution_parameters looks good so far - I think that will solve the problems on master
<hkaiser>
jbjnr_: I'll wait for the tests to finish cycling and will create a PR
<jbjnr_>
ok - do I merge it to my master and try it out
<jbjnr_>
is it just compilation fixes - or did you also solve hello world strangeness
<jbjnr_>
and thanks very much for doing this
<hkaiser>
jbjnr_: I have not looked into the hello_world strangeness yet, but it should fix most of the test failures we're seeing as well
<jbjnr_>
great
<hkaiser>
there is just the problem heller introduced a while back - no idea how to fix this yet - so some of the tests will still fail :/
<jbjnr_>
did you push already? I see nothing new
<hkaiser>
I pushed 3 hours ago - was waiting for the tests
<jbjnr_>
ok ta
parsa has joined #ste||ar
<K-ballo>
wow, tests.unit.parallel is taking as long as the entire tests.unit used to take last I looked at times
<jbjnr_>
the partitioned vector stuff is outrageously slow
<jbjnr_>
I think we need a specil flag to enable it and have it off by default
<diehlpk_work>
hkaiser, Is this rlated to broken master? /usr/local/include/hpx/lcos/future.hpp:813:11: note: candidate constructor (the implicit copy constructor) not viable: no known conversion from 'hpx::lcos::future<boost::range_detail::integer_iterator<int> >' to 'const hpx::lcos::future<void> &' for 1st argument
<diehlpk_work>
class future : public detail::future_base<future<R>, R>