Confirmed users
563
edits
NSS:TryServer: Difference between revisions
m
clarify NSPR instructions
(→Overview: updated -t, -u and -p) |
m (clarify NSPR instructions) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 61: | Line 61: | ||
-e all (or "none") | -e all (or "none") | ||
[default is "none" if omitted] | [default is "none" if omitted] | ||
--nspr-patch | |||
</pre> | </pre> | ||
| Line 69: | Line 71: | ||
==Platforms (-p / --platform)== | ==Platforms (-p / --platform)== | ||
The currently available platforms are <code>linux</code>, <code>linux64</code>, <code>linux-make</code>, <code>linux64-make</code>, <code>linux-fuzz</code>, <code>linux64-fuzz</code>, <code>linux64-asan</code>, <code>linux64-fips</code>, <code>win64</code>, <code>win64_make</code>, <code>win</code>, <code>win_make</code> and <code> | The currently available platforms are <code>linux</code>, <code>linux64</code>, <code>linux-make</code>, <code>linux64-make</code>, <code>linux-fuzz</code>, <code>linux64-fuzz</code>, <code>linux64-asan</code>, <code>linux64-fips</code>, <code>win64</code>, <code>win64_make</code>, <code>win</code>, <code>win_make</code>, <code>aarch64</code> and <code>mac</code>. Specify any combination of those, like <code>-p linux,win64</code>, to choose the platforms your patch should be tested on. If you want to test all platforms use <code>-p all</code>, if you want no platforms (which is only useful when you want only tools, see below) then use <code>-p none</code>. | ||
==Unit tests (-u / --unittests)== | ==Unit tests (-u / --unittests)== | ||
The currently available test suites are <code>bogo</code>, <code>crmf</code>, <code>chains</code>, <code>cipher</code>, <code>db</code>, <code>ec</code>, <code>fips</code>, <code>gtest</code>, <code>interop</code>, <code>lowhash</code>, <code>merge</code>, <code>sdr</code>, <code>smime</code>, <code> | The currently available test suites are <code>bogo</code>, <code>crmf</code>, <code>chains</code>, <code>cipher</code>, <code>db</code>, <code>ec</code>, <code>fips</code>, <code>gtest</code>, <code>interop</code>, <code>lowhash</code>, <code>merge</code>, <code>sdr</code>, <code>smime</code>, <code>ssl</code>,<code>tlsfuzzer</code> and <code>tools</code>. Specify any combination of those, like <code>-u ec,gtest</code>, to choose the test suites to run with your patch. If you want to run all test suites use <code>-u all</code>, if you want no tests use <code>-u none</code>. | ||
==Tools (-t / --tools)== | ==Tools (-t / --tools)== | ||
| Line 82: | Line 84: | ||
Specify either <code>all</code> or <code>none</code> to enable or disable extra builds. The number and type of extra builds varies per platform. | Specify either <code>all</code> or <code>none</code> to enable or disable extra builds. The number and type of extra builds varies per platform. | ||
==Enable NSPR changes (--nspr-patch)== | |||
Mozilla doesn't maintain separate infrastructure for the NSPR project, but you can test NSPR changes in nss-try. Use a patch file that was created by executing "hg diff" in the top level nspr directory and is named nspr.patch. Copy that patch into the main nss directory (nss/nspr.patch). Include the patch in your submission to nss-try and add parameter --nspr-patch. | |||
=Try syntax implementation= | =Try syntax implementation= | ||