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/
EverYoun_ has joined #ste||ar
fane_faiz1 has quit [Ping timeout: 240 seconds]
EverYoung has quit [Ping timeout: 255 seconds]
EverYoun_ has quit [Ping timeout: 255 seconds]
fane_faiz1 has joined #ste||ar
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
rod_t has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
diehlpk has joined #ste||ar
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
hkaiser has quit [Read error: Connection reset by peer]
hkaiser has joined #ste||ar
EverYoung has quit [Ping timeout: 255 seconds]
EverYoung has joined #ste||ar
rod_t has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
rod_t has joined #ste||ar
EverYoung has quit [Ping timeout: 255 seconds]
EverYoung has joined #ste||ar
EverYoung has quit [Ping timeout: 255 seconds]
K-ballo has quit [Quit: K-ballo]
rod_t has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
EverYoung has joined #ste||ar
fane_faiz1 has quit [Ping timeout: 248 seconds]
EverYoung has quit [Ping timeout: 256 seconds]
diehlpk has quit [Ping timeout: 258 seconds]
hkaiser has quit [Quit: bye]
rod_t has joined #ste||ar
rod_t has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rod_t has joined #ste||ar
rod_t has quit [Client Quit]
nanashi55 has quit [Ping timeout: 260 seconds]
nanashi55 has joined #ste||ar
EverYoung has joined #ste||ar
rod_t has joined #ste||ar
EverYoung has quit [Ping timeout: 255 seconds]
jakemp has joined #ste||ar
rod_t has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<github>
hpx/master 9b1b369 Alex Hirsch: Fix setting of default build type
<github>
hpx/master b8e7eb4 Mikael Simberg: Merge branch 'master' into fix-default-build-type
<github>
hpx/master 60e9fa0 Mikael Simberg: Merge pull request #3033 from W4RH4WK/fix-default-build-type...
fane_faiz1 has joined #ste||ar
jbjnr has joined #ste||ar
jaafar has quit [Ping timeout: 260 seconds]
fane_faiz1 has quit [Ping timeout: 240 seconds]
<heller>
jbjnr: the pycicle status looks great!
<jbjnr>
thanks
<jbjnr>
it now correctly scrapes the results from each build and should update github with the results.
<jbjnr>
but - we might need a pycicly github account so that my face isn't attached to each one :)
<jbjnr>
also, we might want pycicle-cscs/pycicle-fau/pycicle-lsu probably so that if builds fomr one succeed, but from another fail, the results don't get overwritten by the other one ...
<heller>
Yes
<heller>
I was thinking that we should report separately for each build
<heller>
Such that we have something like: pycicle/cray(daint)/gcc-5.3/boost-1.63/...
<heller>
Each site would get its own status then
<heller>
Maybe coerce the config/build/test status into one?
<heller>
So we could have something like: pycicle/linux(greina)/gcc-5.3.0/boost-1.65.1/release
EverYoung has joined #ste||ar
EverYoung has quit [Ping timeout: 252 seconds]
<jbjnr>
heller: I think, one status per build is too many, but one per PR on each machine would be ok
<jbjnr>
so if Release AND debug ANF boostv1 AND boostv2 AND etc all pass, then status=PASS, else fail ???
<jbjnr>
I will do a clang build setup on daint today
<heller>
jbjnr: ok, if everything is coordinated inside pycicle than I am fine
<jbjnr>
currently it is not, but that would be a next improvment - still working on getting a stable dashboard display etc
<heller>
ok
<heller>
the problem with one status per machine is that it is harder to digest which configuration actually failed
david_pfander has joined #ste||ar
<heller>
jbjnr: if all checks pass, the status is folded anyways
<heller>
i'd go for one status for each config
<jbjnr>
I see. Might be a bit messy though
<jbjnr>
with so many statuses
<heller>
not if all pass ;)
<heller>
one per configuration, also has the advantage, that the status URL could directly forward to the build id
<simbergm>
heller: the stacksize test seems to still have occasional failures :( I'll keep an eye on it
<simbergm>
it may be only with gcc 4.9
<github>
[hpx] msimberg closed pull request #3035: Make parallel unit test names match build target/folder names (master...fix-parallel-test-names) https://git.io/vbqB9
rod_t has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hkaiser has joined #ste||ar
Smasher has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
EverYoung has quit [Ping timeout: 246 seconds]
aserio has quit [Ping timeout: 264 seconds]
aserio has joined #ste||ar
<wash[m]>
aserio: I won't be on the call today
<aserio>
wash[m]: thanks for the heads up!
<jbjnr>
hkaiser: sorry about the bogus github status link for the PR you mentioned. I believe that this was caused by my testing of the github status setting and I might have writtedn some crap to several branches in the form of status updates. I think it is behaviing as expected now. please tell me if you find any more like that.
<hkaiser>
jbjnr: ok, will do - thanks
rod_t has joined #ste||ar
fane_faiz2 has joined #ste||ar
rod_t has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rod_t has joined #ste||ar
<github>
[hpx] biddisco created fixing_2092 (+1 new commit): https://git.io/vbczS
<github>
hpx/fixing_2092 121753b John Biddiscombe: Do not bind test running to cmake test build rule
<zao>
Load average: 183.29 70.55 26.69
<zao>
Upside of things, I just spawned 50 parallel test runs of a single build. I hope that all tests are well-behaved and won't drive me into swap :P
<jbjnr>
hkaiser: did you mentioned someehere that you had subsumed the work I did on making future_then pass predicate using && into some other branch/work?
<hkaiser>
yes
<hkaiser>
#3039
<zao>
Turned out that I indeed could rebind the Testing directory of a build tree, so they won't trample on each other.
<jbjnr>
ok, great. Should I start testing that branch for my work?
<zao>
Unless there's a test that writes to the build directory itself. I sure hope not :)
<jbjnr>
zao: probably not, but not sure
EverYoung has joined #ste||ar
<jbjnr>
most tests only write to std::cout/err
<hkaiser>
jbjnr: yes
<hkaiser>
pls
<jbjnr>
some examples might create files ...
<jbjnr>
hkaiser: ok. Will it work ok, or are there any thing I need to look out for
<zao>
This is a lot of threads... oh boy.
EverYoung has quit [Ping timeout: 255 seconds]
rod_t has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rod_t has joined #ste||ar
<hkaiser>
jbjnr: circleci is green now, I think
<jbjnr>
?
<hkaiser>
I meant for #3039
<jbjnr>
aha. great. cdash still shows errors, but they are the same as master, so no surprises there. thanks
<jbjnr>
I'll play with it soon. probly not tonight though
<hkaiser>
jbjnr: sure, all scheduling is done through executors now
<jbjnr>
awesome!
mcopik has joined #ste||ar
rod_t has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
david_pfander has quit [Ping timeout: 240 seconds]
rod_t has joined #ste||ar
rod_t has quit [Client Quit]
<zao>
Soooo.... the machine appears hung solid :D
<jbjnr>
surprise!
<jbjnr>
when you check -you'll find partitioned_vector_xxx is the problem
rod_t has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
fane_faiz2 has quit [Ping timeout: 248 seconds]
rod_t has joined #ste||ar
aserio has joined #ste||ar
tjtn has joined #ste||ar
<tjtn>
Hey all
<hkaiser>
tjtn: hey
aserio has quit [Ping timeout: 248 seconds]
<tjtn>
So I found out about Stellar through a repo on GitHub, and started poking around the site a bite
<tjtn>
*bit
aserio has joined #ste||ar
<tjtn>
Anyway, I'm working on an article for my blog (https://www.timnoetzel.com) on the user experience for developers who code complex systems, I was wondering if I could interview somebody from your team
<tjtn>
Just a few short questions over email
<hkaiser>
tjtn: sure
<hkaiser>
whom would you like to talk to?
<tjtn>
Basically the article would cover developer experience, and ideally would feature somebody who's got some strong opinions about it
<tjtn>
Maybe one or two of you can PM me your emails and we can get a conversation going there?