| [platform-releng-dev] 4.2 Build. I-Build I20120417-0800 Autotagging failed to merge, build halted. |
At least ... that's what the email subject would look like once I get that automated :)
But, the build scheduled for 8:00 this morning failed with the message below.
It used to be such builds would continue merrily along, but it was requested that such builds should fail fast, since
it would be "known" at that point to be incorrect. (See bug 366279)
So, someone might have been "integrating" their changes between 8:00 and 8:07 and the build failed like it is (now) supposed to ... or, maybe, it might be the "cached" version of the repo is not in such great shape since I've been doing many test builds.
So, I am going to schedule another I-build for 10 AM, and in the meantime I will "clean out" the cached version of the repos we use during auto-tagging.
Thanks,
= = = = = =
git commit
[R4_HEAD e12395a] Releng build auto tagging for I20120417-0800
4 files changed, 11 insertions(+), 11 deletions(-)
git tag I20120417-0800
Updated tag 'I20120417-0800' (was 0000000)
git push
To file:///gitroot/platform/eclipse.platform.releng.maps.git
5fa4c79..e12395a R4_HEAD -> R4_HEAD
! [rejected] master -> master (non-fast-forward)
error: failed to push some refs to 'file:///gitroot/platform/eclipse.platform.releng.maps.git'
To prevent you from losing history, non-fast-forward updates were rejected
Merge the remote changes (e.g. 'git pull') before pushing again. See the
'Note about fast-forwards' section of 'git push --help' for details.
ERROR. exit code: 1 Could not push to repository
[end] [08:07:46] tagRepo
Unexpected auto-tagging return code: 1. Build halted.