[DO NOT MERGE] Test CI with omnitrace updates #248
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
jrmadsen
commented
Jun 27, 2022
jrmadsen
commented
- omnitrace has been a proof-of-concept for using timemory as a toolkit to rapidly build a full-featured profiling and tracing tool
- Many miscellaneous updates were required to pull this off and the number of updates got out of hand
- Thus, I am opening this PR to check whether all the testing is passing before attempting to split the changes into several PRs
- avoid returning const ref for trivially copyable type
- fixed ambiguous error with data_tracer_tests - updated nccl-tests submodule
- Settings how have categories - Fix to defines.h and version.h as submodule
- add_secondary fix - plotting header include fix - fix to operation::finalize::get - fix to operation::finalize::merge - fix to graph_data - fixed types in storage/node.hpp
CircleCI: install sed via conda in python-install CircleCI: disable libunwind for python-install
- e.g. rusage_cache{ RUSAGE_SELF } or rusage_cache{ RUSAGE_THREAD }
- strict config option
- improved variable support
- $env: lvalues
- support for ${VARIABLE} syntax
- support for variable expansion in substring
- chained config files
- context_handler::m_enabled - context_handler::operator() returns if not enabled
- mpi_get also uses binary serialization when a vector of arithmetic types
- initialization of PAPI causing failures in hybrid_tests.hybrid
- support for overridding the setting serialization
- disable running examples in debug builds since they take too long
- using set_default(...) not longer return true for p.exists("<name>") but get<..>("...") works and the action is executed
- specifying a setting as hidden causes it to be elided from iteration and output serialization
- Removed replace of "__" and "--" causes issues with /__w/.../
- Added support for config variables: %cfg{...}%
- %env{...}% is equivalent to $env{...}
- %cfg{...}% is equivalent to $cfg{...}
jrmadsen
force-pushed
the
setting-categories-and-utility-headers
branch
from
ec3a5af
to
ff2f231
Compare
- fix to settings::push and settings::pop when new settings added by reserving m_order - fix to empty CONFIG_FILE
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.