hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar-group.org | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | This channel is logged: irclog.cct.lsu.edu
Yorlik_ has joined #ste||ar
Yorlik has quit [Ping timeout: 256 seconds]
hkaiser has quit [Quit: Bye!]
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 256 seconds]
K-ballo1 is now known as K-ballo
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 256 seconds]
K-ballo1 is now known as K-ballo
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 256 seconds]
K-ballo1 is now known as K-ballo
K-ballo has quit [Remote host closed the connection]
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
diehlpk_work has joined #ste||ar
<pansysk75[m]>
I'm looking at the CI tools we are using, CircleCI, GitHub Actions and Jenkins
<pansysk75[m]>
They all seem to serve a sort of similar function, why are we using all of them?
<zao>
I believe that historically there has been different platforms supported on the different vendors and things like GH Actions are relative newcomers. Some of the CI runners are out on HPC clusters (CSCS?) so those I think are wired in via Jenkins.
<hkaiser>
pansysk75[m]: as zao said, historical reasons - also the different platforms have different hardware and usage limits,
<hkaiser>
github allows us to test windows and macos, for instance
<pansysk75[m]>
Oh ok thanks, it's all new to me so I thought I was missing sth
<pansysk75[m]>
And currently, only the "jenkins/cscs-perftests" job is the one that also runs the performance tests/reports?
<pansysk75[m]>
Because there is also "ci/circleci: tests.performance" that is being built (and others that build the tests.performance target), but I can't find those being ran anywhere
<hkaiser>
pansysk75[m]: yes
<hkaiser>
the circleci builds and runs all perf tests, but it doesn't collect perf results