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 905ae4246a 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 46c70158b6 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards e5db4ada98 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards 536bd4fd8a 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards 8a376d5845 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards 639e72943c 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards b7d92261db 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards 4aded4a280 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards cf59be03fa 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards a592ecc632 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards ca2d4b2a24 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 5b5b76890c 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 281dfef30d 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards ab0b488fa8 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 3f7abf6f0b 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 53b8e524d0 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 84a96764d8 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards 8678b0569a 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 108d698a1b 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards e95d9e310f 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards 92e2ceefc5 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 49755b98f3 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 191cce1f3f 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 20f6ccd210 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards fe4c51f2b4 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards 56a84187ea 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards 305837ecb0 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 6864db3da2 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 937ebee9a5 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards fcc9d9082c 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 6ef14f7538 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards 4b4bc63c1e 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards fa69c77802 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 2f2cefbcab 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 18300479d7 212: force: #45: 1: Success after gdb: 22 commits discards cc2bc34277 211: onsuccess: #44: 1: Success after linux: 26 commits discards 054a52cc8e 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards db40e0a6db 209: force: #37: 1: Success after baseline build: no new commits discards 57ea8969bb 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 9dd9e2e24c 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 75d7a07d3c 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 4584cccea8 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 2562ec7183 204: force: #26: : Failure after baseline build: no new commits discards d3f533f8d0 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 1f61991179 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards e0ad26074d 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 9d43365333 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards c64dcb898d 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 296f5a1e25 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 8a0d327ef1 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 4315481bd4 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards e7a42fabec 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards d69b5dabb2 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 373778287b 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards b8998e3f71 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards bd12eff3ff 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 1847233e3e 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards f6a1e31a3d 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards d0f595c52f 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 3fc4546941 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 156e664459 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards bd27d76cea 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards cec8944cbd 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards 6af729e48c 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards 47bbf224aa 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards f035f0aaba 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards 770a105874 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards efa0871e5d 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 5afae13c65 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards 3f19ffb4af 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards d9092ffdd3 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards fd1cc9871a 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards b0dad22231 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 8d07842166 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 35ccecbea7 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 5cfdbf334b 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 6d5e1e8759 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards d39829fea6 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 061402460f 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards f67afc4e16 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards b2a9482e61 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 47f481f209 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards 8df9761b5f 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards bd5995549b 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 4fbe56cefe 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards d1b61b69dc 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 96ff5b259d 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 23b16d4613 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards fa74c010c8 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 0756e2e400 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards d12a0e46cb 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 355f32be22 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 6aae0be70f 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 59968ac5e4 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 3e9996d5f9 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 031f894e67 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 2e65186da3 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 6592157e73 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards ea81f7e16e 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 560c436913 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards f94ac1da83 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 66d924c22a 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 6f0bd7ea36 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 45396470af 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 96a5dab84b 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new c4cbcfa190 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 79143a31c3 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 97af7b1de8 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 5ae3635671 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 1d853451a6 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new f083a7c15f 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new d684797635 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 46f74c707e 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 0ab616cbeb 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 163cc9182f 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new fdd02ab0b6 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 2547da0637 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 00107a9482 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new 4bbc05dca6 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new d3bd158b14 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new dff9fa21e8 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new be698e8954 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new bd702424aa 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new ae4305687e 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new cf57201f6b 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 8df902743a 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new b6289274a2 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 03779142f0 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 8d72b17dfc 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new bc2bfc160d 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new 325f9415a9 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 7ddab638d9 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new bb6373d8f4 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 1b447647bb 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 3f86772dea 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new f2eca30c44 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new 09e4ebab09 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 4c5f971385 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 86bb1108a0 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new 73a743d3a1 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new e77e5217e1 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 351bef0649 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 06f8727f47 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 6e45b1d258 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 82ee2c61f6 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 1b844954e0 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 2a71618f97 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 2737de99ba 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new f0f489a7bc 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 7e58c85c64 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 93acf8f14f 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new ea23fe3523 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new d5bab3208b 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 3be61f3109 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 83d9f99334 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new f2e4f34896 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new be04207b1a 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 2da9e7c19e 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new d469c1d4c8 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 9dd4eff377 204: force: #26: : Failure after baseline build: no new commits new 17e214a6ed 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new e01d122cd1 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 6f47c9fdf6 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new e7dd845da5 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new d8ef35c544 209: force: #37: 1: Success after baseline build: no new commits new bc2ca4eaa9 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new cd99a44378 211: onsuccess: #44: 1: Success after linux: 26 commits new 8d2d952151 212: force: #45: 1: Success after gdb: 22 commits new 914b83d553 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new fe22a92347 214: onsuccess: #47: 1: Success after gdb: 21 commits new 87b300546d 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new e2fe78a287 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new f1dd114bd0 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new d58d30878e 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new aedaed592a 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new b7a2ffdd27 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new e6ccc2f06a 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 867f76587d 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 843ddc877a 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new f9a0e2c643 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new f8aec8734b 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 57e975e888 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new 61cdc08743 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 94501c6a53 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 766d4ba558 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 9025365e97 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 304e14c564 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 2cc306bddf 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new 454ec2df48 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 37d72ab8e0 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 8df3013bd6 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new afffca23ed 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new c8bb893b7b 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new de7382c03c 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new e938daeb78 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new ac2a3dfcf8 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new ef6351ddbe 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new 1c53b72eca 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new c40eb7c0be 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new 121a658acc 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new 913fd70b67 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new d0fa11c62f 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 71dce953a1 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...]
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 (905ae4246a) \ 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 2192 -> 2088 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 35520 -> 34836 bytes 04-build_abe-gcc/console.log.xz | Bin 203728 -> 203144 bytes 06-build_abe-linux/console.log.xz | Bin 8864 -> 8580 bytes 07-build_abe-glibc/console.log.xz | Bin 241556 -> 240772 bytes 08-build_abe-gdb/console.log.xz | Bin 34848 -> 34672 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2840 -> 2748 bytes 11-check_regression/console.log.xz | Bin 1588 -> 2388 bytes 11-check_regression/results.compare2 | 71 +++++++++++++++++++++++++++++++++- 12-update_baseline/console.log | 60 ++++++++++++++-------------- 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 +- jenkins/notify.sh | 2 +- manifest.sh | 37 ++++++++++-------- sumfiles/gdb.log.0.xz | Bin 1946612 -> 1926688 bytes sumfiles/gdb.log.1.xz | Bin 20324 -> 20320 bytes sumfiles/gdb.log.2.xz | Bin 5388 -> 5400 bytes sumfiles/gdb.log.3.xz | Bin 5428 -> 5248 bytes sumfiles/gdb.sum | 16 +++++--- sumfiles/gdb.sum.0 | 16 +++++--- sumfiles/gdb.sum.1 | 4 +- sumfiles/gdb.sum.2 | 4 +- sumfiles/gdb.sum.3 | 4 +- 29 files changed, 154 insertions(+), 72 deletions(-)