This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts.
discards f64c901f4c3 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] discards cfd62d8c456 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards 28878b87fd0 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 9d960cea1bb 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 8464d592922 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] discards b1393e358df 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards 363a035607d 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 8276ab3d7f9 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 2d1fd746d13 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 7cd17810b98 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards ac0a62f3723 121: force: #26: : Failure after baseline build: no new commits discards bdeacf83496 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 07eaba07a61 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 44cb068010d 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 73583a00bd6 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards ac88dc028a3 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 67907a82a4d 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards a2eb30f504f 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 3e0f808ce68 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards ac65c509fcb 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 469233c8d93 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 335255acbb9 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 2e63262bb9e 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 4fbe4186c07 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards d35299b8155 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards f7d70113383 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 955fe62214f 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 9bc65a9e2b3 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards a5257db7559 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 4d8b53c6aa9 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 6fc3a2c3cc5 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards c3a7e8e72c0 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 157647e71e3 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 457dccf59e1 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 1e5f6f920a7 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards 57cf6c5c512 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 915b3da164c 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards f9484783012 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 0e0c69ef1e0 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards b8c1c43e9f9 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards ae001d0f266 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards c63caa13d4d 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 34d6f3b1365 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 3bc324dfdaf 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards df1d79cd74f 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 942acd838fc 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 98c2fd58bcb 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 29de1b0d680 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 85a0cb0bc5f 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 2f19d5eef8d 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 753a0a22aa9 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 3dd53f0ae5c 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 316039bfb2c 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 766006296cb 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 63f504de5b6 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 98315b1f4e7 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards e192ee60281 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 2985bc11459 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards b39f21eb0f0 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 5f4bd08221e 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 6f852a1e2de 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 84a553107fe 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards a86c6dee708 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards c5d8712bbda 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 125d55919de 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 30355328e44 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 72c283d4bf5 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards a75808e067b 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 475e053f47a 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 06339428b13 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards effd588c80e 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 1950dc22a18 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 3e7c7f08623 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 7c04df0347a 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 87ed52aa4f2 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 7991d914d45 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 9a3294bec35 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards e3bd3de71da 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards fe122f93653 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards dc47058663e 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards e2167028ea9 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards a586b6a7c1b 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards d03c3a3d64d 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 4978299584b 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 08ec21b8cdf 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 46304be2a48 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards bb122ffe110 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 43c6cc68b74 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards b1f864c0939 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 2b7e9102ff2 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 661decd8c74 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 3302a9b1ca9 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards c096e5f04a5 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 8e0c12a4f9d 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards c377413b353 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 5a1374b2455 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 9b2d4ae25d2 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 055c7bdcf2c 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards f9d9d7544d5 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 0b43e433e02 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 82818de69cf 31: onsuccess: #38: 1: Success after linux: 14 commits new 2a194d71f7e 31: onsuccess: #38: 1: Success after linux: 14 commits new 4557969e428 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 000d7744215 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 0be3f40934c 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new a56fbe99fe2 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 4d2209743a6 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 6da430bfb14 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new dc1d2198c45 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new 6c876c22726 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new c1533967497 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 4d3e8d7a465 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 3cbe5651e6c 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 736ae1ac3b2 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 1daf02b0283 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new ed2f02077ed 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 66f5baf9cf4 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 32eaa1a8f97 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new d481ee693a0 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 2adcf1aae5b 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new aebc850dcbb 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new cba3bc99683 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 4d656707a1f 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new ef200bc8674 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 2a6a2f867db 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new b7cbacd1337 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 56cd0ef8c9e 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 6c1f697b9e4 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 482699c01b2 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 5dc12dec343 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new cf847c607c2 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new e5a42b6d222 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 7e49461c8a9 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new b3bdc959c26 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 1790ca4ab0d 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new b0d7ee78d5b 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new c8feaf4f0e1 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 52c46fc2703 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new d0c8d0706ec 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 0dfd91cb703 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 3feab57ff72 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new a5c7d9b27cb 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 4a56f3d56f3 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 11d47a7204f 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 7576fe06766 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 9cc2dcae95d 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 1051553765d 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 9a0dbed0743 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 8b8dad2a0a7 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new edab1b6c8ff 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new a289d7cda78 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new cd5121eb18c 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 07e5b69e041 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 32b74b9e1ba 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new f0664068560 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new fdb0406a8c7 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new ae0386f12c0 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 9ad2d6f1040 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 0ea294c1a2b 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 20f79b58769 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 138fb685876 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 1bb55a2c005 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new ec030133642 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 0f90e2c3fa5 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 628fe377b6a 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new fe7d946b57c 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new bd9e8bde1e0 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 4e0b2efee08 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 138b43f2819 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 83d3f93acdb 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new d3e0fc5685e 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 3a806223ace 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 55e56a0da6a 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new c9fc24029fe 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 6b8a8afb73c 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 435fe00b7d6 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 8510a3e9e9c 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new abf68736a3e 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new d57260d82b6 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new c4977297949 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 1fc63313c12 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new ac272ba2ae3 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 8ac4498208b 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new a23868e02a6 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 8de90255302 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 5c0683dd03b 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 9bcc97ef33e 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 310b70174f9 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 4401ef10513 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 8abcb736db6 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new ec7935eb063 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new dd7691ca033 121: force: #26: : Failure after baseline build: no new commits new 8c4cb6b75c3 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 464deac6488 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 1438c79c199 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new ec3327554c5 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new baf3c4bebee 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new 1f01bafb196 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] new 2a2b7d12ce5 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new b264ffc1ac6 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new e8b48c8bd7f 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new 47766b00e8c 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] new 4b2f18a351c 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...]
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (f64c901f4c3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...]
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2040 -> 2260 bytes 02-prepare_abe/console.log.xz | Bin 2576 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 49244 -> 50148 bytes 04-build_abe-gcc/console.log.xz | Bin 235312 -> 237464 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9064 -> 8784 bytes 07-build_abe-glibc/console.log.xz | Bin 232684 -> 232348 bytes 08-build_abe-gdb/console.log.xz | Bin 47160 -> 46788 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3072 -> 3108 bytes 11-check_regression/console.log.xz | Bin 4452 -> 5132 bytes 11-check_regression/mail-body.txt | 35 ----------------------------- 11-check_regression/mail-subject.txt | 1 - 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 40 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 32 +++++++++++++++++++++++++++ mail/changes-list-short.txt | 1 + mail/mail-body.txt | 35 ----------------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 38 ++++++++++++++++---------------- sumfiles/gdb.log.xz | Bin 14456 -> 14452 bytes sumfiles/gdb.sum | 4 ++-- 30 files changed, 86 insertions(+), 124 deletions(-) delete mode 100644 11-check_regression/mail-body.txt delete mode 100644 11-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt