Also i didn't know how to build the test server so i added a dune file, i don't know if thats ok

Hi @francoganga! This PR looks like a great start ✨ – we can probably do a few small things to get it merged, and then improve on it.

First thing would be to run the formatter, you can do this with dune fmt. That should format all the new OCaml code you've written.

Second would be how the Autobahn Riot app is defined. We probably want something a little more like this to be more idiomatic with Riot, but also to encapsulate the docker spawning process and make sure the Autobahn Riot app doesn't terminate immediately.

module Autobahn = struct
  let spawn_docker args = ...
 
  let init () = 
    let docker_pid = spawn_docker args in
    (* after spawning the OS process, we want to keep the riot Autobahn app alive,
       so we just _wait_ to receive a message *)
    match receive () with 
    | _ -> failwith "should never have received a message"
    

  let start () =
    let pid = spawn init in
    Ok pid
end

This may actually help with not terminating the tests abruptly. The way Riot.start works is that we pass in a bunch of modules that are "apps", and Riot will supervise all of them. If one of them finishes, it'll be started again, until it reaches the limit of restarts. When it reaches the limit of restarts, then the supervisor of all the apps will finish. At that point, the server will also be terminated. This may explain the behavior you're seeing.

Hope this helps, and feel free to drop by the Riot discord if we can help! 🙏🏼

Hi @leostera , i cleaned up the code a bit, riot gives me the same error at some point. What i discovered is that if i run autobahn without riot (manually) it fails in the same way. Also if i run the autobahn tests in small subsets ex:
run "1.*", then "2.*", etc. it works fine, the problem appears to be when it runs all the test at once.