You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the time since utility python module share/trick/trickops/send_hs.py was added to TrickOps (3/2023), Trick has moved on to a different output in the send_hs file that gets created, so this utility module is currently broken in the latest state of master. When I originally added send_hs.py it was not added with unit testing, so it's break was never discovered by Trick's CI.
What this issue will address
In this issue I will update send_hs.py to work with the latest output and add a unit test to cover it's usage, something I should have done in the first place!
What we use it for
For the curious, we use this module to help us get send_hs data into a format we can more easily plot in our CI system. For example, here's one such plot showing us how our realtime performance ratio changes over time, where the x-axis is CI job number. It's a nice way for us to see if anything comes into our production branches that significantly affect realtime performance.
Each colored line represents one of our Orion scenarios we continually test in CI. Happy to provide more details on the plot if anyone in the community is interested in the details.
* Update pip when testing trickops
* Remove MonteCarloGenerationhelper.py's
* unecessary dependency on send_hs
* Update send_hs.py to work with the new fields Trick's output produces.
TODO: unit tests
Closes#1807
Background
In the time since utility python module
share/trick/trickops/send_hs.py
was added to TrickOps (3/2023), Trick has moved on to a different output in thesend_hs
file that gets created, so this utility module is currently broken in the latest state ofmaster
. When I originally addedsend_hs.py
it was not added with unit testing, so it's break was never discovered by Trick's CI.What this issue will address
In this issue I will update
send_hs.py
to work with the latest output and add a unit test to cover it's usage, something I should have done in the first place!What we use it for
For the curious, we use this module to help us get
send_hs
data into a format we can more easily plot in our CI system. For example, here's one such plot showing us how our realtime performance ratio changes over time, where the x-axis is CI job number. It's a nice way for us to see if anything comes into our production branches that significantly affect realtime performance.Each colored line represents one of our Orion scenarios we continually test in CI. Happy to provide more details on the plot if anyone in the community is interested in the details.
FYI @sharmeye @jmpenn @hchen99 for awareness
The text was updated successfully, but these errors were encountered: