| 1 |
$ cat > dune-project << EOF |
| 2 |
> (lang dune 2.0) |
| 3 |
> (using action-plugin 0.1) |
| 4 |
> EOF |
| 5 |
|
| 6 |
$ cat > dune << EOF |
| 7 |
> (rule |
| 8 |
> (target some_file) |
| 9 |
> (action |
| 10 |
> (dynamic-run ./foo.exe))) |
| 11 |
> EOF |
| 12 |
|
| 13 |
$ cp ./bin/foo.exe ./ |
| 14 |
|
| 15 |
$ dune build some_file 2>&1 | awk '/Internal error/,/unable to serialize/' |
| 16 |
Internal error! Please report to https://github.com/ocaml/dune/issues, |
| 17 |
providing the file _build/trace.csexp, if possible. This includes build |
| 18 |
commands, message logs, and file paths. |
| 19 |
Description: |
| 20 |
("unable to serialize exception", |
| 21 |
|
| 22 |
^ This is not great. There is no actual dependency cycle, dune is just |
| 23 |
interpreting glob dependency too coarsely (it builds all files instead |
| 24 |
of just bringing the directory listing up to date). |