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: website_and_docs/content/documentation/webdriver/troubleshooting/logging.en.md
+12-9Lines changed: 12 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ Logger level helps to filter out logs based on their severity.
68
68
69
69
**Actionable Items**
70
70
71
-
Things are logged as warnings if they are something the user needs to take action on. This is mostly used
71
+
Things are logged as warnings if they are something the user needs to take action on. This is often used
72
72
for deprecations. For various reasons, Selenium project does not follow standard Semantic Versioning practices.
73
73
Our policy is to mark things as deprecated for 3 releases and then remove them.
74
74
@@ -129,10 +129,12 @@ Different languages have different level to log information.
129
129
{{< alert-content >}}{{< /alert-content >}}
130
130
{{< /tab >}}
131
131
{{< tab header="Ruby" >}}
132
-
Logs useful information at level: <code>:info</code>
132
+
<p>Because the Ruby <code>Logger</code> class only has one "debug" level, Selenium is currently using the <code>:info</code> level as a general debug mode, and <code>:debug</code> as a lower level debug mode.
133
+
To bring things in line with other languages, we are considering <ahref="https://github.com/SeleniumHQ/selenium/issues/11797">changing this behavior</a>.
134
+
For now, both info and warnings are handled at the default <code>:warn</code> level.</p>
133
135
{{< /tab >}}
134
136
{{< tab header="JavaScript" >}}
135
-
Logs useful information at level: <code>FINER</code>
137
+
Logs useful information at level: <code>INFO</code>
136
138
{{< /tab >}}
137
139
{{< tab header="Kotlin" >}}
138
140
{{< alert-content >}}{{< /alert-content >}}
@@ -184,18 +186,18 @@ Logs can be displayed on `stdout` or stored in a file.
0 commit comments