Skip to content

testsuite: extend the make one target#1530

Closed
shindere wants to merge 1 commit intoocaml:trunkfrom
shindere:testsuite-running-improvement
Closed

testsuite: extend the make one target#1530
shindere wants to merge 1 commit intoocaml:trunkfrom
shindere:testsuite-running-improvement

Conversation

@shindere
Copy link
Copy Markdown
Contributor

Until now, the make one DIR=... command was able to handle only
directories containing legacy tests.

This PR extends the target so that it can also handle directories
containing ocamltest-driven tests.

Until now, the make one DIR=... command was able to handle only
directories containing legacy tests.

This commit extends the target so that it can also handle directories
containing ocamltest-driven tests.
@gasche
Copy link
Copy Markdown
Member

gasche commented Dec 14, 2017

Thanks a lot, I was thinking of making this PR today but I didn't find the time.

@gasche
Copy link
Copy Markdown
Member

gasche commented Dec 14, 2017

Thanks, I was thinking of making this PR today but I didn't find the time.

This is good to merge if the CI approves... but it looks like the CI is not happy.

@gasche
Copy link
Copy Markdown
Member

gasche commented Dec 14, 2017

Summary of the CI output:

[...]
 ... testing 'w58.opt.ml' with ocamlopt: => passed
 ... testing 'w55.opt_backend.ml' with ocamlopt: => passed
 ... testing 'w59.opt_backend.ml' with ocamlopt: => passed
Running tests from 'tests/win-unicode' ...
 ... testing 'exec_tests.ml': => skipped
 ... testing 'mltest.ml': => skipped
 ... testing 'symlink_tests.ml': => skipped
make[2]: *** [retries] Error 3
make[1]: *** [legacy-without-report] Error 2
make: *** [all] Error 2

(all tests reported in the log are skipped or a success.)

@shindere
Copy link
Copy Markdown
Contributor Author

shindere commented Dec 14, 2017 via email

@shindere
Copy link
Copy Markdown
Contributor Author

shindere commented Dec 14, 2017 via email

@shindere
Copy link
Copy Markdown
Contributor Author

Some help would be welcome on that one:

  1. Is there a way to run AppVeyor again, to make sure the build
    didn't fail randomly?

  2. I was not able to see the output of Travis. What's wrong there?

@gasche
Copy link
Copy Markdown
Member

gasche commented Dec 15, 2017

The log that I have shown is from Travis. I can reproduce it on my machine (cd testsuite; make all). The error comes from the fact that

awk -v retries=1 -v max_retries=5  -f makefiles/summarize.awk <_log >_retries

returns the error code 3.

@shindere
Copy link
Copy Markdown
Contributor Author

shindere commented Dec 15, 2017 via email

@shindere
Copy link
Copy Markdown
Contributor Author

This PR actually breaks an assumption which was important.

Currently, in trunk, the exec-one target of testsuite/Makefile only takes
care of the legacy tests and that was a design choice I forgot, sorry about
that.

The motivation was precisely to be able to run the legacy and new tests
separately.

Can we perhaps close this PR and continue to live wiht the current situation
during the transition stage?

@gasche
Copy link
Copy Markdown
Member

gasche commented Dec 15, 2017

Closing as requested.

There should be a way to both (1) let us run the test in a give directory reliably, no matter how the tests are written and (2) give people the ability to run only legacy tests or only new test. Both features are things people want. To be investigated later.

@gasche gasche closed this Dec 15, 2017
@v-gb v-gb mentioned this pull request Dec 18, 2017
EmileTrotignon pushed a commit to EmileTrotignon/ocaml that referenced this pull request Jan 12, 2024
* Update Platform Guiding Principles

Commit in stronger terms to keeping Platform tools independent and retain the possibility to use their CLIs directly.

* Update data/tutorials/platform/op_00_principles.md

Co-authored-by: Christine Rose <christinerose@users.noreply.github.com>

---------

Co-authored-by: Anil Madhavapeddy <anil@recoil.org>
Co-authored-by: Christine Rose <christinerose@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants