summaryrefslogtreecommitdiffstats
path: root/tools/example
Commit message (Collapse)AuthorAgeFilesLines
* test: add callout-testDeepak Kodihalli2017-03-154-0/+20
| | | | | | | | 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 <dkodihal@in.ibm.com>
* metadata: introduce 'process' keywordDeepak Kodihalli2017-03-151-0/+1
| | | | | | | | | | | | | | | 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 <dkodihal@in.ibm.com>
* Error log inject toolMichael Tritz2017-03-152-0/+9
| | | | | | | | | 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 <mtritz@us.ibm.com>
* Include namespaces in the phosphor-logging exception nameAdriana Kobylak2017-03-023-3/+3
| | | | | | | | | | | | | | | | | 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 <anoo@us.ibm.com>
* Move inherits keyword from errors.yaml to metadata.yamlAdriana Kobylak2017-02-206-6/+6
| | | | | | | | 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 <anoo@us.ibm.com>
* elog-gen.py : order inherited errorsDeepak Kodihalli2017-01-274-1/+12
| | | | | | | | | 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 <dkodihal@in.ibm.com>
* elog-gen.py : get inherited-from errorDeepak Kodihalli2017-01-271-0/+2
| | | | | | | | | | | | 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 <dkodihal@in.ibm.com>
* elog-gen.py : read multiple error yaml filesDeepak Kodihalli2017-01-272-0/+7
| | | | | | | | | | | | | | | | 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 <dkodihal@in.ibm.com>
* Fix types in error-logging YAML to match openbmc standardsDeepak Kodihalli2017-01-211-6/+6
| | | | | Change-Id: If5e2e534740f0675ba9294905ae531e015aed85a Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
* Rename <Interface>.logging.yaml to <Interface>.metadata.yamlDeepak Kodihalli2017-01-211-0/+0
| | | | | | | This change is just for brevity. Change-Id: Ie2360b19179837a1dc3675e96a4adcc2114f2bc6 Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
* Break elog yaml files into two piecesAndrew Geissler2016-11-232-16/+19
| | | | | | | | | This is the final piece to supporting the phosphor-dbus-interfaces design where the errors are defined in one yaml file and their corresponding meta data is defined within another file. Change-Id: Idd2e18c1fd82fccb1298a2570a484deb382954f8 Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
* Base error log namespaces on yaml file pathAndrew Geissler2016-11-231-4/+4
| | | | | | | | | This is another step in the direction of getting us to support the error yaml file as it will be defined in the phosphor-dbus-interfaces repo. Change-Id: Ib437bea920f511bdbf541c3e2653bbf35a83fe92 Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
* Move the phosphor logging example yaml into sub directoryAndrew Geissler2016-11-221-0/+21
The real yaml will be defined in the phosphor-dbus-interfaces repo. This one will be an example one and used for testing. Future commits will refactor it to separate the error def from the meta data. Change-Id: Id05f935cbc24fb030e2ba378423ef3261bf5f7fb Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
OpenPOWER on IntegriCloud