Because of this, the argument `created_before` in the `get_new_bugs()`
method was always set to the date when it was called for the first time.
After a while, users would not get the exepcted results, since most new
bugs would have been created after this date, and would be ignored by
autosummary.
fix: make sure to send lists to Jinja template for reports and hardware
hardware, full_test_reports and stress_test_reports are obtained using
the get() method on an HTML form, so by default they return an empty
string.
When generating the summary report, send lists instead of potentially
empty strings in order to prevent concatenating str and list in the
Jinja templates.
Perform additional stripping to make sure we ignore lines with spaces
only and to remove un-necessary spaces on non-empty lines.
autosummary: Send status result to the Auto Test Status Tracker webapp
Once the summary is generated, there is now a button at the bottom of
the summary page to send the data over to the Auto Test Status Tracker
webapp. If everything goes fine, the page is refreshed with a link to go
check the status record.
autosummary: New page to manually input image name if release e-mail not found
Auto-Summary looks for a mail.content file in the project milestone's
oem-share directory. If found, it uses it to extract image name and
sha256 sum.
Thanks to this commit, if mail.content is not found, a new page is shown
to the user to let him/her manually input an image name. Auto-summary
then goes to check if there is an appropriate sha256sum file for it, and
generates the report if all is good.
Note: mail.content should *always* be there, but we encountered cases
where it was not, ergo this commit.
