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 3230119cefa 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards c0ca3b5f2c3 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 4acafb10c1b 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards ae02bcfd302 204: force: #26: : Failure after baseline build: no new commits discards e51e00862ae 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards de1d572c553 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 9787542a957 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 47283ac8278 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 6dca639ae65 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards fabce85f550 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 48720cea33f 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 27c8e923cdd 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 8f6b86ed485 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 3582f8fa2ed 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards fc05875b6a4 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 822bb94c1f9 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 7568828f5ab 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards fef939bc442 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards fcd7a8ae659 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 5b62d9663cc 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards a130b07165f 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards ed5c73905ea 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 2cd6fbfa7df 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 88963063be7 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards e6bc8cc354f 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 4a02d827940 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 69f0908d642 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 09dcd8e7797 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 59e3ca5739e 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 65857556d8f 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 845109ddbb2 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards da6ff5e6d0f 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 945bde6b0d1 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards f1aa6dc339a 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 053d54f38e6 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 15d207059be 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards da2f3581271 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 75d38c4b964 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 9ddaf642aa8 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 7d45ef92ecd 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 1616611c20a 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards b7f32cd91ff 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 600e75cf46d 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards b4274d48a07 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 1e151b495dc 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 47e86e02703 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 3d1d7579247 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 2883bb8f849 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards b3a68b8fc7a 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 7c7c2617442 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 7982b1a81f2 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 94bd12d29b7 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 7e356c4df01 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 0341448b45c 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 53d58e76c2c 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards aed62960eb2 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 44a1e93b4a0 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards a6e9e05bc49 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 3f1cb9f3a9b 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards beec9e2aaaf 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 78b216b4314 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards fd857a08290 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 3da86ae2406 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards ae44ed1819a 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards d88f12fb00a 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 6fb8d1e3d1a 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 1740f70d9ab 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 5e1067023e8 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards dbae49dad30 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 4b3f8f4871e 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 9f547482de8 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 80af1bab75c 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 3ec39b60130 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 0c70e0b3e95 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards bc06ad15ac9 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards e77d45592a3 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 6a5f35ae914 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 0435b5b5ee6 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards d6128234ea2 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards fefcacf49f8 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 5e9b1b17ee0 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 46387ccb342 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards a1213fd054d 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 212d9c9ef89 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 45f0eee13aa 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards c35572b8fa5 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 6913ff5a111 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 43a4734b575 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 4e3728992ab 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 18133eb6351 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 9d408001b17 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards d71fcb2c94b 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 343ab397b38 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards b582a717e06 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 267a8866226 113: onsuccess: #898: 1: Success after linux: 3 commits discards 311d8758243 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 162bc711aee 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 8fdafe1bc4b 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 8e87d3f6a72 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 8136fce9963 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 7b011937a96 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 9560489e50a 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 275568c394f 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new d16ffcc8239 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new ce5759b7d94 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 83724d31f04 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 566fde48855 112: onsuccess: #896: 1: Success after binutils: 24 commits new 89a2dcfed29 113: onsuccess: #898: 1: Success after linux: 3 commits new 35e6c51af2e 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 1d9ba11c1a5 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new ebc87771bbd 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 5543c040a0f 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new baffa61b74e 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new ec7d0fae265 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 09c71667383 120: onsuccess: #906: 1: Success after binutils: 29 commits new 5dbcf2b3910 121: onsuccess: #908: 1: Success after glibc: 2 commits new ecc2e3be8a0 122: onsuccess: #909: 1: Success after linux: 2753 commits new 22e7dcc0d4e 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 25ce5599b45 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 573a3df0f94 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 8e3ce56fa00 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 5ebf3eba4e3 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 5b0ba83f9b9 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new f4573fdf329 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 1953ee35274 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 2b26f9c10d1 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 477c9b61a04 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 5e12a6b1ad8 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 7b981171314 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 111b98db5bd 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 694509a21f2 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 73f1b4ed0d9 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new d27039ab960 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 6f241f7ec99 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 988db039532 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new c42cebfba5e 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 1832537d9d7 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 84d42bfa4f5 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new de09690cd57 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 3337e2774fa 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 0c093da2681 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 50c5ad6e298 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 7cc893ae81b 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 4e6441369ed 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 4d3da5b8abd 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 224fbf6050d 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 56b19f927c2 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 79a363e0188 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new fc3d9c38bac 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new e24db1df809 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 165e7b55047 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 4862b40650f 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 77f06975662 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 8c67f6c6c19 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new cea29fc6784 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 00929e63d79 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new ba742861732 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 4128d9c651b 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 702c025a672 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 14dd819d4b0 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new da4cd963c7e 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new d4497e3e2ff 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 727dee43df9 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 55cce0fb705 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new c77d30d48a4 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 7009a3fb61c 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new e743be2377a 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 22129add1f4 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 718ae9e81cd 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new ca6379a17d9 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 953066a917e 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new bf0ac9c86f1 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 10167939857 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 4612887fc39 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 6ab1bbe77ef 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new e979749f3f2 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new f5a8e097312 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new ccc81b756aa 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new b658e8efe95 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new d8e2668aa02 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 245b2a79579 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 8dfa808796f 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 762b5421146 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new e692d266b9b 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 09490cdce92 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new a5ceded96c6 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new e64e57f0f87 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 531de0c4726 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 05c54f135d2 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new dc293035f5a 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 42b84639e66 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new f6b21e2edfa 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 1686972531f 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 2b2ed59a1f8 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 2b8e9cd502c 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new dbf6ebb215e 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new af0ab93f33f 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 9316d7943c5 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 875566855b2 204: force: #26: : Failure after baseline build: no new commits new bf66c74a9ef 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 50ca128c5bb 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new e547b858887 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 6ad3bb6d051 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...]
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 (3230119cefa) \ 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 1756 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2484 -> 2492 bytes 03-build_abe-binutils/console.log.xz | Bin 34968 -> 35248 bytes 04-build_abe-gcc/console.log.xz | Bin 203032 -> 202828 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8876 -> 8192 bytes 07-build_abe-glibc/console.log.xz | Bin 241856 -> 241768 bytes 08-build_abe-gdb/console.log.xz | Bin 34492 -> 34812 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2644 -> 2876 bytes 11-check_regression/console.log.xz | Bin 5584 -> 5700 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 12 -- 11-check_regression/mail-body.txt | 115 +----------- 11-check_regression/results.compare | 20 +- 11-check_regression/results.compare2 | 101 ++++++---- 11-check_regression/results.regressions | 20 -- 12-update_baseline/console.log | 40 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 117 +----------- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++-- results | 20 -- sumfiles/gdb.log.0.xz | Bin 1924668 -> 2010724 bytes sumfiles/gdb.log.1.xz | Bin 39740 -> 34764 bytes sumfiles/gdb.log.2.xz | Bin 14988 -> 14248 bytes sumfiles/gdb.sum | 50 ++--- sumfiles/gdb.sum.0 | 48 ++--- sumfiles/gdb.sum.1 | 315 +------------------------------- sumfiles/gdb.sum.2 | 14 +- 35 files changed, 201 insertions(+), 718 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