-
Notifications
You must be signed in to change notification settings - Fork 40
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
Structure log messages #231
Comments
negiDharmendra
added a commit
that referenced
this issue
Jul 11, 2019
negiDharmendra
added a commit
that referenced
this issue
Jul 11, 2019
negiDharmendra
added a commit
that referenced
this issue
Jul 11, 2019
negiDharmendra
added a commit
that referenced
this issue
Jul 11, 2019
negiDharmendra
added a commit
that referenced
this issue
Jul 15, 2019
nehashri
pushed a commit
that referenced
this issue
Jul 17, 2019
nehashri
pushed a commit
that referenced
this issue
Jul 17, 2019
nehashri
pushed a commit
that referenced
this issue
Jul 17, 2019
nehashri
pushed a commit
that referenced
this issue
Jul 17, 2019
nehashri
pushed a commit
that referenced
this issue
Jul 17, 2019
At first run Gauge version: 1.0.6.nightly-2019-07-16
|
nehashri
added a commit
to getgauge/gauge
that referenced
this issue
Jul 19, 2019
Runners related logs added properly to gaulge.log file.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Gauge can now understand plugin's log messages when it is structured properly (refer getgauge/gauge#216) for changes made in Gauge. The runner must now start logging in this format so that Gauge understands the messages properly.
The text was updated successfully, but these errors were encountered: