|Anonymous | Login||2019-10-17 21:18 MSK|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0030688||Open CASCADE||[OCCT] TOOLS:Jenkins Certification Tool||public||2019-05-02 10:08||2019-05-02 10:13|
|Target Version||[OCCT] 7.4.0||Fixed in Version|
|Summary||0030688: Jenkins - warnings monitoring reports old testing results on restart|
|Description||After (real) fixing of all compiler warnings, Jenkins still sends warnings monitoring report to developer with old warnings.|
It seems that report is even sent BEFORE actual compilation jobs are actually finished - e.g. I see all jobs finished for macOS/Linux, while Windows jobs are not finished yet.
This behavior has been observed several times on various branches (the last one is CR30687_1-CR30687_1-KGV, in case if Jenkins logs can be helpful).
|Steps To Reproduce||- Create a branch generating compiler warnings (in OCC Products for example)|
- Start Jenkins testing
- Wait testing completion and receive warning monitoring report.
- Push update fixing compiler warnings.
- Start Jenkins testing (only compilation, for example) within the same workspace.
Result: warnings monitoring report is still sent.
|Tags||No tags attached.|
|Test case number|
|2019-05-02 10:08||kgv||New Issue|
|2019-05-02 10:08||kgv||Assigned To||=> bugmaster|
|2019-05-02 10:12||kgv||Description Updated||View Revisions|
|2019-05-02 10:12||kgv||Steps to Reproduce Updated||View Revisions|
|Copyright © 2000 - 2019 MantisBT Team|