Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

It has been observed that some bugs (particularly performance-related ones) can take a weeks to resolve, and can often not cannot be reproduced by the CPS dev team.

...

Performance Bugs

  • Available resources in the deployment (memory and CPUs)CPU cores, number of application instances)
  • What is the load on the system (how many concurrent operations, etc.)?
  • Measured CPU and memory consumption
  • For Out Of Memory Errors (OOMEs): Attached heap dumpWhat is the load on the system (how many concurrent operations, etc.)? - I think this should be a requirement moving forward

Acceptance Criteria for Bugs

...

  • All information in the Bug Reporting Template is provided, especially steps to reproduce
  • Bug reporter tests with the latest released version?
  • But what do we do when a bug is not reproducible by us?

Sharing artifacts such as Logs in the Open Source

Some bugs being reported often require sharing information such as logs, heap dumps, etc. This needs to be done in a way that IPR is protected, since CPS is developed in the open source.