InfrastructureSystems.jl
InfrastructureSystems.jl copied to clipboard
add function to get random seed
This is a step to make sure that over the whole platform the same random seed is used and allows the user to create an ENV variable for reproducibility if they want to.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 79.16%. Comparing base (
711caa4) to head (9e83894). Report is 13 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #457 +/- ##
==========================================
+ Coverage 77.79% 79.16% +1.36%
==========================================
Files 71 72 +1
Lines 5818 5744 -74
==========================================
+ Hits 4526 4547 +21
+ Misses 1292 1197 -95
| Flag | Coverage Δ | |
|---|---|---|
| unittests | 79.16% <100.00%> (+1.36%) |
:arrow_up: |
Flags with carried forward coverage won't be shown. Click here to find out more.
| Files with missing lines | Coverage Δ | |
|---|---|---|
| src/InfrastructureSystems.jl | 55.55% <ø> (ø) |
|
| src/random_seed.jl | 100.00% <100.00%> (ø) |
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
If we go with this approach, might be convenient to have a setter too.
If we go with this approach, might be convenient to have a setter too.
I don't think that we can set a env variable from a function like this