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 c88e51e4243 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards e8942aac13f 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards cab3432de1a 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 6066c028ca7 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 0424eb54901 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards f9e64a0d215 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards a4db994174a 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 9d9839cadab 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 84191673b11 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards c293381f8c0 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards b7bbb770624 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 9608b60a5a6 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 2b3c4a46586 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards d538b3b976d 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 40babb10263 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards cf6103fd624 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards b92b0c2b2f2 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards b6ff694ad6c 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 36ffec29686 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 4c9791622d0 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 05ebafa3699 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards e61d255aced 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards ee8d4c2b17d 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards f4eb8b07224 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards c144b1489ac 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 5faafc8340e 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards b0a6d2a50b2 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards aac91354f35 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 685523c22be 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards fd4921e4d66 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards fb109424b96 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards da0edffa201 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards f47f8c7442a 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 206f8bcb2fc 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 3a2d451fa83 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards aaa45199805 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 722ada7c54f 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 9f2904b6653 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards c254918b417 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 7face6efeb5 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 8c4956eaa3c 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 16ac907cb13 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards c7f99d0ac26 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 1268596666a 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards edbd161abf3 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 5ff52e22988 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 2355a388dd8 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 1707acd528d 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards accbf18182b 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 6b2b38e24a7 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 0a618a9f62a 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 20938806c52 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 179c91517a9 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 9a44b287cb5 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards c464c0017f3 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 49b4cc16aa6 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 06f693174a5 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 19dc86d77b1 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 6303bbc35eb 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 597086b6159 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 31b84974540 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 1dc274f8ecc 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards d90f067a598 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 5aba20b7a9a 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 596733803f4 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 4baca45b1ee 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 2de3bf88350 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards d48f412f9e0 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards d769989037c 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 3eeed27b2d5 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards c5250dafc09 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards cb4ea410896 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards e82edbb58c9 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards def3a9dd764 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards d4da0e4fb99 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards adcbed02b18 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 493585bd0a1 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 46b2936da72 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 414afc8df82 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 950cc325f8b 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards ac73afb02af 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards 40d148a1e85 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards c43742facaf 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards fabf37a00bb 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 3407062afca 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 637b52d88db 113: onsuccess: #898: 1: Success after linux: 3 commits discards 9ed492663e1 112: onsuccess: #896: 1: Success after binutils: 24 commits discards a7df0756954 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 5bdbf8cd14d 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 070e965b229 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 3d9b78993ec 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 9092f93c7f4 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 6a4ea6892d2 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards c9e82a9cf79 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 3f41814dc7f 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 4578ff13c3f 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 43600ee39a6 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards 7ffc1ab676c 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 53382b1c3ff 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 1da50820ca9 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 4bcfc1a0fa1 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new fc03bca7989 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new ba8222b2009 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new f2e32dbbbf2 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 5479ec729bf 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 03b5898e3a4 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 5dc59696ae8 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 52c0ec1eaab 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 4c4d24a3bed 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 88f28f46d7d 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 4a871287089 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 4947268fb7a 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 2dc4ef3f99f 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new ace15799072 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 448a3547b19 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 77e60be497b 112: onsuccess: #896: 1: Success after binutils: 24 commits new a2f0f20c7f9 113: onsuccess: #898: 1: Success after linux: 3 commits new 485901f5bde 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new b2ced024808 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new f045b1dc2a8 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 738711bd7af 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new fbaa572f607 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 6820e294018 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 2bb7f572db9 120: onsuccess: #906: 1: Success after binutils: 29 commits new 883de510884 121: onsuccess: #908: 1: Success after glibc: 2 commits new 32a119d17ad 122: onsuccess: #909: 1: Success after linux: 2753 commits new e74189c20b5 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 6e9b1e2fced 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new b769e3a8d95 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 7b634c46cae 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new c6c4219b5f1 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new e436ebcdc2c 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new c8c0b716f92 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 02e07bc449a 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 178e6c20c5b 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 7f89d195f25 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 119e637a07f 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 5141fc31e23 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new a7e32d83255 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 5dd3af22b3a 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 31a2d836403 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 56c8f7b0727 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new ac141733f26 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 8b177491d1a 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new cc4af5a09ff 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 8ae3d0b1510 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 49758443715 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 3edd432330b 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 92b637ece2f 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 8e02c052771 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new ad18cc1f1b5 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 5190850d55a 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 5589e305721 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new a2b012e8e02 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 9c21f0fe6cf 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new ddd91996b49 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 637aa40b044 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 28c1c8de767 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 0331ae1ab75 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 414a8ee0c9d 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 0a3ca31ffd5 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new b43dedee80e 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 0a89dbe1516 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 98a7fa432e2 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new adcb8bc6829 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 01820c809c2 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 98adeae3457 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new c48c938b51d 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 26cd956c156 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new c533f6212b0 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 2333aa895bc 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new 6864dfc9d35 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new bdd3293e9b4 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 37df8712566 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 1a5134717c2 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new e7c7c95eb9d 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 8ed2c112110 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new ea3634c53d5 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new b9a31b6dd14 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 56296b08385 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 82ca886f767 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 10802220597 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 780a94b085a 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new b23eda6104d 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 698d5b596c1 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new b4c16f054d1 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 1fd6542829b 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 13608521b74 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 4fc9bd4e14f 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new bfac00a47a8 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new dfc9262be6f 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 7857b8ea16c 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new e8367700173 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 5fe2a08c198 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 3720770d991 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 9e491ecbc03 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new a8fd9e1e829 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new f534738ba89 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new b488a1af5b2 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new bc68cf84bfa 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 58d006142a3 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new a0e2b2424b0 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new ddbd640d562 199: onsuccess: #15: 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 (c88e51e4243) \ 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 1792 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39316 -> 38940 bytes 04-build_abe-gcc/console.log.xz | Bin 206548 -> 203616 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8528 -> 9588 bytes 07-build_abe-glibc/console.log.xz | Bin 246352 -> 243912 bytes 08-build_abe-gdb/console.log.xz | Bin 38664 -> 38628 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3768 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2080 -> 2132 bytes 11-check_regression/console.log.xz | Bin 7064 -> 6612 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 | 21 +- 11-check_regression/results.compare2 | 103 +- 11-check_regression/results.regressions | 30 - 12-update_baseline/console.log | 68 +- 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 | 47 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 30 - sumfiles/gdb.log.xz | Bin 2001036 -> 1923280 bytes sumfiles/gdb.sum | 4348 ++++++++++++++++--------------- 30 files changed, 2308 insertions(+), 2440 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