dheeraj12347 commented on issue #12887: URL: https://github.com/apache/cloudstack/issues/12887#issuecomment-5225522600
> > [@daviftorres](https://github.com/daviftorres) any chance to tst/review the PR? it’s getting orphaned a bit. > > Hey [@DaanHoogland](https://github.com/DaanHoogland), I could use some guidance on how to compile and run CloudStack with the changes that [@dheeraj12347](https://github.com/dheeraj12347) introduced in [#12967](https://github.com/apache/cloudstack/pull/12967). > > I'm also wondering how I can intentionally trigger a few errors so I can see how they appear in the error logs now that they include timestamps. Hi @daviftorres , sure. For a quick build from the PR branch, you can use: ```bash mvn -pl server -am -DskipTests compile ``` That should be enough to verify that the Management Server side compiles. For actually checking the `.err` output, you’ll need a running CloudStack environment with the changes from #12967 applied. The main thing to verify is that an ERROR-level message written to stderr appears in the corresponding `.err` file with a timestamp, similar to the format already used in the `.log` files. The PR also adds the same handling for the Usage server. For triggering an error, I don't want to suggest a specific operation without knowing which CloudStack setup you're using, since the easiest way to reproduce an ERROR depends on the environment/configuration. If you let me know whether you're testing with a local development setup, simulator, or an existing CloudStack installation, I can suggest a more specific way to test it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
