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 0d271fa401 252: onsuccess: #134: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 0ddf5caf39 251: onsuccess: #133: 0: [TCWG CI] https://ci.linaro.org/job [...] discards 8224056397 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 0cd58f85b0 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 3c7d770dbe 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 07da871676 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] discards d0b0d79c0b 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 0588b2d400 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards 8c30818ea4 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards 8368f65531 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards e5e1e30723 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards cc77390c0b 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards 9f66097fef 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards dade27e32a 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 51825ed185 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards e6b5740294 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards b2b77494ef 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 83b47283bc 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 04a0234376 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards ecc41ef2c8 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards 2d500a5715 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 96de014cae 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 97951127ad 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards 50a054d79d 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards 3914eb4606 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 304c2ac3ac 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards df5552d14d 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 954fc89b7e 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 34ea9d6959 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards dd694eb4a3 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards a3cbb6deac 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards 1b329d7057 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards eb97ace041 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards e3fc967336 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards b62539f844 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards 00e5024e8f 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards 119a82aa5c 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards 9269ceb3fc 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards 1dfa0ef4f5 214: onsuccess: #47: 1: Success after gdb: 21 commits discards c01e80b237 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 47e8a59694 212: force: #45: 1: Success after gdb: 22 commits discards 96603fa5e0 211: onsuccess: #44: 1: Success after linux: 26 commits discards a4b4a0e658 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards 89f8b9f817 209: force: #37: 1: Success after baseline build: no new commits discards 01982f02c6 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 831cd5a1e8 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards df89b6b210 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards b2e1e02b6d 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 97989d2003 204: force: #26: : Failure after baseline build: no new commits discards 3b85eaf1f3 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 981ed5a6dd 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards c3677780c3 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 1aff614615 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards a6ea4c937c 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 8cce525efe 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 77b98d6409 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 48bcb4c6ee 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 1f208d4fc8 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 5080e27ac1 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 3ba0be7823 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 5b3fd145f4 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards f3845ce15e 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 9be4802d1b 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 2e46fb5bb3 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 6ca0c2af8d 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 1804a9b825 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 0ccbbc2cf0 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards bbc7dbbe16 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards e21423e4c1 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards af3593628c 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards dd69a6a12a 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 3679ab5931 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards ffc238e932 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 951fe4c79f 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards 36fc891338 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards dc2953fdaf 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 21ab1c2941 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards 3573334983 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards d8abcd968e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards 88b26d15a0 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 5208b3f9d7 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 830e4f9a30 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards 1c6e35ab1c 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 22bde883d6 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 55045e7863 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards be0aca687d 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 2cf996184f 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards ed3d3e1808 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards acd4342b37 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 27d95236e8 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 02b86b49c1 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards ad1c000106 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards e1a26b737d 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 2fe16e3a17 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 0d859e2954 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 8d0b38f8e8 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards a2553b3e6f 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards da5e4b01a6 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 2a53afbd7e 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards bc64cf9f3f 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 67a9c257b2 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 1f67250c74 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 555cd4dfa2 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 1d87239306 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 1510021eda 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 083a5def92 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 041395584c 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new 0c4da86ff7 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 1e00c95a40 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new e226b1af12 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 3ee8eb5ce3 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 17be0fdcf0 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new cf342f8492 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new ff71db3d33 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 34fbc82edb 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new bf764c66a1 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new e086bf7bf3 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 179ffd84a9 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new f9b39bda58 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 041d283756 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 3b1b77b848 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 42afc1255c 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 8bb56fbef9 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new 3efba78ecd 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new b303950ad6 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new 3a946a21fd 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 62b3467db1 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 9f0b3f1730 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new 1145a64298 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new 4273b8aaf5 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new 40c8d5d270 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 4bfa015203 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 3cac9f6a03 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new d48fc6f5ed 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new 5221e61850 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 3d79b3c77f 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new c91d0c0308 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 21078bb7f1 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 3be3839a50 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 6c8f5b33a4 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 9ce60a041f 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new a8d46f0846 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new f9bf7a0456 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new b19cb0a9b8 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 14265daa64 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 8c8604aa30 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 1fd310439f 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new f4c39b3601 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 63a4237d9a 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 4d75dc5c52 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new a306298f05 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 9ae2f59f22 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 1d891b9b2f 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 5e652758fa 204: force: #26: : Failure after baseline build: no new commits new eed5e19f6b 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 431f3365ca 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 994a930329 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new cbac815f38 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 6f67d3a549 209: force: #37: 1: Success after baseline build: no new commits new c41ccaad3f 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new 32dc54c642 211: onsuccess: #44: 1: Success after linux: 26 commits new b8b1fcb75d 212: force: #45: 1: Success after gdb: 22 commits new ff1c679e71 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new 5e1935465c 214: onsuccess: #47: 1: Success after gdb: 21 commits new 31dfce6302 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 097ba28281 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new adf1be95b4 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new ffb70f2810 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 593dd7c1da 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new dc74c11b6b 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 9dbfd8e55d 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 10c7e7e8f6 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 19be6342ce 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 80221065f8 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 45f27b68cd 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new ee645c7a3c 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new ef43dfe17b 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 6784bb694a 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new cab9f50a30 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 73b2cba73c 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 6110957d31 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 7983672824 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new b6bbfc31e1 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new e11910c9b8 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 0af089b12e 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 4372d56f00 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new a1de94f84a 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new 52ca51e441 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new 08eb189997 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new 4615560553 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new f2cd5f2092 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new 35b1e6065e 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new 1a0a8369ce 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new ef3503c20f 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new 71f180f647 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new 346c86aebe 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 2acdf0f770 247: onsuccess: #122: 1: [TCWG CI] https://ci.linaro.org/job [...] new 7b1ed666da 248: onsuccess: #123: 1: [TCWG CI] https://ci.linaro.org/job [...] new dd7f93f283 249: onsuccess: #124: 1: [TCWG CI] https://ci.linaro.org/job [...] new a7093094b8 250: force: #132: : [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 1d4981ebcc 251: onsuccess: #133: 0: [TCWG CI] https://ci.linaro.org/job [...] new 042a4e37f6 252: onsuccess: #134: 1: [TCWG CI] https://ci.linaro.org/job [...] new 0375286895 253: force: #141: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...]
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 (0d271fa401) \ 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 2016 -> 2164 bytes 02-prepare_abe/console.log.xz | Bin 2488 -> 2448 bytes 03-build_abe-binutils/console.log.xz | Bin 35256 -> 35140 bytes 04-build_abe-gcc/console.log.xz | Bin 204160 -> 204276 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8244 -> 8416 bytes 07-build_abe-glibc/console.log.xz | Bin 241576 -> 241536 bytes 08-build_abe-gdb/console.log.xz | Bin 34600 -> 34900 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3056 -> 3156 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 548 -> 1240 bytes 11-check_regression/results.compare | 27 + 11-check_regression/results.compare2 | 1 + 12-update_baseline/console.log | 46 +- git/gdb_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 27 + manifest.sh | 26 +- sumfiles/gdb.log.0.xz | Bin 1916908 -> 1972076 bytes sumfiles/gdb.log.1.xz | Bin 784 -> 29644 bytes sumfiles/gdb.sum | 3668 +++++++++++++++++++++++++++++++- sumfiles/gdb.sum.0 | 3674 ++++++++++++++++++++++++++++++++- sumfiles/gdb.sum.1 | 605 +++++- 24 files changed, 7999 insertions(+), 81 deletions(-) create mode 100644 11-check_regression/results.compare create mode 100644 11-check_regression/results.compare2 create mode 100644 mail/results.compare