phosphor-logging/tools/example/xyz, branch master

test: add callout-test

2017-03-15T21:11:40+00:00

Add test program which can create callouts based on an input device path. It creates an error, with callouts, with name TestCallout. Change-Id: I96b66b73ae4a9c00daff06222841a13747c07408 Signed-off-by: Deepak Kodihalli

metadata: introduce 'process' keyword

2017-03-15T14:20:14+00:00

An error metadata field that has the 'process' keyword set to true is an indication that this metadata will have some associated action that will take place after this metadata (and associated error) is logged to the journal and before the associated error is committed. The associated action will have to be implemented when adding the 'process' keyword. Add 'process' keyword to an example error definition. Change-Id: I42ab3fa230479000a88a18046548242c0043ac86 Signed-off-by: Deepak Kodihalli

Error log inject tool

2017-03-15T13:42:18+00:00

This tool adds an option to the logging-test to inject an error as specified by command line. Change-Id: I1028bd3964db23ed5ffa50414f7a6cc2f880c40c Signed-off-by: Michael Tritz

Include namespaces in the phosphor-logging exception name

2017-03-02T16:27:03+00:00

Currently the phosphor-logging exception name is for example Device for an error file located in xyz/openbmc_project/Error/Callout/. It should instead be named xyz.openbmc_project.Error.Callout.Device following the naming structure of the sdbusplus++ tool to differentiate it from other Device error exceptions. With the full name, the namespaces can be determined, so there's no need to pass the namespace parameter to the template that generates the elog-errors.hpp. As with the name, follow the namespace structure of the sdbusplus exception object. Closes openbmc/phosphor-logging#2 Change-Id: I960d759d90aa18fd43211034ebd6009859113ee7 Signed-off-by: Adriana Kobylak

Move inherits keyword from errors.yaml to metadata.yaml

2017-02-20T13:04:58+00:00

The metadata.yaml file is the correct location for the inherits. Update the elog-gen.py parser to support this change. Change-Id: Iac7f67ec72e761ab3dafbf89c7e4d5495b34f00d Signed-off-by: Adriana Kobylak

elog-gen.py : order inherited errors

2017-01-27T16:43:03+00:00

The elog-gen.py script should process errors such that the generated code has definitions for parent errors before their child errors are defined. Change-Id: I035292731346bdba969f549c7e4033066814890f Signed-off-by: Deepak Kodihalli

elog-gen.py : get inherited-from error

2017-01-27T16:42:25+00:00

Openbmc error interfaces can inherit other error interfaces, thereby allowing to combine metadata across errors. The current implementation would support single inheritance only. This first commit related to error inheritance implementation lets elog-gen.py figure out an error's parent. Change-Id: Ia5c44de755e777e0cb2725afa5988c97283d10f0 Signed-off-by: Deepak Kodihalli

elog-gen.py : read multiple error yaml files

2017-01-27T16:42:17+00:00

This change enables the elog-gen script to look at more than one error yaml file (and corresponding metadata yaml file). The input to the script had to be changed to a yaml directory, containing error yaml files, instead of a single error yaml file. The reason to support reading multiple error yaml files is that, without this, applications have to all dump their errors in a single big error yaml file. Now it's possible to write application/domain specific error yaml files; they just need to be exported to the same location, from where elog-gen.py can pick them. Change-Id: I9418bf0e0b54a7b7f7701b337649cb8eb4c54913 Signed-off-by: Deepak Kodihalli

Fix types in error-logging YAML to match openbmc standards

2017-01-21T08:13:59+00:00

Change-Id: If5e2e534740f0675ba9294905ae531e015aed85a Signed-off-by: Deepak Kodihalli

Rename .logging.yaml to .metadata.yaml

2017-01-21T08:13:59+00:00

This change is just for brevity. Change-Id: Ie2360b19179837a1dc3675e96a4adcc2114f2bc6 Signed-off-by: Deepak Kodihalli