[Logwatch-devel] Sample log files / training set?

[Jason Pyeron]

There are many formats that logwatch handles.

For example there is emerge, we do not have Gentoo and are likely not going to install it just to test logwatch parsing.

We are likely going to test our changes using jenkins (http://stackoverflow.com/questions/15395335/test-coverage-in-jenkins-for-a-perl-application) and validating code coverage along the way.

Is there a set of log files we can use for testing?

-Jason

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- [phone] x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-



------------------------------------------------------------------------------

[John Wilcock]

I'd be happy to send a few sample gentoo emerge logs - just let me know
where to submit them...
--
John

Post by Jason Pyeron
There are many formats that logwatch handles.
For example there is emerge, we do not have Gentoo and are likely not going to install it just to test logwatch parsing.
We are likely going to test our changes using jenkins (http://stackoverflow.com/questions/15395335/test-coverage-in-jenkins-for-a-perl-application) and validating code coverage along the way.
Is there a set of log files we can use for testing?
-Jason

------------------------------------------------------------------------------

[Jason Pyeron]

-----Original Message-----
From: John Wilcock
Sent: Monday, November 28, 2016 01:58
I'd be happy to send a few sample gentoo emerge logs - just
let me know
where to submit them...

Thanks.

Do you want to do a git pull request (https://github.com/pdinc-oss/logwatch /tests/logs/ ) or email them?

--
John

Post by Jason Pyeron
There are many formats that logwatch handles.
For example there is emerge, we do not have Gentoo and are

likely not going to install it just to test logwatch parsing.

Post by Jason Pyeron
We are likely going to test our changes using jenkins

(http://stackoverflow.com/questions/15395335/test-coverage-in-
jenkins-for-a-perl-application) and validating code coverage
along the way.

Post by Jason Pyeron
Is there a set of log files we can use for testing?
-Jason

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- [phone] x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-



------------------------------------------------------------------------------

[Jason Pyeron]

-----Original Message-----
From: John Wilcock
To: Jason Pyeron
Sent: Monday, November 28, 2016 08:14
I'm not familiar with github, so email will be easiest for me
- one recent log from a test box attached, Just ask if you want more.

Thanks, just confirming there is nothing sensitive in the logs.

Also note that logwatch hasn't been particularly good with
emerge logs for quite some time, as you'll see in the
output from logwatch 7.4.3 also attached.

May I assume, you are refering to:

Unsuccessfull exit with:
Status 1 : 3 Time(s)

**Unmatched Entries**
Syncing repository 'gentoo' into '/usr/portage'...
Syncing repository 'sunrise' into '/var/lib/layman/sunrise'...
Starting layman sync for sunrise...
layman sync succeeded: sunrise
laymansync sez... "Hasta la sync ya, baby!"
*** exiting unsuccessfully with status '130'.
Syncing repository 'gentoo' into '/usr/portage'...
Syncing repository 'sunrise' into '/var/lib/layman/sunrise'...
Starting layman sync for sunrise...
layman sync succeeded: sunrise
laymansync sez... "Hasta la sync ya, baby!"

There is an exit with status 130, not in the above list, and all the unmatched entries.

John
-----Original Message-----
From: John Wilcock
Sent: Monday, November 28, 2016 01:58
I'd be happy to send a few sample gentoo emerge
logs - just
let me know
where to submit them...
Thanks.
Do you want to do a git pull request
(https://github.com/pdinc-oss/logwatch /tests/logs/ ) or email them?
--
John
There are many formats that logwatch handles.
For example there is emerge, we do not
have Gentoo and are
likely not going to install it just to test
logwatch parsing.
We are likely going to test our changes
using jenkins
(http://stackoverflow.com/questions/15395335/test-coverage-in-
jenkins-for-a-perl-application) and validating
code coverage
along the way.
Is there a set of log files we can use
for testing?
-Jason
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-
-
- Jason Pyeron PD Inc.
http://www.pdinc.us -
- Principal Consultant 10 West 24th Street
#100 -
- [phone] x333 Baltimore, Maryland
21218 -
-
-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
--------------------------------------------------------------
----------------
_______________________________________________
Logwatch-devel mailing list
https://lists.sourceforge.net/lists/listinfo/logwatch-devel

------------------------------------------------------------------------------

[John Wilcock]

Post by Jason Pyeron

Also note that logwatch hasn't been particularly good with
emerge logs for quite some time, as you'll see in the
output from logwatch 7.4.3 also attached.

Status 1 : 3 Time(s)
**Unmatched Entries**

Indeed there are a few unmatched entries, but I was also referring to
the extraneous "to"s in the Packages Unmerged section and the extraneous
"(NN to of NNN)" in the Package Installed section.

I suspect that the emerge log format must have changed at some point,
but this has been the state of play with logwatch and emerge for several
years so I doubt you'll find anybody still using the ancient emerge
versions that the logwatch emerge script was presumably designed for.

If I get a bit of time I'll see if I can improve the logwatch script
(though my perl skills are somewhat rusty to say the least);
alternatively I'd be happy to test updated versions.