You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling ocaml-mdx-test doesn't work every time
argv0 cannot be trusted, also Mdx doesn't control how its installed and shouldn't. PATH is the right abstraction here.
In Mdx's testsuite, Dune gives us a path containing /, Windows' execve exits without warning and nothing happen.
In Mdx's testsuite
dune.inc files are changed because of line encoding
mli unit tests are failing because of line encoding
mdx-test/* tests use POSIX shell features (echo, heredoc, for loops) and unix tools (ls, seq)
I'm using Mdx in Odoc's testsuite and I'd like to run tests on Windows.
Currently, Mdx on Windows doesn't work well:
Line endings: Fix end of line parsing on Windows #294
Cram blocks don't work because Mdx is calling
sh.Calling ocaml-mdx-test doesn't work every time
argv0 cannot be trusted, also Mdx doesn't control how its installed and shouldn't. PATH is the right abstraction here.
In Mdx's testsuite, Dune gives us a path containing
/, Windows'execveexits without warning and nothing happen.In Mdx's testsuite
dune.incfiles are changed because of line encodingmliunit tests are failing because of line encodingmdx-test/*tests use POSIX shell features (echo, heredoc,forloops) and unix tools (ls,seq)I'm using Mdx in Odoc's testsuite and I'd like to run tests on Windows.