Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add --detailed feature to buidltest report command #1558

Closed
wants to merge 31 commits into from

Conversation

szuananwar
Copy link
Collaborator

This new feature will let the user to run
buildtest rt --format name,id,user,state,returncode,runtime,outfile,errfile,buildspec --count=1
By running
buildtest rt --detailed

szuananwar and others added 28 commits June 16, 2023 15:07
Add symbolic link of runtime_status_test to buildterst/tests/builders
@szuananwar szuananwar linked an issue Jul 17, 2023 that may be closed by this pull request
7 tasks
@szuananwar szuananwar self-assigned this Jul 17, 2023
Comment on lines +1 to +91
system:
generic:
# specify list of hostnames where buildtest can run for given system record
hostnames: [".*"]

# system description
description: Generic System
# specify module system used at your site (environment-modules, lmod)
moduletool: N/A

# specify test timeout duration in number of seconds
# timeout: 60

# pool size for parallel processing using multiprocessing.Pool. Pool Size must be 1 or higher. The pool size is calculated as follows: poolsize = min(poolsize, os.cpu_count())
poolsize: 1

# determine whether to enable pagination
pager: False

buildspecs:
# whether to rebuild cache file automatically when running `buildtest buildspec find`
rebuild: False
# limit number of records to display when running `buildtest buildspec find`
count: 15
# format fields to display when running `buildtest buildspec find`, By default we will show name,description
format: "name,description"
# enable terse mode
terse: False
# specify list of directories to search for buildspecs when building cache
#root: [ $BUILDTEST_ROOT/examples, /tmp/buildspecs ]
report:
count: 25
#enable terse mode for report
terse: False
format: "name,id,state,runtime,returncode,buildspecs"
# show the latest for every test
latest: True
# show the oldest for every test
oldest: False

executors:
# define local executors for running jobs locally
local:
bash:
description: submit jobs on local machine using bash shell
shell: bash
sh:
description: submit jobs on local machine using sh shell
shell: sh
csh:
description: submit jobs on local machine using csh shell
shell: csh
zsh:
description: submit jobs on local machine using zsh shell
shell: zsh
# compiler block
compilers:
# a list of directories to search for modules
# modulepath: ['/tmp', '/var/']

# regular expression to search for compilers based on module pattern. Used with 'buildtest config compilers find' to generate compiler instance
# find:
# gcc: "^(gcc)"
# intel: "^(intel)"
# cray: "^(craype)"
# pgi: "^(pgi)"
# cuda: ^(cuda)"
# clang: "^(clang)"

# declare compiler instance which can be site-specific. You can let 'buildtest config compilers find' generate compiler section
compiler:
gcc:
builtin_gcc:
cc: gcc
fc: gfortran
cxx: g++

# location of log directory
# logdir: /tmp/

# specify location where buildtest will write tests
# testdir: /tmp

# specify one or more directory where buildtest should load buildspecs
# buildspec_roots: []

cdash:
url: https://my.cdash.org/
project: buildtest
site: generic
buildname: tutorials
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i dont understand why this file is being added.

@szuananwar szuananwar closed this Jul 18, 2023
@szuananwar szuananwar deleted the anwar_branch branch July 18, 2023 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FEATURE]: buildtest report --detailed
2 participants