[jenkins/tests] - add unit test support for win32 on jenkins #6815
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Yay been waiting to this. The webserver tests aren't network related, they hang on the stop method so everytime a test is done it hangs there for 120s which I assume is some timeout. |
|
I have a fix ready for htmltow btw, just haven't submitted it |
|
anyone against this? else i will merge this evening (excluding the webserver tests until the issues with libmicrohttpd are solved) |
|
How are these run btw? Is it a separate trigger? |
|
No they run once a night automatically from mainline or you can activate unit tests when building manually over the jenkins interface. |
|
nice, that was exactly what I was after really :) |
Memphiz
added a commit
that referenced
this pull request
Mar 26, 2015
[jenkins/tests] - add unit test support for win32 on jenkins
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the title says.
Here are the current test results:
http://jenkins.kodi.tv/job/WIN-32/4208/testReport/
The CharsetConverter errors i will fix in a different PR (missing initialisation of CSettings singleton...)
ATM the jenkins script scipts the WebServer unit tests because they seem to have network issues (needing 120 secs for most of the tests but don't fail) which might or might not be firewall related.