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 edaa8b75e4 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] discards 725c3e8c28 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] discards b67b339c59 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits discards 2aa721726f 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits discards 92eb1a9168 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] discards 889e539d14 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] discards b288860fc8 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards 700885b85d 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] discards 6d5449411e 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] discards b4f26b4d3a 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] discards 4dac8e5131 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 2bec845529 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards ea2b75f203 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] discards 1d9932e413 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 2fc4f67c5f 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 8818e38ab0 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 4764bb39e7 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards db48144fa6 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 2486c29675 230: onsuccess: #78: 1: Success after gdb: 2 commits discards f897c5c908 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] discards 741c5a5268 228: force: #74: 1: Success after gdb: 53 commits discards 3848a80fba 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards cb1e71d79d 226: force: #70: 1: Success after baseline build: no new commits discards d655e6c542 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] discards c3595938fb 224: force: #65: 1: Success after gdb: 50 commits discards 164122638a 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] discards 2014a06edb 222: force: #60: 1: Success after gdb: 16 commits discards a2c5153c08 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] discards 8ba145e9d0 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] discards 1d62bc76c4 219: force: #50: 1: Failure after linux: 2520 commits discards c43774ba79 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] discards d264a47c63 217: force: #45: 1: Success after linux: 1 commits discards 7e5d1fbc88 216: force: #43: : Failure after baseline build: no new commits discards c0da44fca9 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 024a4ff1aa 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 5f610a16aa 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 3aaeb9b469 212: force: #27: : Failure after baseline build: no new commits discards a075119393 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 783528691b 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards e2111c4b30 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 758579221d 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards de4425d059 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards e87f674d81 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 70fcd7668c 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 76d9c00896 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 8ab0b07d11 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 69382f7e3a 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards c56edb3720 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 98b4930aab 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 3adbbc3802 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 5e775c22cd 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards ee31de14ef 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 769f2125af 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 8ccf5b440b 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 2ac224b200 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards b839d43a89 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards c8f801fbb9 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 7c136d85c7 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards b7ddb30bfd 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 76e32b860b 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards 12a0810c31 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 286a79798d 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards ba20bdff08 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards 4f8d35fb68 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards 05763bb91a 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards dd83ac7c8b 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 2b40fad921 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards cf8034c7a1 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards dca7c11189 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards cfffa9ee7d 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards 76386ed0aa 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 011116a67e 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 63bc1ab9f5 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 39f3ed432c 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 001c9eca52 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards e423c95654 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards ebab52f0bc 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 1eed47244b 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 2b7dae140e 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 6a8f17b8ab 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 2c53995bad 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards c2c69bf78e 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 82a9b2f404 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards a009c10dfe 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 4f1013194d 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards bba456f77a 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards a9dfe8b46d 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards b8ec53afbe 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards d0a49094dc 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards f872ffc340 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 2493da8100 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 111ada5052 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 057d5897c1 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 82fc0911b8 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 67847a9ceb 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards eb459359aa 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 5408f78dd9 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 76b8fe71eb 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 01a3af9c13 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 42b5513183 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards cbae104886 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 2139785f76 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 791b089286 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new d85ab214cc 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 3b83d33c98 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 494dbdd41c 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new bdc23eeef5 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 09c2f2f6b4 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 4ce43258e4 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 72c2a1d107 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new c85394b4e0 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 7dd545c23d 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 7ad92a3594 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 2db2637325 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 0ec3376c89 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new cff90a9554 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 86a02ba90c 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new f4410f63f2 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new eee9bbda57 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new f81530bfce 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new d698ca966e 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new f42baa72c4 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 9c9b03d5d0 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 13497b89d9 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 6566788487 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 34378c2505 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new 525eec3324 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new c7080924a1 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 27ac9be6b2 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 63529fbe3e 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 934e18aee9 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 47d65778b4 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 092daea87e 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new a460daa02e 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new 211f7d1e96 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new b8addf637d 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new abe4f65506 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new 6e1cc5901f 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new f1980fe6c7 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new 8870637797 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new 31440d1224 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new a3f6c273ed 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new 4b98f1e51e 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new 2c0d85d201 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 2d590f6cc0 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new b40a1035bd 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new ffff14aa3c 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 7eb197f192 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 4847719631 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 991f75bdc7 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new b5a6662a46 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 169b0ffb7f 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 2bae78b622 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new fe1a2d5220 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 40003c8931 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 7ef8ddf5b7 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new b508a48f02 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 175b0e4e85 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 355c954d4d 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 64951540d7 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new c25fdbf26e 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 72c442880f 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 330961a6d1 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new d831ff38d7 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 2c1215e932 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 4f7baf0881 212: force: #27: : Failure after baseline build: no new commits new 1e7d14158d 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 028337f9b5 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 726b7c0720 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 78041155b4 216: force: #43: : Failure after baseline build: no new commits new 74c8f928c0 217: force: #45: 1: Success after linux: 1 commits new 66db28c01c 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] new 4f9a7bcf5a 219: force: #50: 1: Failure after linux: 2520 commits new a2cbd13d42 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] new cd156f8745 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] new cc1ac53ccb 222: force: #60: 1: Success after gdb: 16 commits new e60ef3a88a 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] new 7f2e7fb010 224: force: #65: 1: Success after gdb: 50 commits new 6a3ac4c40e 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] new 86f51b10e2 226: force: #70: 1: Success after baseline build: no new commits new 48d5b66df7 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 4352bb2606 228: force: #74: 1: Success after gdb: 53 commits new 44f3a02647 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] new 8f4464c532 230: onsuccess: #78: 1: Success after gdb: 2 commits new 044268d167 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new 87953c628c 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 210d31bfad 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 4dbd340226 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new c1438c3c85 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new aa3b45d187 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] new 38e1aab9d7 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new d132bc10e5 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 1f0dd1d915 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] new f839e6f75e 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] new 12f210c2fd 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] new dc329d7cd9 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new 8c6e49c5eb 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] new 2bc28e40c5 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] new 5b4d855562 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits new bd6dc1db99 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits new 94506b81e8 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] new 719fe93e67 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] new 87d188c391 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits
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 (edaa8b75e4) \ 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 2028 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 49288 -> 49088 bytes 04-build_abe-gcc/console.log.xz | Bin 235672 -> 236404 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9492 -> 9696 bytes 07-build_abe-glibc/console.log.xz | Bin 232444 -> 232280 bytes 08-build_abe-gdb/console.log.xz | Bin 47016 -> 47824 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3808 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4524 -> 4720 bytes 11-check_regression/console.log.xz | Bin 5960 -> 9704 bytes 11-check_regression/results.compare | 24 +- 11-check_regression/results.compare2 | 1126 +++++++++++++++++++--- 12-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 38 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 35 +- manifest.sh | 28 +- sumfiles/gdb.log.0.xz | Bin 2897708 -> 2937920 bytes sumfiles/gdb.log.1.xz | Bin 144012 -> 143364 bytes sumfiles/gdb.log.2.xz | Bin 15484 -> 16716 bytes sumfiles/gdb.log.3.xz | Bin 10040 -> 15144 bytes sumfiles/gdb.log.4.xz | Bin 0 -> 10324 bytes sumfiles/gdb.log.5.xz | Bin 0 -> 10104 bytes sumfiles/gdb.log.6.xz | Bin 0 -> 10120 bytes sumfiles/gdb.sum | 1668 +++++++++++++------------------- sumfiles/gdb.sum.0 | 1678 +++++++++++++-------------------- sumfiles/gdb.sum.1 | 846 ++++++++++------- sumfiles/gdb.sum.2 | 405 ++++---- sumfiles/gdb.sum.3 | 247 ++++- sumfiles/{gdb.sum.3 => gdb.sum.4} | 33 +- sumfiles/{gdb.sum.3 => gdb.sum.5} | 28 +- sumfiles/{gdb.sum.3 => gdb.sum.6} | 26 +- 35 files changed, 3404 insertions(+), 2850 deletions(-) create mode 100644 sumfiles/gdb.log.4.xz create mode 100644 sumfiles/gdb.log.5.xz create mode 100644 sumfiles/gdb.log.6.xz copy sumfiles/{gdb.sum.3 => gdb.sum.4} (99%) copy sumfiles/{gdb.sum.3 => gdb.sum.5} (99%) copy sumfiles/{gdb.sum.3 => gdb.sum.6} (99%)