Bug 7021 - Number of reported warnings does not match number in MySQL database
Summary: Number of reported warnings does not match number in MySQL database
Status: RESOLVED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.8
Assignee: Alexandru Damian
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-12-03 11:59 UTC by Magnus D
Modified: 2015-01-23 17:45 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
toaster_ui.log (2.98 KB, application/octet-stream)
2014-12-03 11:59 UTC, Magnus D 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Magnus D 2014-12-03 11:59:00 UTC 
Created attachment 2274 [details]
toaster_ui.log

For some builds, the number of Warnings displayed on the first page does not match the number of warning messages displayed when clicking that number.

When looking into the database, we found for example that for a build, in the table orm_build we have the number of warnings set to 1, which is 
correct, but there is no entry in the table orm_logmessage for this build. Interestingly, in the toaster log file (see attached) the text that 
should be saved for the warning appears after the text Unsaved log.


We are running Toaster, setup as a production instance, using a MySQL database as backend. Toaster is used from the toaster/master branch taken from poky-contrib, last commit hash "52d4df8a548a4d9c32198095d610d303c57839ec".
Comment 1 Alexandru Damian 2015-01-19 16:41:08 UTC 
Prepared for upstream review.
Comment 2 Alexandru Damian 2015-01-23 17:45:51 UTC 
merged into master