Type: required
Title: cwscheckapi replaced with subsequenttests
Posted by: [email protected]
Affected: [email protected],[email protected],-
TaskId: i109707
<http://www.openoffice.org/issues/show_bug.cgi?id=109707>
Effective from: DEV300 CWS sb118
CWS:
<http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300/sb118>
CWS status: new
*Summary*
--------
- solenv/bin/cwscheckapi
- solenv/bin/installoffice
+ solenv/bin/subsequenttests
*Description*
-------------
Quoting <http://qa.openoffice.org/issues/show_bug.cgi?id=109707>:
"CWS sb118 (see
<http://wiki.services.openoffice.org/wiki/Test_Cleanup>) uniformly
places tests that depend on modules up in the build hierarchy (some
unit tests, unoapi tests, etc.) into directories mentioned in
build.lst files but with makefile.mks guarded by OOO_SUBSEQUENT_TESTS.
"solenv/bin/cwscheckapi used to run unoapi tests, by default for only
those modules modified by a CWS (broken for HG-based CWSs).
"cwscheckapi can be subsumed by a new tool,
solenv/bin/subsequenttests, that scans all build.lst files for
makefile.mks mentioning OOO_SUBSEQUENT_TESTS and calling dmake on all
of those."
subsequenttests requires a complete OOo build, up through module
smoketestoo_native, as prerequisite. Quoting
<http://hg.services.openoffice.org/cws/sb118/file/8bd61fad2965/solenv/bin/subsequenttests#l42>:
print STDERR "usage: $0 [-P<n>] [-- <args>]\n";
print STDERR " -P<n> number of parallel dmake invocations\n";
print STDERR " <args> are passed to dmake invocations\n";
@Gregor: Can you include a call of subsequenttests, if present in a
CWS, after the Smoketest step in the buildbot scripts?
@Bernd: Note that this will render the CWSCheckAPI entries on a CWS
EIS page meaningless. Unlike cwscheckapi, subsequenttests does not
report any status to EIS.
solenv/bin/installoffice (and a few other solenv/bin scripts) was only
used by cwscheckapi and has consequently also been removed.
Send feedback to [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
