unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exec-watch/exec-watch-multi-levels.t/bin/dune

@@ -0,0 +1,3 @@
+(executable
+ (name main)
+ (libraries unix))

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exec-watch/exec-watch-multi-levels.t/bin/main.ml

@@ -0,0 +1,9 @@
+let () =
+  let touch path =
+    let fd = Unix.openfile path [ Unix.O_CREAT ] 0o777 in
+    Unix.close fd
+  in
+  print_endline "foo";
+  match Sys.argv.(1)  with
+  | exception _ -> ()
+  | path -> touch path

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exec-watch/exec-watch-multi-levels.t/dune-project

@@ -0,0 +1 @@
+(lang dune 3.6)

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exec-watch/exec-watch-multi-levels.t/run.t

@@ -0,0 +1,38 @@
+Test the behaviour of exec watch mode when the current directory is not the
+project root directory.
+
+"dune exec --watch" works fine when invoked at the root level
+  $ DONE_FLAG=_build/done_flag
+  $ dune exec --watch ./bin/main.exe $DONE_FLAG &
+  foo
+  Success, waiting for filesystem changes...
+  $ PID=$!
+
+Wait for the $DONE_FLAG file to exist, then delete the file. This file is
+created by the program being exec'd, so when it exists we know that it's safe to
+change the code and proceed with the test.
+  $ ../wait-for-file.sh $DONE_FLAG
+  $ kill $PID
+  $ wait $PID
+  [130]
+
+Perform the same test above but first enter the "bin" directory.
+  $ dune clean
+  $ cd bin
+  $ dune exec --root .. --watch ./bin/main.exe ../$DONE_FLAG &
+  Entering directory '..'
+  foo
+  Success, waiting for filesystem changes...
+  Leaving directory '..'
+  $ PID=$!
+  $ cd ..
+  $ ../wait-for-file.sh $DONE_FLAG
+  $ kill $PID
+  $ wait $PID
+  [130]
+
+Test that the behaviour is the same when not running with "--watch"
+  $ cd bin && dune exec --root .. ./bin/main.exe
+  Entering directory '..'
+  Leaving directory '..'
+  foo