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 50019bdb29 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards 1a73660738 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards 161da876b5 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 03a4164f86 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards 8afa88d014 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards 3611c9cc86 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards c3a4ecf6fb 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards b190a8db38 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 180e03e6ad 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards a2757c3b1d 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards cdfc078b62 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards bbf4c3e305 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards 0219916bda 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 9e7720466e 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 1fbabc78f8 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 92c6a9a2b1 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards f781f3c4bf 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 67b90a02a3 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 95bf542f95 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 89e8c43e7a 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards 94e0a61b51 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 84eb0f91bd 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 4a48e6ac6a 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards cc434bf8b7 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards c8dddb8809 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 66700d037c 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards cf9acbb44c 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards 27579603e0 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 384ef89332 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards f3f6e4647a 212: force: #45: 1: Success after gdb: 22 commits discards d439e08c47 211: onsuccess: #44: 1: Success after linux: 26 commits discards caeb00033f 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards 7018cb0ead 209: force: #37: 1: Success after baseline build: no new commits discards ee0683754c 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards b444924074 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards bfaeddc1c1 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 8c08609290 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards f22f507cb9 204: force: #26: : Failure after baseline build: no new commits discards f5dc578f32 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 487948fbed 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards cfe3710b9d 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards c271f6501c 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 3bb131701f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 2e67f9f0e3 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards ab061da5fc 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards f6c1608659 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 508f6f9534 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards c9be668f16 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards b5f2c7a42a 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 75914bf466 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 220ca48365 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 59f7e62287 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 6143c8a9d8 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 6ee797fe4c 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards ae624785d5 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 56930e59b2 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 6f384938ec 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards ca335f29cb 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards f0585eb225 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 8c77bea947 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards b4d50aca83 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards fb96ff87a9 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 586e7d51dc 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 9768c338cb 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards 5b7fa20b6b 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 19407e69d4 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards 4163d6b13e 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 50e74b306e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 7127d09e1c 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards a04ab63597 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 2331d4f262 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards f6d3166b68 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 7c53b94b76 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 83bd4a036d 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 480e69f608 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 12251e6ee8 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 03102ddca3 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards 28566e64ab 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 42ddcc8452 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards cf94419145 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards bbe3493b56 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards d5c48f3e34 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 73e4c0da52 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards a33becb746 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards eeeb05bc60 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 843046d22d 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards faa3211ca4 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards b0d378a61b 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards b8237f1345 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 4feed10e28 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 3a90b97e0c 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 75a38af914 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards edcf6822b4 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 4d2b274b3e 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 27eefcd125 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards e142bde3ae 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 5791559dfa 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 0f0dca9b2d 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards a1ffc5ad44 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards d350db195a 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 4dac7c83b5 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 570b49d6b5 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 0ee33af7ad 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 91ea56ff93 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new f8e33e126c 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 451e4f5eac 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new a4c1d4dec7 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 45b3bae2ba 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new ea926129d2 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 1ee1b38c2e 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new bc09aae498 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 418a6235a4 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 853e0593f3 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new a4463a70e5 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new c32a3ac66d 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 4b5645306b 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new d58199009f 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new aeffbf6018 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new f5164c288f 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new f3be6e61b6 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new bfa601ab60 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 3d43808b53 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new bbb1ede307 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 906b80b54d 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new b8c337a7cc 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new d3142f81e3 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new 8466409d11 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new bb347b81b2 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 0caa182368 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new dbc24b80e0 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 3ca9c6d34e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new a344b5be9c 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 0bf581c36f 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 705b5e6475 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 05ebe5689e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new dcf661aced 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 60d72f7e4f 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new d2bde14684 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 8dcbe4e663 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 0400c05c68 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new 6fe5c9dc06 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new 7884469dc7 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new a02db94e98 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new fd6a8ca186 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new 99bcb294a7 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new db1c74358d 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new db008c3e0c 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new edc9708423 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new de5a5f3367 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 1c0683d6e0 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 96eedc9dfb 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new d7557d58de 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 20e1b733bd 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new e20ad25407 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new fdb7973746 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new d4f6d8ca09 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 52e0d89cbc 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 1a01725e29 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 3e7339d323 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 5ee74bd5a8 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 54b62bbbc4 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new fe21867a18 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new c6849db507 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 1ed03f7f97 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 33fa3dd09c 204: force: #26: : Failure after baseline build: no new commits new 426afee945 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new e24bae0bce 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 35479484c1 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 9ad63a12f8 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 7f1713bd2e 209: force: #37: 1: Success after baseline build: no new commits new a34464b14f 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new 80b1f1eec4 211: onsuccess: #44: 1: Success after linux: 26 commits new 07c2846409 212: force: #45: 1: Success after gdb: 22 commits new dd2e51cb15 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 8f2e2f99b4 214: onsuccess: #47: 1: Success after gdb: 21 commits new 94e75d7fdc 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new a80f91f615 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new e806de22ac 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new cdefe98284 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 0ae840e640 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 89b09fe864 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 1813fe4cfc 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new a3208ceb9a 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 5099ee1435 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new c3a1cd0714 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 06f8b8f85e 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 0dcf8360a3 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new ecfdb26654 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 8e3c23491a 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 863f8ba43d 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 3b7fd5ae7b 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 1592d033ab 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 61973bd801 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 6a719e84a4 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 6a5dd8c7ed 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new a1daf9b002 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new b8f735f298 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new 0c14ca764d 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new d5537f624c 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new cc8e9f9c00 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new 072dc0351d 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new 1efeea2721 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new edaf87914a 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...]

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 (50019bdb29) \ 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 2208 -> 2084 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2572 bytes 03-build_abe-binutils/console.log.xz | Bin 35036 -> 36180 bytes 04-build_abe-gcc/console.log.xz | Bin 204088 -> 205460 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8652 -> 8640 bytes 07-build_abe-glibc/console.log.xz | Bin 241032 -> 242600 bytes 08-build_abe-gdb/console.log.xz | Bin 34752 -> 35008 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2620 -> 2640 bytes 11-check_regression/console.log.xz | Bin 4152 -> 2920 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 +++ 11-check_regression/results.compare | 14 ++++- 11-check_regression/results.compare2 | 106 +------------------------------- 11-check_regression/results.regressions | 15 +++++ 12-update_baseline/console.log | 70 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- mail/changes-list-long.txt | 8 +-- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 26 ++++---- mail/short-diag.txt | 2 +- manifest.sh | 13 ++-- results | 15 +++++ sumfiles/gdb.log.0.xz | Bin 1999124 -> 1998632 bytes sumfiles/gdb.log.1.xz | Bin 15124 -> 28000 bytes sumfiles/gdb.sum | 26 ++++---- sumfiles/gdb.sum.0 | 28 ++++----- sumfiles/gdb.sum.1 | 103 +++++++++++++++++++++++++++++-- 29 files changed, 230 insertions(+), 208 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions