[tor-bugs] #25549 [Core Tor/Tor]: Add tor CI config for AppVeyor
Tor Bug Tracker & Wiki
blackhole at torproject.org
Tue Apr 3 01:18:47 UTC 2018
#25549: Add tor CI config for AppVeyor
-------------------------------------------------+-------------------------
Reporter: isis | Owner: saper
Type: enhancement | Status:
| needs_revision
Priority: Medium | Milestone: Tor:
| 0.3.4.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-ci, tor-testing, 034-roadmap- | Actual Points:
subtask, 034-triage-20180328, |
034-included-20180328 |
Parent ID: #25550 | Points: 2
Reviewer: isis, catalyst | Sponsor:
| Sponsor3
-------------------------------------------------+-------------------------
Comment (by saper):
Updated appveyor.yml:
http://repo.or.cz/tor/appveyor.git/blob/8807cfb47251059482fea948b5be1d7da60888dc:/appveyor.yml
Build logs on AppVeyor:
https://ci.appveyor.com/project/saper/appveyor/build/1.0.44
* `make check` works
* there is no need to --disable-gcc-hardening, removed
* AppVeyor understands separate build and test phases, therefore `make`
and `make install` are kept separate from `make check`
Few things I do not like about the current `make check`:
* main test produces a lot of sub-tests that are reported as one in the
summary (and to find details one needs `test-suite.log` or `test.log`
file). Simple `make test` output was much more readable. This can be fixed
by using a custom automake test driver.
* Tinytest produces a messy output like:
{{{
geoip/load_file: [forking]
FAIL ../src/test/test_geoip.c:409: Unable to load geoip from
"/c/projects/appveyor/src/config/geoip"
FAIL ../src/test/test_geoip.c:411: assert(0 OP_EQ rv): 0 vs -1
[load_file FAILED]
}}}
I hope it can be parsed somehow to be displayed in the AppVeyor's test
output tab.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25549#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list