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
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ v20.8.0
72
72
```
73
73
74
74
## 1.2 Downloading the pre-built binaries and starting the server
75
-
Builiding all frameworks can be challenging. There's a new way that allows to skip that and just run the benchmark without builiding all implementationss.
75
+
building all frameworks can be challenging. There's a new way that allows to skip that and just run the benchmark without builiding all implementations.
76
76
77
77
78
78
Start with checking out a tagged release like that. Pick the release that you want (e.g. chrome 100):
@@ -106,13 +106,13 @@ npm run results
106
106
Open js-framework-benchmark/webdriver-ts-results/table.html in a browser and take a look at the results. You can open the result table with the link [http://localhost:8080/webdriver-ts-results/table.html](http://localhost:8080/webdriver-ts-results/table.html)
107
107
108
108
109
-
Here's what you should do when the benchmark run was not sucessful. Let's assume the benchmark printed the following to the console:
109
+
Here's what you should do when the benchmark run was not successful. Let's assume the benchmark printed the following to the console:
110
110
```
111
111
================================
112
112
The following benchmarks failed:
113
113
================================
114
114
Executing frameworks/non-keyed/ef-js and benchmark 04_select1k failed: No paint event found
115
-
run was not completely sucessful Benchmarking failed with errors
115
+
run was not completely successful Benchmarking failed with errors
116
116
```
117
117
You'll now have to run the benchmark again for those that failed like that:
0 commit comments