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 ec04ff92f29 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards e69af07177d 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards f16bb796bae 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 85d97d4e194 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards d52f80b57c9 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 4eae68f16e9 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 52dd951488d 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 6b4e9c55239 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards e46919613fd 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards ca1f878ca0d 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards fdb89f4a88f 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 4744bf7061e 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards ff094d6845b 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 4842935df25 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 68ab1d9e0b0 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards d2025cdac96 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 5a4d5c89daa 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 331e91c943f 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 334d1a998b7 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 45a7713bae0 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 0463c429137 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards a58d7458c7b 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 1eab72d35fc 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 9a1ca1a8b5f 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 20f93b72360 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 23437da3bbf 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards be5d676ba11 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 159e2c4827a 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 97d0e75b950 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 3f8fdf6fd11 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards bfbb05ef51b 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 259391cff47 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 83628fe4eed 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 8a218ce58a5 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 2afaf8cbf9a 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards fa768f4bcb2 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 2c10c819a07 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 8769a54ebd2 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 2d1b5f89842 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 7252a8e494f 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards be7011f4322 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 645559e6677 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards f9da1b613be 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards f38f7efc26e 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards b6408267b73 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 440e95c6ad4 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 68090aa7951 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 8a779cce96d 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 775ad64cc0d 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards fd29e03af9f 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 07c3685ee5c 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards f0a0da2955a 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards d1392b51aa7 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 90ac1940ba0 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards dbeb3c97c97 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards c1226ec49e6 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 8e197fffc4a 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards e751106e9e0 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards b0aa9555f89 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 7eb15183fc8 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 625220b8c8e 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 27da9d3d1bd 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards dfd490a281f 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 68ca0a57c23 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 2fee209bdc4 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 68a3ace8bdc 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards a20225318b6 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 1b880259fbd 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 61aabe2584d 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 4f5cf158cfe 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards f9706780b2c 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards a59c6a6ba1c 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 549ee920396 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 2e5bf245a26 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 1e92506f1fc 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 1140aee86c7 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 57936204b73 121: onsuccess: #908: 1: Success after glibc: 2 commits discards e5d0520965d 120: onsuccess: #906: 1: Success after binutils: 29 commits discards bbea663c0de 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards dd09ae6e700 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards eb6f2e339d1 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 9ebe658f263 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 151ce6a71c6 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 5c9f2ff4ee1 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards e0e1d63cfc6 113: onsuccess: #898: 1: Success after linux: 3 commits discards b002c20554c 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 6b7efded314 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards ac88570607c 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 56c34e946ff 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 6d3a2b783a4 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 6816fffd008 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 1fb20ce4d4d 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 14eea477add 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards f86242d2bcd 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 1a89924eb35 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 396c0d7d0d4 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards f3a72e267af 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards be35076f2b6 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards c13f5eba18b 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 15685ad1b25 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards 30bcefb1f93 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 372720f80e6 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 4bcfc1a0fa1 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new 1da50820ca9 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 53382b1c3ff 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 7ffc1ab676c 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 43600ee39a6 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 4578ff13c3f 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 3f41814dc7f 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new c9e82a9cf79 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 6a4ea6892d2 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 9092f93c7f4 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 3d9b78993ec 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 070e965b229 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 5bdbf8cd14d 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new a7df0756954 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 9ed492663e1 112: onsuccess: #896: 1: Success after binutils: 24 commits new 637b52d88db 113: onsuccess: #898: 1: Success after linux: 3 commits new 3407062afca 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new fabf37a00bb 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new c43742facaf 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 40d148a1e85 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new ac73afb02af 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 950cc325f8b 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 414afc8df82 120: onsuccess: #906: 1: Success after binutils: 29 commits new 46b2936da72 121: onsuccess: #908: 1: Success after glibc: 2 commits new 493585bd0a1 122: onsuccess: #909: 1: Success after linux: 2753 commits new adcbed02b18 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new d4da0e4fb99 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new def3a9dd764 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new e82edbb58c9 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new cb4ea410896 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new c5250dafc09 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 3eeed27b2d5 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new d769989037c 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new d48f412f9e0 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 2de3bf88350 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 4baca45b1ee 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 596733803f4 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 5aba20b7a9a 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new d90f067a598 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 1dc274f8ecc 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 31b84974540 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 597086b6159 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 6303bbc35eb 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 19dc86d77b1 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 06f693174a5 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 49b4cc16aa6 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new c464c0017f3 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 9a44b287cb5 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 179c91517a9 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 20938806c52 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 0a618a9f62a 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 6b2b38e24a7 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new accbf18182b 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 1707acd528d 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 2355a388dd8 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 5ff52e22988 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new edbd161abf3 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 1268596666a 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new c7f99d0ac26 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 16ac907cb13 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 8c4956eaa3c 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 7face6efeb5 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new c254918b417 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 9f2904b6653 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 722ada7c54f 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new aaa45199805 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 3a2d451fa83 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 206f8bcb2fc 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new f47f8c7442a 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new da0edffa201 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new fb109424b96 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new fd4921e4d66 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 685523c22be 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new aac91354f35 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new b0a6d2a50b2 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 5faafc8340e 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new c144b1489ac 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new f4eb8b07224 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new ee8d4c2b17d 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new e61d255aced 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 05ebafa3699 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 4c9791622d0 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 36ffec29686 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new b6ff694ad6c 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new b92b0c2b2f2 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new cf6103fd624 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 40babb10263 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new d538b3b976d 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 2b3c4a46586 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 9608b60a5a6 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new b7bbb770624 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new c293381f8c0 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 84191673b11 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 9d9839cadab 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new a4db994174a 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new f9e64a0d215 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 0424eb54901 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 6066c028ca7 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new cab3432de1a 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new e8942aac13f 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new c88e51e4243 198: onsuccess: #14: 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 (ec04ff92f29) \ 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 1768 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 38884 -> 39316 bytes 04-build_abe-gcc/console.log.xz | Bin 203840 -> 206548 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 10104 -> 8528 bytes 07-build_abe-glibc/console.log.xz | Bin 244200 -> 246352 bytes 08-build_abe-gdb/console.log.xz | Bin 38280 -> 38664 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3756 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2112 -> 2080 bytes 11-check_regression/console.log.xz | Bin 7004 -> 7064 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 6 +- 11-check_regression/mail-body.txt | 44 +- 11-check_regression/results.compare | 15 +- 11-check_regression/results.compare2 | 101 +- 11-check_regression/results.regressions | 15 +- 12-update_baseline/console.log | 40 +- 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 | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 15 +- sumfiles/gdb.log.xz | Bin 2027672 -> 2001036 bytes sumfiles/gdb.sum | 4336 +++++++++++++++---------------- 31 files changed, 2360 insertions(+), 2314 deletions(-)