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_check_gdb/master-arm in repository toolchain/ci/base-artifacts.
discards 350d5ed36b94 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/ [...] discards 38755fa998e4 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards 9ed005b92190 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/ [...] discards 2c3a538fcfab 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/ [...] discards 03b589d41044 239: force: #106: 1: [TCWG CI] Success after baseline buil [...] discards 9518d8a23819 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branch [...] discards da431698c4f5 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards 76abcc47ee9f 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: [...] discards de500de892c0 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] discards e971bec7af40 234: force: #94: 1: [TCWG CI] Success after baseline build [...] discards eea33ee66d72 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 61fcbdf6aa7b 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 136f2e8464f1 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards ee4d46dbcc0c 230: onsuccess: #78: 1: Success after gdb: 2 commits discards a45a30aaaeeb 229: force: #77: 1: Failure after gdb-13-branchpoint-1594- [...] discards cc275cb43f2b 228: force: #74: 1: Success after gdb: 53 commits discards 01508c3ee686 227: onsuccess: #72: 1: Success after binutils/gcc/linux/g [...] discards e75152999016 226: force: #70: 1: Success after baseline build: no new commits discards b510e12a88a2 225: force: #68: 1: Failure after gdb-13-branchpoint-1540- [...] discards 45a22d017d9d 224: force: #65: 1: Success after gdb: 50 commits discards 2d476e14701f 223: force: #63: 1: Failure after gdb-13-branchpoint-1489- [...] discards daf6b8713d89 222: force: #60: 1: Success after gdb: 16 commits discards 2b2c8dd88237 221: force: #53: 1: Success after gdb-13-branchpoint-1472- [...] discards abd558397f72 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02d [...] discards 3981fe51cdf9 219: force: #50: 1: Failure after linux: 2520 commits discards 6d70b2da0e58 218: force: #48: 1: Success after gdb-13-branchpoint-1471- [...] discards a52caa7c3241 217: force: #45: 1: Success after linux: 1 commits discards 3006a12c3ad2 216: force: #43: : Failure after baseline build: no new commits discards fbc4bd4f4d47 215: force: #41: 1: Failure after gdb-13-branchpoint-1470- [...] discards fcae2a9ae015 214: force: #39: 1: Failure after gdb-13-branchpoint-1470- [...] discards cb3bae422627 213: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 063369527227 212: force: #27: : Failure after baseline build: no new commits discards becb70efee1a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 9b2f3e3fa9e6 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 954f6b069f69 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 222c55d485ef 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 6aa4dc6134b7 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards bba4cca6678e 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 8a687712876f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 47f7c474794a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards db6d2a820956 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 4ca2699c7264 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards f26cc9c136e4 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 2a8382567de6 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards a52b1f83a8b6 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 55843e279c0d 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards a7f5f360b980 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards c93e09c78722 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards be7cb960e624 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 121254983239 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 8497efeb35e3 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 00657b41f59a 192: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards e53d24e12720 191: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards 952ed9b61986 190: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards 6954e11857fe 189: onsuccess: #683: 1: Success after binutils/gcc/linux/ [...] discards 7443df49793f 188: onsuccess: #682: 1: Success after binutils/gcc/linux/ [...] discards bfd9a604a192 187: onsuccess: #681: 1: Success after binutils/gcc/linux/ [...] discards 2d1ffd769322 186: onsuccess: #680: 1: Success after binutils/gcc/linux/ [...] discards a46d354c2c8d 185: onsuccess: #679: 1: Success after binutils/gcc/linux/ [...] discards 21c01828f2e8 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/ [...] discards 281230787283 183: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards fe7945ca1d1b 182: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards da80978fd126 181: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards 4ee9b625065f 180: onsuccess: #674: 1: Success after binutils/gcc/linux/ [...] discards 222efcae78c8 179: onsuccess: #673: 1: Success after binutils/gcc/linux/ [...] discards 9d2ea7567bc4 178: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] discards 8a0753e72dad 177: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 78dc5bdf80ac 176: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] discards 26c092270b89 175: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards e31b6c1ccb0f 174: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards e274e5aad057 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 1 [...] discards 984685fa6ea8 172: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards e3f7de7551e5 171: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards 05eff82d96b0 170: onsuccess: #664: 1: Success after binutils/gcc/linux/ [...] discards ee01939eb40a 169: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 9541a2a6df5d 168: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards 2ecacd9beaba 167: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards 13f1ec7fcca4 166: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards 76db1a0584df 165: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards 6cd269ea950f 164: onsuccess: #658: 1: Success after binutils/gcc/linux/ [...] discards 4a4ac52745c8 163: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] discards 88ee0cd76724 162: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] discards 2dfd4035d252 161: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] discards b4c6ee128c60 160: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] discards d52411e6b202 159: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards c99c50523e16 158: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards 21a41b9f7d4d 157: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards 0c0d6151473c 156: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards ed9f9431ff9b 155: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards 75174a8f5778 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/ [...] discards d7138f146639 153: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] discards 883109912c32 152: onsuccess: #645: 1: Success after binutils/gcc/linux/ [...] discards d6de9d536b1f 151: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards 1354f980f69e 150: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards 5c7d8aeba162 149: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards 0a3a53164307 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 [...] discards 54c5bc4ce803 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 1 [...] discards c9413e4c1ad1 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 3 [...] discards e944abbcaa94 145: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards 1c7ae3c65ca6 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 4 [...] discards 1a1a763979ca 143: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new bd519f092bd3 143: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new 274961d37030 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 4 [...] new 42155914f336 145: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new 542d133665ac 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 3 [...] new 42d8765c691c 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 1 [...] new 51bc044a5fd0 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 [...] new a268a39ad5aa 149: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new 5a60f0f84107 150: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new d1b1c3b235e3 151: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 7863cf6a194e 152: onsuccess: #645: 1: Success after binutils/gcc/linux/ [...] new 4249df71dd9f 153: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] new d9698e187236 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/ [...] new 9800a30f4796 155: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new 7e3955431e6c 156: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new 29be62aedda9 157: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new a91f214cbc03 158: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new ba2076680d5c 159: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new 62e1ba07bd87 160: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] new 5d3a5df7ecef 161: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] new 8abbc02b9b1c 162: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] new f55f6378c16c 163: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] new 22d3cf5e19eb 164: onsuccess: #658: 1: Success after binutils/gcc/linux/ [...] new 162e6517cf65 165: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new c4cf24f95900 166: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 1dfdbef461f4 167: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 5507e6ccc08c 168: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new af560d67f229 169: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new 8bfe9e80feee 170: onsuccess: #664: 1: Success after binutils/gcc/linux/ [...] new e13a25a9c880 171: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new cef133f60035 172: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new 461275205daf 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 1 [...] new 4d9ef834dc59 174: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new 68e053224b6f 175: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new 34ce3753d5b3 176: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] new 30ad9c7a7e71 177: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new d71e475098db 178: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] new e63a5dbd49a2 179: onsuccess: #673: 1: Success after binutils/gcc/linux/ [...] new 15781e7d58ac 180: onsuccess: #674: 1: Success after binutils/gcc/linux/ [...] new 9db9e0df66e6 181: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new 812eafc49ebc 182: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new 668759dece00 183: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new e02afea976cd 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/ [...] new be30815b286c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/ [...] new 42051900bab4 186: onsuccess: #680: 1: Success after binutils/gcc/linux/ [...] new 02df95a38d2f 187: onsuccess: #681: 1: Success after binutils/gcc/linux/ [...] new 9e92827bd459 188: onsuccess: #682: 1: Success after binutils/gcc/linux/ [...] new d06da3c08342 189: onsuccess: #683: 1: Success after binutils/gcc/linux/ [...] new cc88d05a0d1f 190: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new c5b119c17fe8 191: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new 037426fb6970 192: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new 6c36e57703cb 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 31ae7f8aa9ef 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 79db58946d1f 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new f49a4576d608 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 6513a1defdc9 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 19c7f140cf09 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 22bffd96f593 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 97badd14cdc6 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 0c728491b18d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 9c677bb65a9e 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 22c7ca9216b0 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new ef64397843c4 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new d2100157d89c 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new df18a028ae1e 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 7353f7a84107 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new a8504ab2b503 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new fbef1b541239 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 05519a745286 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 7ba3fa0046b1 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new c6ffea83ac26 212: force: #27: : Failure after baseline build: no new commits new 1f8def180388 213: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 83bd853c44c0 214: force: #39: 1: Failure after gdb-13-branchpoint-1470- [...] new 0b9116544c90 215: force: #41: 1: Failure after gdb-13-branchpoint-1470- [...] new 9517e20a8ad4 216: force: #43: : Failure after baseline build: no new commits new 7b3d2c18bb57 217: force: #45: 1: Success after linux: 1 commits new b0dbd3a7dc2e 218: force: #48: 1: Success after gdb-13-branchpoint-1471- [...] new 9506a69f49e6 219: force: #50: 1: Failure after linux: 2520 commits new cd544bc4485a 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02d [...] new 4b15d49e2f57 221: force: #53: 1: Success after gdb-13-branchpoint-1472- [...] new 81ce15cf084f 222: force: #60: 1: Success after gdb: 16 commits new 41baf6724fa2 223: force: #63: 1: Failure after gdb-13-branchpoint-1489- [...] new 2200c731ebf5 224: force: #65: 1: Success after gdb: 50 commits new 91c6d8773159 225: force: #68: 1: Failure after gdb-13-branchpoint-1540- [...] new 1487a753aef4 226: force: #70: 1: Success after baseline build: no new commits new a6001df7b7ee 227: onsuccess: #72: 1: Success after binutils/gcc/linux/g [...] new 1173b6fa627c 228: force: #74: 1: Success after gdb: 53 commits new 8488dfd83749 229: force: #77: 1: Failure after gdb-13-branchpoint-1594- [...] new 2bf6df6edbc1 230: onsuccess: #78: 1: Success after gdb: 2 commits new 0f1808846f0f 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new e52a71d05085 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 5e74b2c481cf 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 62ab113dbbac 234: force: #94: 1: [TCWG CI] Success after baseline build [...] new dc3610d9e4da 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] new 559dc3228018 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: [...] new 3e8e288bbdb7 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new 3f3c9052024e 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branch [...] new 9b315297d5a8 239: force: #106: 1: [TCWG CI] Success after baseline buil [...] new 07d223643005 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/ [...] new e9d1250c8ff7 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/ [...] new 21bbc7b9e2e4 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new cbd971978fcd 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/ [...] new 9b46f50d987e 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/ [...]
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 (350d5ed36b94) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...]
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 2044 -> 2092 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 49332 -> 49864 bytes 04-build_abe-gcc/console.log.xz | Bin 234752 -> 236932 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8188 -> 8744 bytes 07-build_abe-glibc/console.log.xz | Bin 232424 -> 232408 bytes 08-build_abe-gdb/console.log.xz | Bin 47016 -> 48380 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3760 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4156 -> 5560 bytes 11-check_regression/console.log.xz | Bin 6168 -> 6712 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 226 +++++++---- 12-update_baseline/console.log | 48 +-- 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 | 57 ++- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 34 +- manifest.sh | 38 +- sumfiles/gdb.log.0.xz | Bin 2929368 -> 2933292 bytes sumfiles/gdb.log.1.xz | Bin 138736 -> 144600 bytes sumfiles/gdb.log.2.xz | Bin 16476 -> 21388 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 19812 bytes sumfiles/gdb.log.4.xz | Bin 0 -> 6360 bytes sumfiles/gdb.sum | 179 ++++---- sumfiles/gdb.sum.0 | 388 +++++++++--------- sumfiles/gdb.sum.1 | 745 ++++++++++++++++++++++++++++------ sumfiles/gdb.sum.2 | 330 ++++++++++++++- sumfiles/{gdb.sum.2 => gdb.sum.3} | 333 +++++++++++++-- sumfiles/gdb.sum.4 | 187 +++++++++ 35 files changed, 1945 insertions(+), 638 deletions(-) create mode 100644 sumfiles/gdb.log.3.xz create mode 100644 sumfiles/gdb.log.4.xz copy sumfiles/{gdb.sum.2 => gdb.sum.3} (86%) create mode 100644 sumfiles/gdb.sum.4