hkaiser 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/ | GSoC2018: https://wp.me/p4pxJf-k1
<diehlpk_work>
Have to go to a meeting and will check later
aserio has joined #ste||ar
AnujSharma has quit [Read error: Connection reset by peer]
<Anushi1998>
Shouldn't I expect {BUILD_DIRECTORY}/bin/credit_exhaustion_test to run successfully? It expects atleast two locality but that should be created by test itself :/
<K-ballo>
that sounds like an executable, not a test
<Anushi1998>
yes it's an executable of credit_exhaustion.cpp made by make tests
<K-ballo>
are you running the executable, or are you running the test?
<K-ballo>
the test will fire enough instances of the executable to satisfy the number of localities the test has as a parameter, the executable has no clue this is happening
<Anushi1998>
I am running the executable. What do you mean by running test
<Anushi1998>
How can i run test than directly?
<K-ballo>
the executable is just some code that was compiled, the test carries additional logic, determines success/failure, etc
<K-ballo>
make tests.unit.agas.credit_exhaustion, probably
<K-ballo>
or ctest --something
<Anushi1998>
okay, thanks :)
<K-ballo>
actually no, make would not run the test, just build the executable
<K-ballo>
or at least, I'm not sure...
<K-ballo>
ctest would definitively run the test (but it would NOT build it)
<Anushi1998>
yes make will just make executable, I guess
<Anushi1998>
that's what make tests is doing
<nikunj>
Anushi1998: you could use make tests.unit.name to make it and then inside of tests/unit/name run ctest command
<K-ballo>
but special targets, like `make test`, do run the tests (while still NOT building them)
<nikunj>
This should run the test specific to the directory's test
<K-ballo>
ctest -R regex runs tests whose names match a pattern, there should be some other way to request to run one specific test
<K-ballo>
ctest --build-and-test ! :|
<Anushi1998>
Thanks :)
<zao>
I use the "run tests matching this regex" with a fully anchored regex.
<zao>
'^asdf\.qwer$' or something.
<nikunj>
hkaiser: yt?
<K-ballo>
zao: so simple, so elegant
<K-ballo>
how come there is no "run just this one test" command
eschnett has joined #ste||ar
<zao>
When in doubt about anything `ctest`, the answer is "no, it's horribly angled toward what CDash might need".
<zao>
I've had to jump through so many hoops to get useful information out of test runs with bind-mounts and everything.
mcopik has quit [Ping timeout: 256 seconds]
aserio1 has joined #ste||ar
<jakub_golinowski>
M-ms, yt?
aserio has quit [Ping timeout: 265 seconds]
aserio1 is now known as aserio
<M-ms>
jakub_golinowski: here
<jakub_golinowski>
I am preparing the PR and I realized that there I still have the code allowing for passign argc and argv globally
<jakub_golinowski>
should I delete it from PR?
<M-ms>
yeah, you can do that
<jakub_golinowski>
M-ms, ok
zura has quit [Quit: Leaving]
<K-ballo>
slack seems to be reporting issues for forcing the build to use C++14
<K-ballo>
looks like the code will override HPX_WITH_ options based on try compile
<jakub_golinowski>
(also I rewriten history of other branches even though they were pushed earlier but this was only pushed to my fork so I guess this is not such a huge issue)