Skip to content

Commit

Permalink
Fixed linting issues
Browse files Browse the repository at this point in the history
  • Loading branch information
mrsharm committed Aug 23, 2023
1 parent 53ea22c commit 54a8b87
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions src/benchmarks/gc/GC.Infrastructure/docs/ASPNETBenchmarks.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,9 @@ There are four main types of errors while running ASP.NET Benchmarks using crank

### 1. Inability To Connect To The Server

The typical error message associated with this is of the following form:
The typical error message associated with this is of the following form:

```
```cmd
The specified endpoint url 'http://asp-citrine-win:5001' for 'application' is invalid or not responsive: "No such host is known. (asp-citrine-win:5001)"
```

Expand All @@ -26,5 +26,4 @@ Fix arguments by refering to [this](https://github.com/dotnet/crank/blob/main/sr
The test failures could be as a result of either runtime failures or failures of running the benchmark on the managed side of things. For both of these issues examine the log file to identify the reasons.

### 4. Missing Artifacts

Check failure on line 28 in src/benchmarks/gc/GC.Infrastructure/docs/ASPNETBenchmarks.md

View workflow job for this annotation

GitHub Actions / lint

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### 4. Missing Artifacts"]

For the case of missing artifacts such as missing traces, examine the log file for the exception reasons.

Check failure on line 29 in src/benchmarks/gc/GC.Infrastructure/docs/ASPNETBenchmarks.md

View workflow job for this annotation

GitHub Actions / lint

Files should end with a single newline character

0 comments on commit 54a8b87

Please sign in to comment.