On Wed, Nov 18, 2009 at 11:21 AM, Simon Laws <[email protected]> wrote: > I think we need to include the otests in the build. The thing that > killed us last time was the svn updates from OASIS which didn't work > efficiently. However now some of the test suits are settling down we > could take a cut of the binary artifacts (contributions) and test > against these. Would need to go in our svn for the time being but I > imagine OASIS might publish binary artifacts eventually somehow. > > Thoughts? > > Simon >
I agree that needs to happen, but its not great that it would further add to the already excessive build time and we've only just moved the otest out of trunk as it was a bit of a pain with the way they use externals. I can think of some things we could try to alleviate those issues: - remove some of the existing unit and itests which duplicate otests, may make things slightly quicker though probably not a huge difference - first try to make some progress on the build restructure thread. Having this otest requirement may help motivate progress on that discussion - get snapshots of the OASIS contributions published so the test runners can use those snapshots instead of needing the svn externals. If we can't get OASIS to do it we could just publish them ourselves. ...ant
