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_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts.

discards 7a4d2f19a8 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 95b5f0bb8e 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 7987962a28 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 508a70f4d4 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 085ee88eb1 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 604cbb2c99 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 0d27253812 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 635e868c6a 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ceec3014c7 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6faec1fc17 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards f3c15a4b8d 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards b6c54ccaf1 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 9b977533e6 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards a37ca7d8b0 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards 21c5a31896 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 097332713a 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 945d60f953 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards d2fa4ab96d 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 002972b9a9 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards c8ce71449b 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 444a561b98 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards b0f2d88663 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards aa2e70b17f 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 0c81b24697 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards af023365af 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 95ab6b2e13 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 49acbed38f 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards 166620149c 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 79eb1347f0 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards c14ea84c3e 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards ce46f409ab 127: force: #27: : Failure after baseline build: no new commits discards 5d09ac5e9e 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards aad54bd9fb 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards e2705604f4 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 9073753eea 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards cc2703097b 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 32e452c916 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 2f8f8cd364 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards ac2d12a11d 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 2f194aa76f 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 1930812bd4 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 5ab0458295 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 1e56b88f11 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 18631e20c9 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards b8322bca1a 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 19971e4295 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 0af76677fb 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards c50e6bd015 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards cc4867516a 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 46ec3bfb6e 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 81ae9f4f74 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards df2a671cc3 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards 1600dd552a 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards ea47594c35 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards c418700408 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards a803fe2238 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 5641c1942c 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 2b116172d6 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards d4e6d42624 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards ff14f2ee9f 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards be3637b4ed 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards c4277365de 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 9d0d24c15a 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 94c7aa8e39 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards ae5c47cdac 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards e7dad896f1 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 671f46f1a1 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 415883f9d6 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 9822dd7074 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards 9f1cd343b8 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards dcad555cc3 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 2fe94d9002 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 63f2cf509a 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 6a22bef658 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 5b41eac842 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 3dd4c171c4 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards ce65a516d5 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards a9cafcef93 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards d49dae964e 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 3733ae46c7 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards a1113e7fbe 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 044a68dac4 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 26405019db 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 5293793d2e 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 39fe987515 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards bc3aedfa48 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 22d0b2db9a 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards 04c348e56d 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 34a67fefae 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 83ccfbdba2 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards 11e65685b0 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 3fe0ba0fa1 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 6c957bd299 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards b08a259bc7 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 63c11a3d0e 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 14ec7d4d4b 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 860e32f6b9 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards 824b0fb5f4 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards 81ce7c29bd 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards 84247627e2 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards b27c57c35b 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new c0ad985260 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 4005d20e3a 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new bd280145cf 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new dc382d9bef 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new aa75cfa39c 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 9c658492ee 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 1cabc9f329 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 55d96c2a03 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new f4074bc760 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new a8c5ce52e9 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new fc9700f9e9 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 2f16263374 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 7fe49319a9 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new ac446c530a 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new b701d58ecb 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 51333b273c 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 62232b6b96 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 30062a7df7 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 69a291db01 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 8cd2cc95e9 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new c87d268ce1 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 6dc3a5b5cd 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new e7c265cd2b 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new b76b9302ef 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 7487770475 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 30d725feb8 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 5d9320b638 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 44e5561b79 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 78a7505de0 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 54332991dd 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new b292ccf68a 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 8ec9b69f49 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new ef69b1e877 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 5aed35bbe9 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 8c1e4a2c07 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 7f80c6410e 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new ad373358f7 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 22ff052d58 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 6aaac95d75 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new f5240d25fc 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 7774313e75 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new f53d08fc9f 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 530645e658 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new fac2924b41 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 90c9566351 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new 116d3fe3eb 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new bee82357f3 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 1f0790f264 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new 3beff4d0fb 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 37eca44d3f 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 32cc7e9e65 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 7791dd475f 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new c5209ca14d 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 79502b6335 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 02d0be41dd 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 758f50fcfb 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new dd98d195f8 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new c706f263db 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new aa7080656f 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 42311ba736 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new d8a3217ceb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new f9fa8741b3 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 4e184b2148 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 3a7a0333a7 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 264cacc7c9 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 8b0a1f803a 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 76189145d1 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 5bdd482691 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 83a7d53d90 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 50176d66c5 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 8a6cbf725e 127: force: #27: : Failure after baseline build: no new commits new 8c76baeeaa 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new e701647c23 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 6549ebf71c 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 3524dd5115 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new 052a4c9e9b 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 18369a36b2 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 7433b587e2 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new 5bcd4f83f2 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new f38ce83228 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 7fb2245e38 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 501fe83f52 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 5275088bcb 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 42ec2aa1c9 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new d41683eabe 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new f1cca621f2 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 2f4943f577 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 36a009052f 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 8f96538782 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 043e9beb07 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 917aa596c3 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new c03615ad6e 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new 7ffb462593 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 51ccd18365 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new b9e6374c37 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new c3060702fa 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new e6fc6a81f3 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 9055e6cddd 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new e1796ce778 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 8bcd6953a0 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new a0ee58aeb9 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 0fe6dd3048 158: onsuccess: #71: 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 (7a4d2f19a8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...]

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 2024 -> 2152 bytes 02-prepare_abe/console.log.xz | Bin 2404 -> 2460 bytes 03-build_abe-binutils/console.log.xz | Bin 35612 -> 35352 bytes 04-build_abe-gcc/console.log.xz | Bin 204032 -> 204884 bytes 06-build_abe-linux/console.log.xz | Bin 8660 -> 8728 bytes 07-build_abe-glibc/console.log.xz | Bin 242564 -> 244900 bytes 08-build_abe-gdb/console.log.xz | Bin 34936 -> 36284 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3324 -> 3412 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1196 -> 1196 bytes 11-check_regression/results.compare2 | 4 ++-- 12-update_baseline/console.log | 42 +++++++++++++++++----------------- git/gdb_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 17 +++++++------- sumfiles/gdb.log.xz | Bin 14432 -> 14440 bytes sumfiles/gdb.sum | 4 ++-- 18 files changed, 36 insertions(+), 37 deletions(-)