Hi ben
Is something stuck with integration by the CI monkey.
Sometimes yes. Sometimes tests randomly failed on windows or something
like that :)
I thought this automatically picked and integrated any Fix To Include status
slices.
But these two cases were marked Fix To include a fews days ago, and
have not yet been integrated.
No we (either esteban marcus and me look at the code) at least I try to
browse the code,
and click on a button.
Case 17296 --> Fix To Include 2016-01-21 22:29
Case 17435 --> Fix To Include 2016-01-22 16:34
Fix to include are marked when we do not want that the monkey recheck
them to avoid that
they get unttaged for integration.
When I do an integration session like today for example. I tend to go
slowly and proceed with the
domain I can understand.
So now I will do
Case 17296
But I see several cases integrated since then didn't pass through Fix
To Include, so I'm curious what the process is. Is it still a manual
pick of items to integrate?
Fix to include is just a marker to avoid endless verification of an issue.
Now this is not because a fix is reviewed by the monkey that he should
be automatically integrated.
In addition we pay attention to some fast paths when people need it.
Do I answer your questions?
Stef
In that case why are the above passed
over? There is no indication on the tracker.
Case 17429 --> Fix To include 2016-01-22 16:52
--> Integrated 2016-01-22 21:05 Build 50539
Case 17446 --> Fix To Include 2016-01-22 21:40
--> Integrated 2016-01-22 23:40 Build 50540
Case 17404 --> Fix Reviewed By Monkey 2016-01-24 03:42
Case 17443 --> Fix Reviewed By Monkey 2016-01-24 04:57
Case 17457 --> Fix Reviewed By Monkey 2016-01-24 05:03
--> Integrated 2016-01-24 17:55 Build 50541
Case 17450 --> Fix Review Needed 2016-01-24 19:37
--> Integrated 2016-01-24 17:37 Build 50542
Case 17301 --> Fix Reviewed by the Monkey 2016-01-24 20:39
Case 17384 --> Fix To Include 2016-01-24 16:50
--> Integrated 2016-01-24 20:39
