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 fd93ac119d 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards c5521171e6 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 4b7e4cdf1e 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards a571932d6a 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 2ea7e8ecf8 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards eaa715bd66 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards d54ab36920 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards f79e4debac 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 588c71e391 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 368322c120 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards efe11b3422 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 9e6a971f18 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 5aaf1f4b0b 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 575bc195ea 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 48190697c6 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 4910d938d9 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards 45693d1992 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 660674b871 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards b87b6ef87b 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards acd7d0a297 127: force: #27: : Failure after baseline build: no new commits discards 3b58adac4a 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 752fdc89aa 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards dd3915249e 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards a44c15ec02 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 1a9e5937f7 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 6147955549 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards f90d1315ae 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 6377324453 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 711559ca7f 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards ce0e48c15a 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 852cd1d390 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards d17be42640 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 240157d3d0 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 86438d9ab0 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 88d4cddf1a 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards deb64551ea 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards abd10a4897 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 2c2469a75d 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards da79e0289f 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 4efe044a9a 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 6eae76e4fd 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards ade5d563dd 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards c9c8652f20 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards f71169d0fa 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards b25a6a40cd 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 3eb08ae939 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards d43123a17d 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 3ac0c1da17 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards b54d80d0c4 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 91ca193c4d 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 85631e8583 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 32d39a1a46 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 6c8d4f5a81 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 8e312c0aa5 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 4584f26d93 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 90c2002768 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 4d1ffe4792 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 9ad85f958c 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards 57811ef6d6 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 8acb79c455 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 4ad014dab5 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 26c437f54f 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 5fd4693057 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 667793cc44 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 31486a75e3 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 69e5d63999 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 810f6e4520 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 928575713c 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards bdddc5ff4d 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards bdd8590177 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 245d691259 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 0991943234 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 23cc9e1011 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 5611e866f2 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards c108542dfa 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 200e580e2d 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards e61719fae9 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 5f62c676f4 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 33e4323442 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards fe7979accf 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards ec04d2c941 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 1fad4c5ca1 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 30e1009cbb 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 4ceae63b29 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards ed704c6f86 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 6239e0cfc4 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards f57b443eaf 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards e7239cfdae 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards 1845273ce9 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards d3513430b1 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 362fd5561c 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards b3f0ee5616 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards 7fa7271a3c 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 57d598ebc9 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 0fc8b5607d 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards e5479eae51 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] discards 7d911abefb 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] discards 83df806a9a 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] discards dc55969291 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] discards c613ad6ffc 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 4d65385ba7 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new aa7a9e1983 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new b58dfa6f6d 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new efc52cebce 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] new afb8952a7c 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] new 089fb2080c 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] new 055c874da5 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] new 74cbd3e542 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new fcebfd7f60 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 998f2e676d 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new eb3a8a6007 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 7a0966c5ad 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 54539a588e 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 578ae7dc87 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 4913567191 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 64358b3321 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 4de88b9405 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 8fb426b66d 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new dcdeee1157 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new f73899f782 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 32d8cd1373 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 75a26096ee 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 43e19e7736 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 093eb58153 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 950b7c676c 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new d1c200ad80 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 6f25e6cb88 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new c449a3d21e 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new c9180bcf7d 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new b2986057a8 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new b918bd0965 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new c136aeb180 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new d4f8db3922 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 343915106a 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 9cd3f9e8cc 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 3bdc3788be 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new d07755eff2 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new c8cb82ca42 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new eb55c8c77d 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new f0a7997861 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 6a831dacf1 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 844de0884c 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 7e2ae585b4 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new f18ede61fe 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 7b0a84abf4 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 577e7e63b5 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new a31c1a357a 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 54870bbdcd 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 7a9f8a5323 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 73cee8d33c 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new dc9bfbeb5e 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 7d4707254f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 3461166fbb 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 97cbd48961 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 33d012efe6 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 74214a0c54 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 3ecb29b49f 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new 3df332c325 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new 70928215fc 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 3996a2afea 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new d34e48e649 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 780832a5aa 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 2915881155 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new caae57f7d2 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 772bcf7270 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 7b7c4ba465 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 653dea9417 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new d42a0f4397 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new c8a4d4dd04 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new fe10f3e9ff 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 9822692796 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 13b92b3888 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 4b507043bb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 8bbbb6385c 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new def059a9b8 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new aa088dca85 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 924ced55ef 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new cd8c1ee39d 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 95f2c477a9 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 51973fa128 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 95653fb8fc 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 2e860750e0 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new ef02e5bf45 127: force: #27: : Failure after baseline build: no new commits new b5a0964311 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 9a5165c516 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new c3d47369e5 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new abdf1c725e 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new efd0d89eb6 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 1b84f9165d 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 18f3ef58b1 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new bd66919db1 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new fc9c195549 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 280a3073c7 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 61f4c7ebd7 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 6ad8870916 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 3c29c80ef5 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new ce0630fe05 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 83943cd771 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new f2c92f2cdc 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new bedeff33ff 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 87857b970b 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new fcb30fef79 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 1245520270 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...]
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 (fd93ac119d) \ 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 2056 -> 2088 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2540 bytes 03-build_abe-binutils/console.log.xz | Bin 35064 -> 35084 bytes 04-build_abe-gcc/console.log.xz | Bin 203288 -> 203964 bytes 06-build_abe-linux/console.log.xz | Bin 9068 -> 8316 bytes 07-build_abe-glibc/console.log.xz | Bin 241080 -> 241756 bytes 08-build_abe-gdb/console.log.xz | Bin 34744 -> 34836 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2824 -> 2800 bytes 11-check_regression/console.log.xz | Bin 4932 -> 4168 bytes 11-check_regression/results.compare2 | 4 ++-- 12-update_baseline/console.log | 40 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 38 ++++++++++---------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 +++++++++++++++--------------- manifest.sh | 32 +++++++++++++-------------- sumfiles/gdb.log.xz | Bin 14436 -> 14440 bytes sumfiles/gdb.sum | 4 ++-- 23 files changed, 75 insertions(+), 91 deletions(-)