|
ea12428d
|
2019-12-10T09:25:39
|
|
appveyor: switch to Previous Visual Studio 2019 (VS issues after update)
After update [1] of the Visual Studio 2019 image cmake unable to find
path to the c compiler [2]:
cmake : CMake Error at CMakeLists.txt:47 (project):
At line:1 char:1
+ cmake -G 'Visual Studio 16 2019' -A x64 ..
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (CMake Error at ...t:47 (project)::String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
The CMAKE_C_COMPILER:
C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe
is not a full path to an existing compiler tool.
[1]: https://github.com/appveyor/ci/issues/3231
https://www.appveyor.com/updates/2019/12/09/
[2]: https://ci.appveyor.com/project/libevent/libevent/builds/29431286/job/a68h7dn9rcride9g
|
|
|
aff23122
|
2019-11-17T23:22:53
|
|
appveyor: fix EVENT_CMAKE_OPTIONS expansion (for multiple arguments)
Fixes: 63f73ee2 ("CI: integrate testing for components export")
|
|
|
8be8ac46
|
2019-11-17T02:45:54
|
|
Merge #929 -- cmake package improvements
Example:
find_package(Libevent 2.2.0 REQUIRED COMPONENTS core)
add_executable(test test.c)
target_link_libraries(test ${LIBEVENT_LIBRARIES})
* upstream/pr/929:
CI: integrate testing for components export
cmake: test for find_package()
cmake: improve package config file
|
|
02dc7a1b
|
2019-10-22T22:29:12
|
|
appveyor: fix openssl version mismatch warning
yuangongji:
"Many warnings appear when building and running with Visual Studio 2019 in Appveyor:
WARN C:\projects\libevent\test\regress_ssl.c:210: Version mismatch for openssl: compiled with 1000214f but running with 1000212f
Simply add the openssl binary to the "PATH" environment variable to fix it.
I wrote a simple demo to reproduce it: https://github.com/ygj6/verify
I see there are dozens of openssl libraries in the system of appveyor: https://ci.appveyor.com/project/ygj6/verify/builds/28290688
If you do not specify which openssl to use, the system cannot find the correct library."
|
|
|
28ba0a47
|
2019-11-17T02:37:59
|
|
appveyor: disable parallel tests execution
Refs: https://github.com/libevent/libevent/pull/917#issuecomment-553784701
|
|
|
63f73ee2
|
2019-11-14T18:34:56
|
|
CI: integrate testing for components export
|
|
|
38eb4846
|
2019-10-18T23:32:14
|
|
appveyor: add vs2019 os to test some new features brought by Win10
|
|
|
b32a6443
|
2019-10-09T00:16:50
|
|
Fix all all yamllint warnings in travis/appveyor rules
|
|
|
c88c578a
|
2019-10-09T00:13:01
|
|
appveyor: do not allow any failures
Yes we still have flacky tests, but anyway two main configuration can
fail too (and they do fail from time to time) so let's not allow any
failures and see how this will go.
(Credits to @ygj6 via #910)
|
|
|
72d140c2
|
2019-10-08T22:01:01
|
|
appveyor: fix build script for compiling using mingw-w64
|
|
|
93a92547
|
2019-04-02T23:25:08
|
|
appveyor: check intermediate powershell commands exit codes and terminate early
Otherwise build errors will be ignored, i.e. if build fails but regress
binary exists (copied from artifacts) it will be runned instead of newly
compiled.
|
|
b34192ba
|
2019-02-25T00:26:39
|
|
Ignore bitrise branches for travis-ci/appvyeor [ci skip]
|
|
|
e2e82241
|
2019-01-29T20:58:01
|
|
appveyor: disable verbosity of MSBuild
|
|
|
588ee6df
|
2018-11-24T20:22:40
|
|
appveyor: switch to new VS/MinGW and x64
The cache had been reseted with the following REST API requests:
DELETE https://ci.appveyor.com/api/projects/nmathewson/libevent/buildCache
DELETE https://ci.appveyor.com/api/projects/libevent/libevent/buildCache
DELETE https://ci.appveyor.com/api/projects/azat/libevent/buildCache
|
|
|
f88b8946
|
2019-01-29T10:10:23
|
|
Add OS-specific exclude patterns of the branch names for the CI
|
|
|
51945fd9
|
2018-12-17T21:41:32
|
|
appveyor: cover static libs for MSVC
|
|
|
1a79fd38
|
2018-11-21T07:04:33
|
|
appveyor: enable parallel build
|
|
|
9afe7a6c
|
2018-11-06T11:30:18
|
|
appveyor: skip travis patches (by commit subject/files)
|
|
|
54fdd6bb
|
2018-11-05T17:04:47
|
|
appveyor: cache build directory to reduce overall time (6x time faster)
various build checks (i.e. detecting headers/macroses/functions) takes
7 minutes (from 13 minutes in total) for cmake, which is too high.
By using cache we can reduce this to ~0.
And set APPVEYOR_SAVE_CACHE_ON_ERROR so that cmake checks will be
cached (anyway all sources will be built from scratch due to timestamp
updates while extracting from sources).
|
|
|
50618935
|
2018-11-06T01:22:13
|
|
appveyor: disable verbosity
|
|
|
1503a9a1
|
2018-11-05T18:00:41
|
|
appveyor: do not run on branches that has "travis" in it's name
|
|
|
e17e1ee9
|
2018-10-28T20:52:32
|
|
appveyor: reconfigure tests with allow_failure and fast_finish
|
|
|
29cc8386
|
2018-08-18T23:50:10
|
|
appveyor: add all build tree into artifacts in case of failure
This will help in investigations of win32 failures...
P.S. looks like there is no better way, since
"artifacts.*.publish_on_failure" hadn't been implemented yet (while was
requiested in 2015).
|
|
|
bdd53128
|
2018-08-01T03:01:43
|
|
appveyor: disable almost all configurations (except autotools/cmake basic)
Since we have FREE plan, we have a lot of limits on our builds, so let's
reduce their amount to make them run/start faster (I hope).
|
|
|
e01b9937
|
2017-03-08T23:48:30
|
|
appveyor: remove -DEVENT__ENABLE_VERBOSE_DEBUG=ON build
See-also: c199df7bc78824ff579ff34c5f9f922034e8fa31 ("travis-ci: remove
-DEVENT__ENABLE_VERBOSE_DEBUG=ON (too much useless logs)")
|
|
|
efcfa046
|
2017-01-29T18:13:07
|
|
Bump version in master to 2.2.0-alpha-dev
And according to f8d80a285cf941505277d9060d0357b5b7e543d2 ("Bump version
to 2.1.3-alpha-dev") numeric version have 1 at the end, since it means
"-dev".
|
|
|
9b63b5d4
|
2017-01-22T18:21:57
|
|
Bump version to 2.1.8-stable everywhere
P.S. in referenced commit I made a mistake and instead of *-rc* I wrote
*-beta*.
See-also: f4489b8323cda0bf8eed7c1353911a852d7a947c ("Bump version to
2.1.7-beta everywhere")
|
|
|
108b5fef
|
2017-01-20T16:31:17
|
|
Run tests in parallel (they are lightweight), on CI and vagrant boxes
By default 20 parllel jobs, but one caveat for travis-ci, osx boxes
there slower and have less resources then linux (discovered during
testing), so limit number of parallel jobs to 4 there, and also install
travis_wait, so that travis-ci will not fail the build when there is no
output for 10 minutes, since for osx boxes it is very likely.
Refs: travis-ci/travis-ci@7202
|
|
|
f4489b83
|
2016-11-02T00:31:31
|
|
Bump version to 2.1.7-beta everywhere
- cmake basic
- cmake detecting from git -- event_fuzzy_version_from_git()
- autotools
- win32
- appveyor
|
|
|
51019e94
|
2016-07-13T17:40:48
|
|
Bump version to 2.1.6-beta everywhere
- cmake basic
- cmake detecting from git -- event_fuzzy_version_from_git()
- autotools
- win32
- appveyor
|
|
|
6fcfa25d
|
2016-08-08T17:25:11
|
|
appveyor/autotools: link with openssl by passing LDFLAGS/CFLAGS
This never works, hence green tests in production. and now it works:
https://ci.appveyor.com/project/azat/libevent/build/2.1.5.100/job/eib4xqfb7d3ruo16
(look by /"evthread_win32.c")
|
|
|
4634b85b
|
2016-08-08T15:34:57
|
|
appveyor: image already had openssl installed
Fixes messages like "Version mismatch for openssl: compiled with 1000201f but
running with 1000208f" [1].
According to next link:
http://help.appveyor.com/discussions/questions/1132-openssl-installation-issues
Refs: appveyor/ci#576
[1]: https://ci.appveyor.com/project/azat/libevent/build/2.1.5.95/job/dcy9cfoj3rfo4gdh
|
|
|
e9acc441
|
2016-08-07T23:51:21
|
|
appveyor: check -DUNICODE -D_UNICODE according to ReleaseChecklist (cmake only)
Link: https://github.com/libevent/libevent/wiki/ReleaseChecklist
|
|
|
18108574
|
2016-08-07T21:30:04
|
|
appveyor: ignore failure of mingw-get
Since according to doc [1], appveyour will fail the build on every powershell's
exception:
"PowerShell script is considered successful if it finishes without exception."
[1]: https://www.appveyor.com/docs/build-configuration#powershell
|
|
|
ac90133c
|
2016-08-07T20:52:41
|
|
appveyor: drop shallow_clone, since we use tags for detecting version in cmake
|
|
|
8f950155
|
2016-06-19T14:15:41
|
|
appveyor: support cmake & autotools using build matrix (like travis-ci has)
This will allow us to avoid possible compilation regressions, and also some
failures in different environments (for example because of different
sizeof(size_t)).
For example we can avoid next issues:
- #361
- #314
- #311
(And I'm pretty sure that this is not complete list)
And of course it reduce job for maintainers.
But it also have one downside, appveyor doesn't have such concurrency like
travis-ci, so it can take a while to finish the whole build, but we can resolve
this later, or reduce build matrix to only one for autotools and one for cmake.
Fixes: #364
|
|
1cc2e295
|
2015-05-12T00:27:01
|
|
Use autotools for appveyor until cmake is fixed.
|
|
|
107d565d
|
2015-05-11T12:47:40
|
|
Fix the link for appveyor OpenSSL installer (WIN32)
* change and move the openssl self installer off to a site we own
- the old link was 404, probably due to being replaced with a newer
non-vuln version. But since we are only using this installer to
auto-build with on appveyor (not as a release), then having a file
we don't change and own seems to be a better solution.
* reduce verbosity
|
|
26164a56
|
2015-02-05T20:21:04
|
|
Forgot to install OpenSSL for appveyor
|
|
|
5f89c37e
|
2015-02-05T19:24:19
|
|
Add support for appveyor.com windows CI
This does the same thing as Travis-CI but for windows.
@nmathewson
Go to: https://ci.appveyor.com/login -> Login using Github
Click **+New Project** -> Choose **Github** to the left -> Find **Libevent** in the list and click **Add**
|