Vasileios Karakasis

Hi @vsoch and thanks for you contribution! And also for taking the time to provide a full tutorial as well! Regarding testing, I think that testing it through a container...

> And yes I'd be happy to do that - are there a standard set that you like to run for reframe, or should I ping the Flux core devs...

> And it looks like we need to disable running flux tests for the normal CI - how would you like to try doing that? Just a figure that is...

> I might need some help thinking through this one: https://github.com/reframe-hpc/reframe/actions/runs/3104434148/jobs/5037509247#step:6:449 as it works for me locally (so I cannot reproduce to debug!) You were faster than me! I was...

My PR is done now!

@vsoch The problem with the unit test failure is not Flux's problem. It's something wrong with the local scheduler implementation; I will have a look at it and try to...

Still no luck, but I just noticed that you run the unit tests and reframe etc. in the container using flux, like `flux start ...`. Could you try removing that...

> if we start a flux instance before (via an interactive shell) that wouldn't work in the CI. If you just want to do a sanity check to remove flux...

Thanks for reporting this @nordmoen! We can fix the regex.

This is related to #1524.