Handle message and exitflag in histories

[dweindl]

• Add properties message and exitflag to HistoryBase
• Implement them in derived classes where missing
• Store them in CountHistoryBase

Resolves #1191

[codecov-commenter]

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (6935cee) 84.02% compared to head (81f0d1e) 82.70%.

Files	Patch %	Lines
pypesto/history/base.py	91.30%	2 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1203      +/-   ##
===========================================
- Coverage    84.02%   82.70%   -1.33%     
===========================================
  Files          148      148              
  Lines        11752    11775      +23     
===========================================
- Hits          9875     9738     -137     
- Misses        1877     2037     +160     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[m-philipps]

Should exit flag and message also be listed as possible entries here?

pyPESTO/pypesto/history/base.py

Lines 38 to 39 in b1b17c6

	# all possible history entries
	ALL_KEYS = (X, *RESULT_KEYS, TIME)

[dweindl]

Should exit flag and message also be listed as possible entries here?

No, those are only the fields we want to save on every iteration / function evaluation.