| Summary: |
Number of reported warnings does not match number in MySQL database |
| Product: |
[Build System, Metadata & Runtime] Toaster
|
Reporter: |
Magnus D <magnustoaster> |
| Component: |
toaster | Assignee: |
Alexandru Damian <alexandru.damian> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium
|
CC: |
alexandru.damian, belen.barros.pena, cristiana.voicu
|
| Version: |
unspecified | |
|
| Target Milestone: |
1.8 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
Don't know
|
|---|
| Attachments: |
|
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".