-
Notifications
You must be signed in to change notification settings - Fork 29
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
Update master #83
Merged
Update master #83
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
trigger CI CI test make sure unittest is installed change python version narrowing test scope for debugging widening test scope a bit increased verbosity commented out TestCLI for debugging try ignore test in CI try skip other tests skip some more skip more tests
Fix tests and add them to CI
…sion Python 3.9 introduced importlib.resources.files which replaces the deprecated pkg_resources. Since we support Python 3.8, we should conditionally import pkg_resources if Python version is <= 3.9 and import importlib.resources otherwise.
When the tracker thread is stopped in Python 3.11 in Github Actions, the last message logged to the INFO channel is not "Monitoring thread ended." but instead "The following components were found: [...]". This breaks our tests only in Github Actions. My hypothesis is that this happens due to a race, so this commit tests that in CI.
Add Python 3.8-3.11 in CI test setup, and fix several version-related bugs.
Add python 3.7 to test pipeline
When the tracker thread is stopped in Python 3.11 in Github Actions, the last message logged to the INFO channel is not "Monitoring thread ended." but instead "The following components were found: [...]". This breaks our tests only in Github Actions. My hypothesis is that this happens due to a race, so this commit tests that in CI. added informative comment
Add Python 3.8-3.11 in CI test setup, and fix several version-related bugs.
Fixed syntax error
Add python 3.7 to test pipeline
type hints code formatting
When the tracker thread is stopped in Python 3.11 in Github Actions, the last message logged to the INFO channel is not "Monitoring thread ended." but instead "The following components were found: [...]". This breaks our tests only in Github Actions. My hypothesis is that this happens due to a race, so this commit tests that in CI. added informative comment Added doc infrastructure using mkdocs and mkdocstrings added parsing docs added better CLI docs Improved CarbonTracker docs Redid first page of docs Fix on python3.8 and add slightly more documentation HPC documentation Parsing documentation align spelling of carbontracker in docs move HPC to index.md Expand Getting Started added Github action for pushing docs fix yml formatting Many type improvements more type hints
type hints code formatting fix test
make tests time-independent fixed some typing
Added docs through MKDocs, hosted on Github Pages
Changes in API caused 400's from api.energidataservice.dk
Test error was caused by change in energidataservice api needing to be reflected in tests. Warnings were caused by use of deprecated datetime.datetime.utcnow()
Currently, the parser only regards lines with "2024-06-26 14:37:59 - Average power usage (W) for {device}: [{float}]" but it should also regard lines without [ and ] like so "2024-06-26 14:37:59 - Average power usage (W) for {device}: {float}" remove redundant print statement
Fix parsing error
fixed energidataservice
Fix logging redudancy on multiple instances
Fix listing log files when amount of std and output logs mismatch
Update dev from master
…issions Update pue and default emissions
Breaking: Change default monitor_epochs to -1
minor: Deprecated EnergiDataService and CarbonIntensityGB
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.
No description provided.