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

[GC.Infrastructure] More robustness changes for ASP.NET benchmark runs. #3969

Open
mrsharm opened this issue Feb 20, 2024 · 0 comments
Open
Assignees
Labels
gc-infrastructure Labels related to the GC Infrastructure Code

Comments

@mrsharm
Copy link
Member

mrsharm commented Feb 20, 2024

In Progress

  • Update the connection look up strategy to ping the aspnet machines.
  • Fix up the failure yaml and the filters.
  • Add command line to the log file.
  • If the machines reboots, restart the entire run.
  • Overwriting parameters in the csv in the yaml config.
  • Adding Linux container scenarios as a csv.
  • The iteration specified.
  • Make sure containers work with stand alone GC dlls and the traces are valid.
  • Check in ASP.NET to see if artifacts such as GCLog / Traces are available.

To Implement

  • Conditional Dump Collection in case of Failures. [Medium Priority]
  • Save the Crank Job details in a file. [Medium Priority]
  • Send a canary run to discern the exact runtime version. [Low Priority]
  • Stop Run Midway -- add a (Ctrl+C) -> Generates a failed yaml that includes all the tests.
@mrsharm mrsharm added the gc-infrastructure Labels related to the GC Infrastructure Code label Feb 20, 2024
@mrsharm mrsharm self-assigned this Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gc-infrastructure Labels related to the GC Infrastructure Code
Projects
None yet
Development

No branches or pull requests

1 participant