View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005329||unreal||tests||public||2019-07-12 06:38||2019-12-28 09:44|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||5.0.1||Fixed in Version|
|Summary||0005329: U5: buildbot enhancements|
|Description||Buildbot is looking good on U5 now. We have ub18, deb8, deb9, deb10, fbsd and w10.|
What I want more is:
* clang builds, preferably for all *NIX. I'm thinking of a separate builder with a -clang suffix, like unreal5-ub18-clang. Probably via a separate build account and then use locking. This means the -clang builds will run after gcc, which sounds good to me, I think adding another 6+ VM's just for clang would be excessive :D
* test with specific openssl versions, via a custom path. This basically tests both at the same time (specifying openssl path) and makes it easy to test old openssl versions that we still may want to support. That being said, old openssl versions are also tested automatically via the many OS's.
* we're only testing ubuntu 18 at the moment. we should also test the older long running LTS, ub16, and latest ubuntu.. which is ub19 at the time of writing and ub20 next year.
* any other OS's? yeah.. OS X... but.. :D
|Tags||No tags attached.|
|3rd party modules|
||Also add at least 1 openbsd|
||I think clang is still missing.. definitely need this soon.|
||clang was added. Left to do are: ub19 and.. well.. os x would be nice but probably too much effort for me to install.|
It isn't entirely clear to me if the buildbot website could safely be made public or not. There are a few around that are public, but others have been pulled... making me suspicious about it.
Anyway, have a look at that..
oh, quite important: currently buildbot on Windows is not running the test framework!
This because I use a bash script, so either use mingw or whatever or rewrite it.
Buildbot on Windows is now also running the test framework (since yesterday). It uses a very similar script in unrealircd-tests, it's just called "runwin" rather than "run"
It does not run cipherscan at the moment, which it should.
Also, should split off the tests to a separate buildbot step so it's clear compilation went ok.
||Only leaving this open for cipherscan on Windows.|
|2019-07-12 06:38||syzop||New Issue|
|2019-07-12 06:38||syzop||Relationship added||child of 0005279|
|2019-07-12 20:15||syzop||Note Added: 0020774|
|2019-08-10 11:31||syzop||Note Added: 0020801|
|2019-08-15 14:37||syzop||Note Added: 0020815|
|2019-08-18 15:17||syzop||View Status||private => public|
|2019-08-18 15:54||syzop||Note Added: 0020831|
|2019-08-18 15:54||syzop||Status||new => acknowledged|
|2019-08-22 17:56||syzop||Note Added: 0020839|
|2019-08-28 07:25||syzop||Note Added: 0020861|
|2019-10-06 08:01||syzop||Note Added: 0020940|
|2019-12-28 09:41||syzop||Relationship deleted||child of 0005279|
|2019-12-28 09:44||syzop||Target Version||=> 5.0.1|