A build can throw 2 types of warnings: * Task warnings (associated to a task) * Build warnings (not associated to a task) Right now, we collect all warnings and show them all together in the build dashboard, but we don't link task warnings to the task to which they are associated. We should provide that link between warnings and tasks when applicable.
*** Bug 5847 has been marked as a duplicate of this bug. ***
field added.
(In reply to comment #0) > A build can throw 2 types of warnings: > > * Task warnings (associated to a task) > * Build warnings (not associated to a task) > > Right now, we collect all warnings and show them all together in the build > dashboard, but we don't link task warnings to the task to which they are > associated. We should provide that link between warnings and tasks when > applicable. I meant errors and warnings when I wrote this. For some reason, my description only talks about warnings.
Created attachment 1787 [details] Linking orm_logmessage entries to tasks
Database schema change merged into origin/master.
Ugh, I moved this to 1.7 by mistake, but the fact is that showing the stack trace in the failed task details page depends on us fixing this bug, so chancing it and moving back to 1.6
After investigation, I could not find a reliable link between generated warning messages and the task that generated them After consulting from Belen and Paul, we decided to not implement this feature.