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]
diehlpk has quit [Ping timeout: 260 seconds]
EverYoung 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]
EverYoung 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]
EverYoung 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]
EverYoung 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]
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
EverYoung has joined #ste||ar
EverYoung has quit [Ping timeout: 255 seconds]
diehlpk has joined #ste||ar
EverYoung has joined #ste||ar
EverYoun_ has joined #ste||ar
EverYoung has quit [Ping timeout: 246 seconds]
EverYoun_ has quit [Remote host closed the connection]
K-ballo has quit [Quit: K-ballo]
nanashi55 has quit [Ping timeout: 246 seconds]
nanashi55 has joined #ste||ar
EverYoung has joined #ste||ar
EverYoung has quit [Ping timeout: 255 seconds]
diehlpk has quit [Remote host closed the connection]
hkaiser has quit [Quit: bye]
EverYoung has joined #ste||ar
EverYoung has quit [Ping timeout: 255 seconds]
parsa has quit [Quit: Zzzzzzzzzzzz]
nanashi55 has quit [Ping timeout: 248 seconds]
nanashi55 has joined #ste||ar
parsa has joined #ste||ar
parsa has quit [Client Quit]
jaafar has joined #ste||ar
EverYoung has joined #ste||ar
EverYoung has quit [Ping timeout: 255 seconds]
jaafar has quit [Quit: Konversation terminated!]
jaafar has joined #ste||ar
<heller>
jbjnr: woohoo, inspect
<jbjnr>
someone needs to merge something, so I can test if everything is working again :)
<heller>
;)
<heller>
i still think it is overkill to run inspect multiple times
<jbjnr>
it is run by each builder before the config/build/test cycle
<jbjnr>
doing it like that is easy - doing it in a separate set of scripts is more complicated
<jbjnr>
for now I'm happy
<heller>
figured
<jbjnr>
if you want to improve it, then I'll push my stuff and you can modify it
<heller>
what's missing now is the one status per config ;)
<jbjnr>
I will add one status (on github) per build now
<jbjnr>
easy to do, just change the context string to match the build site/name
<heller>
*nod*
<heller>
I am working on a better UI now ;)
<jbjnr>
waste of time
<heller>
I don't think think so
<heller>
cdash can be reused
<heller>
jbjnr: we should fix the test building first
<heller>
Having failed tests which actually work is a bummer
<jbjnr>
which tests are you referring to
<heller>
The coalescing one
<jbjnr>
if it was passing, it would pass
<jbjnr>
it fails because it is wrong
<heller>
Right
<heller>
So we need to fix it
<heller>
ctest is just doing a "make all" essentially?
<jbjnr>
fixed - I'll push in a mo
<jbjnr>
not fixed
<jbjnr>
parcel_coalescing doesn't get built at all on my system
<jbjnr>
there's no make rule for it
<jbjnr>
HPX_WITH_PARCEL_COALESCING is ON
<zao>
My build is `ninja components tests.regressions tests.unit tests.performance`
<zao>
Especially `components` is omitted if you just build `tests`.
<zao>
(with inspiration from the buildbot/circle)
EverYoung has joined #ste||ar
<jbjnr>
zao: yup. this is not right. if you want to test (for example) coalescing, then the coalescing lib should be built as part of the test build.
<jbjnr>
(I made a PR, but irc didn't show anything)
<zao>
Myup.
<jbjnr>
zao: I suspect other components/plugins might have the same trouble - I guess that's what our test dashboards are for...
<zao>
My project will probably be a bit resourceless for a while, having hardware trouble.
<zao>
There's around 1400 EUR of AMD junk under my desk that's not fit for purpose :D
EverYoung has quit [Ping timeout: 255 seconds]
jaafar has quit [Ping timeout: 240 seconds]
<simbergm>
heller: I'm aware that my tests don't build, sorry about that... on it now
<heller>
simbergm: already fixed ;)
<simbergm>
heller: thank you! I have some catching up to do, seems like you all had a very productive weekend!
<jbjnr>
error: no member named 'random_shuffle' in namespace 'std'
<jbjnr>
grrrr
<heller>
jbjnr: err
<heller>
jbjnr: I thought I fixed this as well :(
<heller>
jbjnr: look for std::shuffle
<jbjnr>
"random_shuffle was deprecated in C++14 and completely removed in C++17."
<jbjnr>
you might have fixed it - but has it been merged to master?
<jbjnr>
if it's in a PR, then we should merge it
<heller>
it should have been merged, yes
<heller>
which file gives you the error?
<zao>
Is there any point in having a proper git checkout when building HPX, compared to say a 'git archive' export?
<heller>
zao: history
<zao>
Apart from possibly commit ID in diagnostics?
<zao>
I currently pipe archive into untar to the build dir, so I get the tree but not the repo.
<zao>
Heck, my build image doesn't have the git program.
<zao>
If there's value, I can do a shallow reference clone.
<github>
[hpx] biddisco opened pull request #3067: #ifdef out random_shuffle deprecated in later c++ (master...fix_random_shuffle_error) https://git.io/vbRpj
mcopik_ has joined #ste||ar
mcopik_ has quit [Client Quit]
<jbjnr>
hmmm master branch triggers an inspect error, but I suspect it is bogus
<heller>
jbjnr: excellent. my UI awesomeness has to wait until then, I guess
<github>
[hpx] biddisco opened pull request #3070: Fix dynamic_counters_loaded_1508 test by adding dependency to memory_… (master...fix_dynamic_counters_loaded_1508) https://git.io/vbEfE
<heller>
jbjnr: the status for pycicle seems to be broken
diehlpk_work has joined #ste||ar
<jbjnr>
heller: will fix asap
EverYoung has quit [Ping timeout: 240 seconds]
<heller>
hkaiser: is #3068 clearer now?
<heller>
FWIW, I have seen hpx::lcos::condition_variable to be the cause for deadlocks (switching to hpx::lcos::detail::condition_variable fixed those)
<heller>
i say the assert should be there. The test however, is then testing something that's a programming bug in the first place. I think it should be removed. Your take?
EverYoung has joined #ste||ar
EverYoung has quit [Remote host closed the connection]
<zao>
Didn't bother making separate Testing directories, so it's possible that things trample on each other a bit.
<zao>
(50 concurrent test runs)
<zao>
(this is master as of c05035a)
<heller>
You should submit to the dashboard
<zao>
Feels like it could get a bit noisy with dozens upon dozens of testruns for a particular commit.
<zao>
But I don't know how well cdash filters/compacts.
<zao>
Doing a test run now to see if I get usable Test.xml out of it.
<jbjnr>
if you run multiple sets of tests in the same build dir, the ctest TAG will be overwritten and only one would be valid
<jbjnr>
assuming you use ctest -D xxx etc
jaafar has joined #ste||ar
<zao>
Yeah, I haven't figured out how to generate/override the tag, so all my builds for a day end up as YYMMDD-hhmm, cycling once a day.
<jbjnr>
ctest picks up the TAG from the build dir, so really you should use N build dirs for N concurrent sets of tests.
<jbjnr>
I think you might be able to provide a TAG on the cmd line, but I doubt its worth the effort ...
<zao>
I've got a proof-of-concept where I bind a separate build/Testing directory into each run, but haven't adapted the scripts to it yet.
<zao>
My approach here will probably ultimately be to shove results into a RDBMS and have an API to ask about failure/success/timeout rates of the tests for a commit.
<zao>
Or whatever one might care about in a dashboard.
<jbjnr>
are you sure you don't want to jusr run pycicle and submit results here?
<jbjnr>
lots of hacking work still needed to do cleaning up of dirs etc - just need some basic python skills
<zao>
Quite possible, if I manage to secure a solid machine and can shoehorn it into the containers.
<zao>
My setup is a bit weird, as I don't have many variants when it comes to compilers and versions.
<zao>
What I can do is run a lot of test suites.
<zao>
A build of tests and deps takes 35min, so if I have variants the CPU time rapidly exhausts.
<jbjnr>
pycicle currently has a=only the option of gcc or clang and on greina, it only builds gcc, so there are not many variants yet implemented.
<zao>
Where does it live? Part of `tools` in HPX or is the bulk in some other repo?
<jbjnr>
it lives in tools, but only in pycicle brnch so far. in a few more days, I reckon it'll be ready for others to use
<jbjnr>
still a bit hacky at the moment and not completeley robust