-
-
Notifications
You must be signed in to change notification settings - Fork 20
Meeting: 09 16 2022
Shahzeb Siddiqui edited this page Sep 16, 2022
·
7 revisions
- Shahzeb Siddiqui
- Wyatt Spear
- Sijie Xiang
- Prathmesh Sambrekar
- Feedback on new aliases for buildtest commands: https://github.com/buildtesters/buildtest/pull/1233 this includes new aliases for several subcommands including bash completion
buildtest bc -h
(buildtest) ~/Documents/github/buildtest/ [devel] buildtest bc -h
usage: buildtest [options] [COMMANDS] buildspec [-h] ...
optional arguments:
-h, --help show this help message and exit
subcommands:
Buildspec Interface subcommands
edit-file (ef)
Edit buildspec file based on filename
edit-test (et)
Edit buildspec file based on test name
find (f) Query information from buildspecs cache
maintainers (m)
Query maintainers from buildspecs cache
show (s) Show content of buildspec file
show-fail (sf)
Show content of buildspec file for all failed tests
summary (sm) Print summary of buildspec cache
validate (val)
Validate buildspecs with JSON Schema
buildtest rt -h
(buildtest) ~/Documents/github/buildtest/ [devel] buildtest rt -h
usage: buildtest [options] [COMMANDS] report [-h] [--filter FILTER]
[--format FORMAT] [--helpfilter]
[--helpformat] [-f | -p]
[-s START] [-e END] [--latest]
[--oldest] [-c COUNT] [-n] [-t]
[--color COLOR] [--pager]
...
optional arguments:
-h, --help show this help message and exit
--filter FILTER Filter report by filter fields. The filter fields must
be a key=value pair and multiple fields can be comma
separated in the following format: --filter
key1=val1,key2=val2 . For list of filter fields run:
--helpfilter.
--format FORMAT format field for printing purposes. For more details
see --helpformat for list of available fields. Fields
must be separated by comma (usage: --format
<field1>,<field2>,...)
--helpfilter List available filter fields to be used with --filter
option
--helpformat List of available format fields
-f, --fail Retrieve all FAIL tests
-p, --pass Retrieve all PASS tests
-s START, --start START
Retrieve tests by starttime
-e END, --end END Retrieve tests by endtime
--latest Retrieve latest record of particular test
--oldest Retrieve oldest record of particular test
-c COUNT, --count COUNT
Retrieve limited number of rows that get printed
-n, --no-header Don't print headers column used with terse option
(--terse).
-t, --terse Print output in machine readable format
--color COLOR Print output of report table with the selected color.
--pager Enable PAGING when viewing result
subcommands:
Fetch test results from report file and print them in table format
clear (c) Remove all report file
list (l) List all report files
summary (sm) Summarize test report
buildtest cg -h
(buildtest) ~/Documents/github/buildtest/ [devel] buildtest cg -h
usage: buildtest [options] [COMMANDS] config [-h] ...
optional arguments:
-h, --help show this help message and exit
subcommands:
Query information from buildtest configuration file
compilers (co)
Search compilers
edit (e) Open configuration file in editor
executors (ex)
Query executors from buildtest configuration
path (p) Show path to configuration file
systems List all available systems
validate Validate buildtest settings file with schema.
view (v) View configuration file
buildtest it -h
(buildtest) ~/Documents/github/buildtest/ [devel] buildtest it -h
usage: buildtest [options] [COMMANDS] inspect [-h] ...
optional arguments:
-h, --help show this help message and exit
subcommands:
Inspect Test result based on Test ID or Test Name
buildspec (b)
Inspect a test based on buildspec
name (n) Specify name of test
query (q) Query fields from record
list (l) List all test names, ids, and corresponding buildspecs
- Test individual compilers via
buildtest config compilers test <compiler1>
: https://github.com/buildtesters/buildtest/issues/1231 - An option to show a list of colors used with
--color
option such asbuildtest report --helpcolor
flag to buildtest report command: https://github.com/buildtesters/buildtest/issues/1206. - Add color option
buildtest bc find --color
https://github.com/buildtesters/buildtest/issues/1240 -
Mergify is a Github workflow to automatically resolve merge conflicts that can be specified in
.mergify.yml
or.mergify/config.yml
or.github/mergify.yml
. This is relevant for Pull Request that requires resolving merge conflict the bot will do it automatically - Use of pyproject.toml to centralize project configuration this is especially true for files like https://github.com/buildtesters/buildtest/blob/devel/.coveragerc and https://github.com/buildtesters/buildtest/blob/devel/.isort.cfg which could be put in pyproject.toml. Take a look at https://pycqa.github.io/isort/docs/configuration/config_files.html. Take a look at spack project pyproject.toml
- Make use of sphinx-dropdown to hide some long text output to help condense the documentation. We should look into this feature and try to incorporate this into the documentation
- mypy is a static type checker for Python this tool helps convert dynamic typing to static typing. It seems like this is a good practice was mentioned in PEP 484 - Type Hints this will create method annotation such as as one below
def greeting(name: str) -> str:
return 'Hello ' + name
In order to use mypy we should look at running this tool for a subset of source code. See https://mypy.readthedocs.io/en/stable/getting_started.html.