Comments

• 

  almost 4 years ago by apappas | Reply

  cc @ilausuch

×
Edit Comment 5204
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
cc [@ilausuch](/users/ilausuch)
 
×
Reply to apappas
cc @ilausuch
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  almost 4 years ago by ilausuch | Reply

  I joined this project because it is really interesting and useful. In my case, I would like to explore 2 different ways with the same objective 1. Use of lnav 2. Use of JS parsers to integrate in the openQA application

×
Edit Comment 5226
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
I joined this project because it is really interesting and useful. In my case, I would like to explore 2 different ways with the same objective 1. Use of lnav 2. Use of JS parsers to integrate in the openQA application
 
×
Reply to ilausuch
I joined this project because it is really interesting and useful. In my case, I would like to explore 2 different ways with the same objective 1. Use of lnav 2. Use of JS parsers to integrate in the openQA application
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  almost 4 years ago by asmorodskyi | Reply

  Just share my experience because I had similar idea but it failed . So one might learn in my failure to not do same mistakes . This is what I have done https://github.com/asmorodskyi/scripts/blob/archiveautoinstlogparse/autoinst_logparse.py . Idea was to download raw openQA logs parse it with some smart python code and generate html file which filter out some useless ( from my POV ) messages and show you colored eye-candy log file . Also I had more ideas how to improve this log but I drop this project at some point ( currently it is deleted from master and only stay in dedicated branch so I can reuse it ) . The reason why I drop it was that approach became very fragile to any kind of changes in openQA raw log . Any new message type or even reformat of existing message in the log lead to hard to debug errors during execution . So I see two solutions here - you need to have very good unit test coverage which can take any random autoinst-log.txt and give answer about every function in isolation if it is still applicable to current log format , or you need to convince tools team to support you approach :) Of course all this applicable only if you have a hope to go for something more than just hackweek project which will be thrown away after a week ;) Feel free to reach me with any questions ( if you have any )

×
Edit Comment 5242
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Just share my experience because I had similar idea but it failed . So one might learn in my failure to not do same mistakes . This is what I have done https://github.com/asmorodskyi/scripts/blob/archive_autoinst_logparse/autoinst_logparse.py . Idea was to download raw openQA logs parse it with some smart python code and generate html file which filter out some useless ( from my POV ) messages and show you colored eye-candy log file . Also I had more ideas how to improve this log but I drop this project at some point ( currently it is deleted from master and only stay in dedicated branch so I can reuse it ) . The reason why I drop it was that approach became very fragile to any kind of changes in openQA raw log . Any new message type or even reformat of existing message in the log lead to hard to debug errors during execution . So I see two solutions here - you need to have very good unit test coverage which can take any random autoinst-log.txt and give answer about every function in isolation if it is still applicable to current log format , or you need to convince tools team to support you approach :) Of course all this applicable **only** if you have a hope to go for something more than just hackweek project which will be thrown away after a week ;) Feel free to reach me with any questions ( if you have any )
 
×
Reply to asmorodskyi
Just share my experience because I had similar idea but it failed . So one might learn in my failure to not do same mistakes . This is what I have done https://github.com/asmorodskyi/scripts/blob/archiveautoinstlogparse/autoinst_logparse.py . Idea was to download raw openQA logs parse it with some smart python code and generate html file which filter out some useless ( from my POV ) messages and show you colored eye-candy log file . Also I had more ideas how to improve this log but I drop this project at some point ( currently it is deleted from master and only stay in dedicated branch so I can reuse it ) . The reason why I drop it was that approach became very fragile to any kind of changes in openQA raw log . Any new message type or even reformat of existing message in the log lead to hard to debug errors during execution . So I see two solutions here - you need to have very good unit test coverage which can take any random autoinst-log.txt and give answer about every function in isolation if it is still applicable to current log format , or you need to convince tools team to support you approach :) Of course all this applicable only if you have a hope to go for something more than just hackweek project which will be thrown away after a week ;) Feel free to reach me with any questions ( if you have any )
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview