I wouldn't worry about the Jenkins failures for your change - in fact, it *is*
welcoming to see Windows validation failing again. I looked at the log and the
issue is caused by the recent regression in shut down sequence, which Dan just
merged: Change subject: [IOT-2110] Modify CATerminateMessag
Thanks for investigating this CJ. From what I'm hearing, there are 2 issues:
1. run.bat does not exit with a non-zero code on failure.
2. bogus command used for i386 and amd64 variants.
Looking at https://gerrit.iotivity.org/gerrit/#/c/19301, it seems problem #2 is
fixed?
So the next step is
Trevor, I've filed bug IOT-2119 on you to look into this. It is a critical
issue for the check-in gate to be giving a +1 verification without actually
testing anything. Multiple folks here at Microsoft are blocked because of a
recent Windows regression escaping from Jenkins (see
https://build.i
My understanding is these Jenkins failure due to inability to delete files (on
Windows) are caused by hung/deadlocked tests. CJ and Dan recently fixed the
issues with these:
https://gerrit.iotivity.org/gerrit/#/c/18713
https://gerrit.iotivity.org/gerrit/#/c/18821
Thanks,
Way
From: iotivity-dev
My understanding is these Jenkins failure due to inability to delete files (on
Windows) are caused by hung/deadlocked tests. CJ and Dan recently fixed the
issues with these:
https://gerrit.iotivity.org/gerrit/#/c/18713
https://gerrit.iotivity.org/gerrit/#/c/18821
Thanks,
Way
From: iotivity-dev
