MetzNet
/
dfhack
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

disable fortress mode tests in CI for now 

until we get a reuable fortress save set up
develop
myk002 2021-05-05 12:51:53 -07:00
parent e07635b345
commit 7060c297a8
No known key found for this signature in database
GPG Key ID: 8A39CA0FA0C16E78
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/changelog.txt
Unescape Escape View File

@ -52,7 +52,7 @@ changelog.txt uses a syntax similar to RST, with a few special sequences:
- The DFHack test harness is now much easier to use for iterative development. Configuration can now be specified on the commandline, there are more test filter options, and the test harness can now easily rerun tests that have been run before.
- The ``test/main`` command to invoke the test harness has been renamed to just ``test``
- DFHack unit tests must now match any output expected to be printed via ``dfhack.printerr()``
- ``fortress mode`` is now supported for unit tests (tests that require a fortress map to be loaded)
- ``fortress mode`` is now supported for unit tests (tests that require a fortress map to be loaded). Note that fortress mode tests will be skipped by the continuous integration framework for now. They'll be re-enabled once we get a reusable fortress save set up.
# 0.47.05-r1

2
travis/run-tests.py
Unescape Escape View File

@ -73,7 +73,7 @@ with open(test_init_file, 'w') as f:
f.write('''
devel/dump-rpc dfhack-rpc.txt
:lua dfhack.internal.addScriptPath(dfhack.getHackPath())
test --resume "lua scr.breakdown_level=df.interface_breakdown_types.%s"
test --resume --modes=none,title "lua scr.breakdown_level=df.interface_breakdown_types.%s"
''' % ('NONE' if args.no_quit else 'QUIT'))
test_config_file = 'test_config.json'