Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

optionaltest and shtest should be made to pass on Windows builds #1846

Closed
Mindavi opened this issue Feb 26, 2019 · 5 comments
Closed

optionaltest and shtest should be made to pass on Windows builds #1846

Mindavi opened this issue Feb 26, 2019 · 5 comments
Labels

Comments

@Mindavi
Copy link

Mindavi commented Feb 26, 2019

Describe the bug
Failed test on appveyor don't trigger a 'fail' on the test run.

To Reproduce

Go to appveyor and look at the test logs. These contain lines like this

============================================================================
Testsuite summary for jq 1.6-51-g9a0d5be
============================================================================
# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0
============================================================================
See ./test-suite.log

https://ci.appveyor.com/api/buildjobs/9jhag16jw73arl27/log (text log)
https://ci.appveyor.com/project/stedolan/jq/build/job/9jhag16jw73arl27 (test page)

Expected behavior
Failed test within appveyor will give a failure status for the tests instead of seemingly passing.

Environment (please complete the following information):

  • OS and Version: Windows
  • jq version: jq 1.6-51-g9a0d5be (master branch)
@nicowilliams
Copy link
Contributor

For optionaltest and shtest this is on purpose. Failures of any of the others do cause appveyor build failures.

See appveyor.yml:

test_script:
  # tests/optionaltest and tests/shtest fail on Windows; run them
  # anyways but ignore their failures.  Also, trace shtest.
  - bash -lc "exec 0</dev/null && cd $APPVEYOR_BUILD_FOLDER && make -j3 SUBDIRS= 'TESTS=tests/mantest tests/jqtest tests/onigtest tests/base64test' check"
  - bash -lc "exec 0</dev/null && cd $APPVEYOR_BUILD_FOLDER && make SUBDIRS= TESTS=tests/optionaltest check || true"
  - bash -lc "exec 0</dev/null && cd $APPVEYOR_BUILD_FOLDER && make SUBDIRS= TRACE_TESTS=1 TESTS=tests/shtest check || true"

Basically, we have to do some work to get these to pass on Windows.

@nicowilliams nicowilliams changed the title Failed tests on appveyor for windows not triggering a test failure optionaltest and shtest failures purposefully ignored in Appveyor build Feb 26, 2019
@Mindavi
Copy link
Author

Mindavi commented Apr 9, 2019

I guess this can be closed

@Mindavi Mindavi closed this as completed Apr 9, 2019
@nicowilliams nicowilliams changed the title optionaltest and shtest failures purposefully ignored in Appveyor build optionaltest and shtest should be made to pass on Windows builds Apr 9, 2019
@nicowilliams nicowilliams reopened this Apr 9, 2019
@nicowilliams
Copy link
Contributor

I think we should leave this open. We really should fix these failures.

@nicowilliams
Copy link
Contributor

Thanks for creating this issue!

@itchyny
Copy link
Contributor

itchyny commented Jun 25, 2023

Closing as we now run Windows CI on GitHub Actions, limiting the target by TESTS=. Portability of shtest is tracked by #1079.

@itchyny itchyny closed this as completed Jun 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants