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 e27aadb1e8c 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards b501e1fe4f2 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards c60874571d8 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards eca4bd5af01 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards e454b1e3e08 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 06b32a2ee59 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 83dbc1faead 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 24601174782 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards bd960d697d8 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 7e00d539f0f 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards ab3268bce36 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards c15644cc51a 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 19f8d229b0f 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 3f2d1b294f4 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards d7d1ca070b1 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 43f637acd56 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards eca5d866768 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards b38a4f0eb75 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards c66740cf985 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards fcb8e43d007 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards f54b8e69251 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards b598502d351 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 6df3331d662 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 3e2e3cee547 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards ad4dfa4f123 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards d8172b89318 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 6db535e462c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards eb97fd468f5 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 1c5ee70fc14 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 516d844d3e9 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 1d0314e30de 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 81edd316a4c 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards a8f669f64d6 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards f30dd3101df 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards c713600e88a 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards fab320fd2c1 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 85cf39b1e8b 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 0a26666bf17 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 422a37d0e07 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 7c34444dcc9 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards e7072affca9 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards ce16eb26885 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 2acc962fad1 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards bacace96583 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 0a8d0318e68 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards fa735bd9d12 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 60e7471807c 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards c75cb71b621 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 63e218d01ba 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 3fe0475958f 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 01b6c2127b8 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 0af4c3fab1b 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards d6b7d6cff62 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards ced2a4ea7c2 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 3467d7bf2ae 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 8bd7446c4b7 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards d03ba0dea76 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 25d96ed1909 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards b4ca68855cb 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 87b5d59b046 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards ac832597911 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 5764d603efe 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards d63d6bcf80c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 981152c84df 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 4e54a6f98d7 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards ff322691b57 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards d38af193d76 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 8dbd74aca79 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 592290e7340 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards ff549f546f7 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 30c5b92e115 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 78ba52b3670 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 71d1e96bcbd 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards f50bb18e367 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 48b8848a570 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards dd6d4b199a3 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 13a30c42c1c 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 3360ee4b06d 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 66f3758b7fd 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 1b7fb2bca99 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 8ce025a6460 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 164e19b9c47 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 268bc041d83 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards d601d2755b1 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards b7e9a3f30bb 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 296552bf784 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 64a49412128 125: onsuccess: #614: 1: Success after linux: 12 commits discards bb524ca79ef 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 82f8f861cfc 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 6e0e6608b94 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 544b455fd5e 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards a90eed535cf 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards b4465b90eac 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards f568c71b395 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards b2eeadce232 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards c3e89a6c412 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 0b5004b16c7 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 07433011600 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 71ccd5d97d5 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 1aad1c6ed29 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards 81ae32652ae 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 86718c7c81b 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 3de94cbbe73 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new d6a1c8c2eb0 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 2b69c8a4ff1 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 6e5628faf95 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new cb9012d3ce3 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new b775f7bebe5 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 36989457128 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 4c345492d37 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 362095951f9 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 50520d08ed4 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 04b4eb34bc1 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 2ec9e63e0cb 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new bc7241e12a5 124: onsuccess: #612: 1: Success after binutils: 18 commits new 11f664acf87 125: onsuccess: #614: 1: Success after linux: 12 commits new e4276f24cbe 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 76d602248d3 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 39fb1ba27de 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new dd6f401e943 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new a66cb6f5f17 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 0a86091fe36 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 60b80417284 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new b5d673e9283 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new c13aa8c4850 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 30052c5e450 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new f6af779a06e 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new edc5ea91c0f 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 28c8507f050 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new e049ed6f2de 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new bb8d211a465 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 4b3a9d6a78d 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 323cf72d116 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 7d9388ccda9 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 9d00eec9dc2 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new ae3500a9799 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 7bf955523d6 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new b008e2acdf3 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 5d066f9b194 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 4c653d9b665 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 2b9ad1e6c64 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 9fe19be7d72 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new d3d114d5370 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 39e0837eb4c 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new b4050b1cff0 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new b15baf0f1d8 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new afbf343bf88 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 002e5f6da7b 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new aa50b389acb 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new b515fa0ef23 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 3a89da45f25 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 025f9d5c8a2 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 049bdebaea8 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 50e9c4fae57 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 2fbcf8ce413 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 9acb487c76f 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new f786d33352b 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 4c115ffc0e7 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 7920d61bd72 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new c51b332f020 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new fb3857e859f 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 206d1d1f0c7 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new d3d566c70d9 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 2748d9befba 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 6caab166679 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new f5fad975d7d 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 591cf91d670 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new a469757b724 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new a6d2e7da3f1 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 105edc34498 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new f8cf8f8bdde 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 8ae7e1bd613 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 9f3275a0951 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 2425c1d3949 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 27b1cdb8dee 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 2db0aa2f90c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 3dcdfa77a50 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new e4a5dbc7ff4 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new beabba48ea7 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 0ecae54e53d 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new f4688a1c0ce 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 3c8cff479bf 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new a68d53bb77e 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 5224a4a8ed1 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 4be37f278e6 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 6521d1cbd35 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new d1b8bd70805 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 52d529c6bb3 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 88c2b1dd704 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 5fb219eca55 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new ba0cd1577a3 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new a03187fa5f1 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new fa735011e21 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new cdaa087258b 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 1e1d6b1259b 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 9b3a6924392 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new ca7f695c5cc 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 3fd27b061dc 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 108b33b93d9 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 621bc209147 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 0d0957742da 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new c0e6bc41486 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 3f3e618421f 212: force: #27: : Failure after baseline build: no new 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 (e27aadb1e8c) \ 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 1808 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 3444 bytes 03-build_abe-binutils/console.log.xz | Bin 52656 -> 52668 bytes 04-build_abe-gcc/console.log.xz | Bin 238028 -> 236000 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9080 -> 9236 bytes 07-build_abe-glibc/console.log.xz | Bin 235084 -> 235808 bytes 08-build_abe-gdb/console.log.xz | Bin 50268 -> 50308 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3748 -> 3764 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2016 -> 1052 bytes 11-check_regression/console.log.xz | Bin 7716 -> 2504 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 19 - 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 97 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 56 - 11-check_regression/results.compare2 | 202 - 11-check_regression/results.regressions | 58 +- 12-update_baseline/console.log | 72 +- dashboard/dashboard-generate.sh | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 97 +- mail/mail-subject.txt | 2 +- manifest.sh | 27 +- results | 62 +- sumfiles/gdb.log.xz | Bin 2948932 -> 0 bytes sumfiles/gdb.sum | 99732 ------------------------------ 28 files changed, 96 insertions(+), 100337 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.compare delete mode 100644 11-check_regression/results.compare2 delete mode 100644 sumfiles/gdb.log.xz delete mode 100644 sumfiles/gdb.sum