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 30ec3b87bba 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 599d25e006b 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards c7105cadf1a 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards fce334210f6 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 31fba11e271 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards cb2fa247a17 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards b85882dd05b 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 7ac7a745ef0 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards b702989fcfe 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 59418928418 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards e9eba068418 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 8144c3604be 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards d3f1ed35b47 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards c19cd8b130a 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 16d19ae9221 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 0db4d20c27d 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 22ea7bf28d7 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 1788ad01b7b 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards e43f0c4ddfa 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 1f177c63c5e 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 2fed89ab352 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards f361b170780 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 100ae9b0ccd 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 01884079225 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards b06e70d758e 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 7a4dfd69688 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 58eb5294eeb 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 10ea0e6e9b2 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 2eb25f874a6 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards bcdd066b567 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 1939801570d 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards cddfc72f09b 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards a94e703a63e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards a9111806a74 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 54d7340ffe2 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards d5e60d7607e 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 9b843a816d5 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 76883ea2e52 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 9c9d23ed750 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 3446ee8a198 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 2589e81cd41 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 150b2887e54 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards bbe79af3dda 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 97cc0b09e45 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 6566186fb41 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards f197ed10aeb 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards e1dd2ed08a7 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 29f52b09209 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards d9337134808 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards b0f9edf1a1c 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 267876fd856 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards abacd24b13d 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 866b6d45949 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 4432ba9547e 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 74251e77a26 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 21feb506a5f 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards f650340a466 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 1c4b6928014 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 86fd93a66ee 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 5ba46865ef4 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 59f85a01ae8 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards e8a33663d75 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards a6b81ddcb82 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards de6ff1e6020 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards b5d72cd8280 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards c919063430f 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 2d4e960fbbf 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards b524061dcf9 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards d383790abde 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards b18dff17f07 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards eb51f6723c1 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards c3bcb3cc06a 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 04048dad066 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 8755f1128b7 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 998e22a7255 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 35ae9f66311 121: onsuccess: #908: 1: Success after glibc: 2 commits discards a4c61aecdbd 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 2843641a658 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards b2a065183ef 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 1cec271b468 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 138bfc35d5b 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 7c75e6b1951 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 79c45ab64b4 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 53d1180be5b 113: onsuccess: #898: 1: Success after linux: 3 commits discards 2c5b2f678c7 112: onsuccess: #896: 1: Success after binutils: 24 commits discards d2ba226b257 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards e3d0360b9e2 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards abc38be16e2 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 6382697d283 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 726b03287e1 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 9d1182af3ce 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards beeba39c822 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 5864cfa7de1 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards e2196cacc53 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 06824f0724e 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards 6aad6537b1f 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards e0458ae349f 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 766574fc047 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards e4245d6e270 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards b5f69221186 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards a52ea58529e 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new f7facfb846d 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new 30bcefb1f93 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 15685ad1b25 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new c13f5eba18b 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new be35076f2b6 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new f3a72e267af 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 396c0d7d0d4 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 1a89924eb35 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new f86242d2bcd 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 14eea477add 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 1fb20ce4d4d 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 6816fffd008 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 6d3a2b783a4 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 56c34e946ff 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new ac88570607c 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 6b7efded314 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new b002c20554c 112: onsuccess: #896: 1: Success after binutils: 24 commits new e0e1d63cfc6 113: onsuccess: #898: 1: Success after linux: 3 commits new 5c9f2ff4ee1 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 151ce6a71c6 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 9ebe658f263 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new eb6f2e339d1 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new dd09ae6e700 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new bbea663c0de 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new e5d0520965d 120: onsuccess: #906: 1: Success after binutils: 29 commits new 57936204b73 121: onsuccess: #908: 1: Success after glibc: 2 commits new 1140aee86c7 122: onsuccess: #909: 1: Success after linux: 2753 commits new 1e92506f1fc 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 2e5bf245a26 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 549ee920396 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new a59c6a6ba1c 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new f9706780b2c 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 4f5cf158cfe 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 61aabe2584d 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 1b880259fbd 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new a20225318b6 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 68a3ace8bdc 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 2fee209bdc4 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 68ca0a57c23 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new dfd490a281f 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 27da9d3d1bd 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 625220b8c8e 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 7eb15183fc8 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new b0aa9555f89 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new e751106e9e0 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 8e197fffc4a 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new c1226ec49e6 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new dbeb3c97c97 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 90ac1940ba0 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new d1392b51aa7 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new f0a0da2955a 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 07c3685ee5c 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new fd29e03af9f 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 775ad64cc0d 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 8a779cce96d 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 68090aa7951 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 440e95c6ad4 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new b6408267b73 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new f38f7efc26e 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new f9da1b613be 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 645559e6677 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new be7011f4322 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 7252a8e494f 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 2d1b5f89842 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 8769a54ebd2 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 2c10c819a07 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new fa768f4bcb2 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 2afaf8cbf9a 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 8a218ce58a5 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 83628fe4eed 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 259391cff47 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new bfbb05ef51b 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 3f8fdf6fd11 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 97d0e75b950 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 159e2c4827a 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new be5d676ba11 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 23437da3bbf 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 20f93b72360 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 9a1ca1a8b5f 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 1eab72d35fc 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new a58d7458c7b 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 0463c429137 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 45a7713bae0 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 334d1a998b7 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 331e91c943f 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 5a4d5c89daa 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new d2025cdac96 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 68ab1d9e0b0 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 4842935df25 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new ff094d6845b 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 4744bf7061e 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new fdb89f4a88f 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new ca1f878ca0d 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new e46919613fd 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 6b4e9c55239 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 52dd951488d 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 4eae68f16e9 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new d52f80b57c9 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 85d97d4e194 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new f16bb796bae 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new e69af07177d 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new ec04ff92f29 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...]

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 (30ec3b87bba) \ 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 1780 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 38840 -> 38884 bytes 04-build_abe-gcc/console.log.xz | Bin 204460 -> 203840 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9524 -> 10104 bytes 07-build_abe-glibc/console.log.xz | Bin 244004 -> 244200 bytes 08-build_abe-gdb/console.log.xz | Bin 38500 -> 38280 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3760 -> 3756 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2100 -> 2112 bytes 11-check_regression/console.log.xz | Bin 7616 -> 7004 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 45 +- 11-check_regression/results.compare | 19 +- 11-check_regression/results.compare2 | 248 +- .../{mail-body.txt => results.regressions} | 46 +- 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 47 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 29 + sumfiles/gdb.log.xz | Bin 1922312 -> 2027672 bytes sumfiles/gdb.sum | 4354 ++++++++++---------- 31 files changed, 2414 insertions(+), 2498 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum copy 11-check_regression/{mail-body.txt => results.regressions} (53%)