Confirmed users
4,467
edits
User:Lukasblakk/TryServerSyntax: Difference between revisions
Jump to navigation
Jump to search
→Using the Try Syntax
| Line 64: | Line 64: | ||
* then splits on ' ' to create a list to pass to argparse which runs parse_known_args (thus keeping anything that is not recognized from causing errors) | * then splits on ' ' to create a list to pass to argparse which runs parse_known_args (thus keeping anything that is not recognized from causing errors) | ||
* we also have allowed for manual sendchanges to send in comments with "try: ..." in order to make it possible to (re)run a particular test/talos/platform and not all things specified in a commit message | * we also have allowed for manual sendchanges to send in comments with "try: ..." in order to make it possible to (re)run a particular test/talos/platform and not all things specified in a commit message | ||
=Using the Try Syntax= | |||
==Default Set== | |||
If you only specify try: or no commit comment is present (or info file) then the default set would be a "Does it compile?" set comprised of: | If you only specify try: or no commit comment is present (or info file) then the default set would be a "Does it compile?" set comprised of: | ||
All try desktop platforms' debug builds, all mobile builds, '''no tests, no talos''' | All try desktop platforms' debug builds, all mobile builds, '''no tests, no talos''' | ||
==Optional arguments== | |||
If the following exist they will be handled as follows: | If the following exist they will be handled as follows: | ||
| Line 88: | Line 88: | ||
--t variables are used to add talos builderNames (if ['all'] then all available talosBuilders will be added for that platform) | --t variables are used to add talos builderNames (if ['all'] then all available talosBuilders will be added for that platform) | ||
==How do I know what test/talos suites I can list?== | |||
'''Note''': we are using a flat file for right now, '''LINK TO VALID_BUILDERS''' but {{bug|589847}} has been filed and in the next iteration we will have a way to generate the lists of valid builder info dynamically from config.py which will keep it in sync with try's configs | '''Note''': we are using a flat file for right now, '''LINK TO VALID_BUILDERS''' but {{bug|589847}} has been filed and in the next iteration we will have a way to generate the lists of valid builder info dynamically from config.py which will keep it in sync with try's configs | ||
==What do I do if my commit comments don't get me what I want?== | |||
If you missed something in your commit comments you can ping whoever is on buildduty [link] and give them [details] to have the build/test/talos you've missed on your changeset triggered. | If you missed something in your commit comments you can ping whoever is on buildduty [link] and give them [details] to have the build/test/talos you've missed on your changeset triggered. | ||