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-aarch64 in repository toolchain/ci/base-artifacts.

discards edaf87914a 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards 1efeea2721 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards 072dc0351d 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards cc8e9f9c00 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards d5537f624c 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards 0c14ca764d 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards b8f735f298 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards a1daf9b002 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 6a5dd8c7ed 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 6a719e84a4 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 61973bd801 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 1592d033ab 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 3b7fd5ae7b 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards 863f8ba43d 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 8e3c23491a 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards ecfdb26654 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 0dcf8360a3 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 06f8b8f85e 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards c3a1cd0714 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 5099ee1435 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards a3208ceb9a 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards 1813fe4cfc 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 89b09fe864 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 0ae840e640 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards cdefe98284 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards e806de22ac 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards a80f91f615 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards 94e75d7fdc 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards 8f2e2f99b4 214: onsuccess: #47: 1: Success after gdb: 21 commits discards dd2e51cb15 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 07c2846409 212: force: #45: 1: Success after gdb: 22 commits discards 80b1f1eec4 211: onsuccess: #44: 1: Success after linux: 26 commits discards a34464b14f 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards 7f1713bd2e 209: force: #37: 1: Success after baseline build: no new commits discards 9ad63a12f8 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 35479484c1 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards e24bae0bce 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 426afee945 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 33fa3dd09c 204: force: #26: : Failure after baseline build: no new commits discards 1ed03f7f97 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards c6849db507 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards fe21867a18 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 54b62bbbc4 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 5ee74bd5a8 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 3e7339d323 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 1a01725e29 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 52e0d89cbc 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards d4f6d8ca09 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards fdb7973746 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards e20ad25407 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 20e1b733bd 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards d7557d58de 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 96eedc9dfb 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 1c0683d6e0 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards de5a5f3367 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards edc9708423 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards db008c3e0c 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards db1c74358d 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 99bcb294a7 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards fd6a8ca186 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards a02db94e98 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 7884469dc7 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards 6fe5c9dc06 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 0400c05c68 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 8dcbe4e663 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards d2bde14684 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 60d72f7e4f 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards dcf661aced 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 05ebe5689e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 705b5e6475 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 0bf581c36f 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards a344b5be9c 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 3ca9c6d34e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards dbc24b80e0 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 0caa182368 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards bb347b81b2 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 8466409d11 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards d3142f81e3 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards b8c337a7cc 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 906b80b54d 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards bbb1ede307 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 3d43808b53 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards bfa601ab60 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards f3be6e61b6 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards f5164c288f 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards aeffbf6018 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards d58199009f 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 4b5645306b 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards c32a3ac66d 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards a4463a70e5 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 853e0593f3 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 418a6235a4 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards bc09aae498 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 1ee1b38c2e 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards ea926129d2 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 45b3bae2ba 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards a4c1d4dec7 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 451e4f5eac 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards f8e33e126c 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 91ea56ff93 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 0ee33af7ad 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 5bfd655bc5 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 7026b91bad 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 110497219d 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 244862ac0c 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 285c1dbe21 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 98c7bc384a 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 80f9157c1b 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 099de3c065 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 8ecf1bba57 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 698bfa791c 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 69d06812c6 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 74d9699462 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 071d1361d6 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 50b6a4d771 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new fdf9bef5c8 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 2723609538 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 03b3b95f44 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new c15f1c5a0f 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new c014c6655d 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new bee330eb85 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new c63ab52bda 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 5b402e9bea 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new 871dcba3bc 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 933a95356c 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 057c32a792 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new 80845fb50f 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 8131d3abd6 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 0f5241c0e1 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 591ec7c318 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new f915556d72 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 3ebe6e1158 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new bef1204815 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 558adf0f7c 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new 137bcea343 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 846f7b3225 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 02a37d8120 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 565699bce0 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 0e0c06ccec 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new 0b5ea3bd10 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new 65525555d5 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 44a937ecc3 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new e481e16e1c 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new b00a843ba1 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new 84b6e4e0ad 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new db92db9eb7 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 0eeb87ccc3 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new d7e2d313ac 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 3ac09c7ccd 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new f5217b3b37 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new e8219bdbae 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new bafefea373 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new c7340cde0c 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 0539c35ab7 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 31ab5c9cc2 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 5d9b46335d 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 02e387f6b3 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new e7efd00c8d 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 431bc1cbd5 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 1499879d10 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new ce5e9a9b04 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new a25521a0b1 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 72ebe9d64b 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 7b05f16062 204: force: #26: : Failure after baseline build: no new commits new 62d20effd3 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new bfac0dd692 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new c0a2a603c0 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 1969be2416 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new aa83b24e41 209: force: #37: 1: Success after baseline build: no new commits new fda00296b9 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new e9aff42ac9 211: onsuccess: #44: 1: Success after linux: 26 commits new 768ea89af9 212: force: #45: 1: Success after gdb: 22 commits new f38dc6809a 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new b368a7cfd3 214: onsuccess: #47: 1: Success after gdb: 21 commits new d190bf7c85 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new ce9936ffa3 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new ed681399e1 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new 012489dc32 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 7e5550cd55 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 1bb8ba6dff 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 3e4feebc1b 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new cb3ec2d84b 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 78cc2e850b 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new fe058b3216 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 210901df0c 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 4f19e54592 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 0bca6d86ec 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new fe97647fd7 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 4c5bf9c6a5 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 2625437534 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 2cf8e9b1b2 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new ab59290485 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new fdea8fda44 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new b4197dc9f0 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 93f8c71822 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new a47e75a92b 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new b8aa34d91e 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 1eb3f2c48c 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new a14190742b 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new a0a6e649c7 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new 6fd1c8b14f 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new 5f2fe86dcb 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new 1d5276e723 243: onsuccess: #116: 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 (edaf87914a) \ 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 2084 -> 2064 bytes 02-prepare_abe/console.log.xz | Bin 2572 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 36180 -> 35428 bytes 04-build_abe-gcc/console.log.xz | Bin 205460 -> 205328 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8640 -> 8252 bytes 07-build_abe-glibc/console.log.xz | Bin 242600 -> 240812 bytes 08-build_abe-gdb/console.log.xz | Bin 35008 -> 34700 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2640 -> 2612 bytes 11-check_regression/console.log.xz | Bin 2920 -> 5224 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 --- 11-check_regression/results.compare | 13 +++- 11-check_regression/results.compare2 | 87 ++++++++++++++++++++++++++- 11-check_regression/results.regressions | 15 ----- 12-update_baseline/console.log | 70 +++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 22 ++++++- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 13 ++-- mail/short-diag.txt | 2 +- manifest.sh | 32 +++++----- results | 15 ----- sumfiles/gdb.log.0.xz | Bin 1998632 -> 1983660 bytes sumfiles/gdb.log.1.xz | Bin 28000 -> 15128 bytes sumfiles/gdb.sum | 18 +++--- sumfiles/gdb.sum.0 | 20 +++---- sumfiles/gdb.sum.1 | 103 ++------------------------------ 33 files changed, 208 insertions(+), 222 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions