Bug 436054 - Log analysis (e.g. comparator errors) is not performed if build fails
Summary: Log analysis (e.g. comparator errors) is not performed if build fails
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.4   Edit
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 434596
  Show dependency tree
 
Reported: 2014-05-28 09:14 EDT by David Williams CLA
Modified: 2020-08-24 08:26 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2014-05-28 09:14:54 EDT
This is significant, since a build can fail because a feature needs to be "touched" ... it'd be much easier to see that -- and see concrete "contribution" to the problem, if the "comparator warnings" were analyzed even if build fails.
Comment 1 David Williams CLA 2014-05-28 22:08:27 EDT
For additional "justification", see bug 436039, and bug 416619. That is "feature qualifiers" are a particularly error prone area, often dependent on "commit time" ... not necessarily "push time", which means the more frequently I-builds are done, the more frequently a feature will miss an increment. 

See also 
http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg01213.html
where the order of making commits (and cherry-picks) can cause failure or success.
Comment 2 David Williams CLA 2014-05-28 22:12:58 EDT
To combine "comparator log" feature improvements ... 

Another improvement would be, in addition to a "releng test" is to send a link to "comparator log" along with the "build done" email message to platform-releng-dev list (similar to how we do "POM updates required"). That is, send if if it has "content" ... the reason being is that if comparator is quickly deemed to be bad enough, it might justify canceling the tests and doing a quick rebuild (after manual intervention of 'touching' bundle or feature).
Comment 3 David Williams CLA 2016-08-11 15:27:08 EDT
Doing a mass "reset to default assignee" of 52 bugs to help make clear it will (very likely) not be me working on things I had previously planned to work on. I hope this will help prevent the bugs from "getting lost" in other people's queries. Feel free to "take" a bug if appropriate.
Comment 4 Eclipse Genie CLA 2020-08-24 08:26:21 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.