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 17ab5f46f5 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 925e075ada 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards da6076f98f 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 0711594577 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 5e970fb746 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards eb419a3826 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards ba5ca0bf7d 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 4927b0cb94 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 6433d1e893 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards f3dce5992c 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards bfa4d67e6f 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 50966c6549 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 9b26ec26a4 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards ae9e87a4ff 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 7e84030f04 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards 11e82b9386 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 02a08c07fc 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 598116a9c4 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 9030b6e87e 127: force: #27: : Failure after baseline build: no new commits discards 71ab5874cf 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards cc9f029cc5 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 6ea938e3cb 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 5ae3786656 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards f55fa99a93 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 8daaf7697d 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards a52796888e 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards bf5abb2d2a 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 9b68c3d43d 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards ac0951e884 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards fc9145c01c 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards e2ac913eb5 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 68f10bf3ef 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards f24e525e91 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards b2e7d27ca2 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 1e96a768c4 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 77597d69a2 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 541e68ae24 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 2619025d82 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards dc11217299 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 132e224459 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards 2970912bdf 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 1d1214ee64 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards 5157c1b6a9 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards 71503d485b 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards abaa76ac06 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 9e7a50e9c2 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 19f3029f86 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards c0aa971c96 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 4709e5f6bd 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 03376ad3c3 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 7fc84f3e38 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards b6fbd47bc1 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 4fbb35ff88 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 6b7118e6a5 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards f21e755e95 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards c6dd73d33e 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards ba885ee6a4 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards da62282443 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 9c6bba3866 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards c42ed735cb 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards a8b07c9ad2 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 9224f00c68 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards ad4a02ea66 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 9ccf1dfcb3 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 8cb42fb21d 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards a97d62c3b4 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards a681e329f7 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards ba8272c7a1 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 74ebb74f8e 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards c208f3afb5 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 1cfea823a0 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards e56dd83baf 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 9cbadc128e 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 0ca14b229c 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 7e9c86ceee 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards e7de64e36b 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards dc7b24a9e3 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 889bb65a07 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards ca070b2ff3 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 85de96835e 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 5709fe8795 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards aa29773a99 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 3e89243709 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 22e9190697 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 76792a8be8 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards bde592ce21 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards b4df3618dc 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards 2eb2a40494 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 4669d8611b 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards df05fdca28 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 2ffdf36830 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards 23a7dc3d57 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards e8ccb2b710 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 43ee39e07b 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards d5d539f922 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] discards abb4b80db2 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] discards b7bffcc15e 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] discards afcb4c6158 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] discards 0800476b2b 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 8850723015 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards be8159fc31 45: onsuccess: #56: 1: Success after binutils/gcc/linux/glib [...] new 447c10d14d 45: onsuccess: #56: 1: Success after binutils/gcc/linux/glib [...] new 4d65385ba7 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new c613ad6ffc 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new dc55969291 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] new 83df806a9a 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] new 7d911abefb 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] new e5479eae51 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] new 0fc8b5607d 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 57d598ebc9 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 7fa7271a3c 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new b3f0ee5616 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 362fd5561c 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new d3513430b1 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 1845273ce9 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new e7239cfdae 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new f57b443eaf 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 6239e0cfc4 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new ed704c6f86 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 4ceae63b29 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 30e1009cbb 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 1fad4c5ca1 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new ec04d2c941 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new fe7979accf 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 33e4323442 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 5f62c676f4 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new e61719fae9 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 200e580e2d 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new c108542dfa 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 5611e866f2 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 23cc9e1011 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 0991943234 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 245d691259 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new bdd8590177 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new bdddc5ff4d 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 928575713c 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 810f6e4520 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 69e5d63999 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 31486a75e3 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 667793cc44 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 5fd4693057 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 26c437f54f 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 4ad014dab5 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 8acb79c455 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 57811ef6d6 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 9ad85f958c 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 4d1ffe4792 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 90c2002768 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 4584f26d93 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 8e312c0aa5 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 6c8d4f5a81 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 32d39a1a46 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 85631e8583 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 91ca193c4d 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new b54d80d0c4 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 3ac0c1da17 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new d43123a17d 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 3eb08ae939 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new b25a6a40cd 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new f71169d0fa 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new c9c8652f20 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new ade5d563dd 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 6eae76e4fd 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 4efe044a9a 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new da79e0289f 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 2c2469a75d 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new abd10a4897 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new deb64551ea 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 88d4cddf1a 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 86438d9ab0 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 240157d3d0 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new d17be42640 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 852cd1d390 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new ce0e48c15a 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 711559ca7f 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 6377324453 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new f90d1315ae 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 6147955549 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 1a9e5937f7 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new a44c15ec02 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new dd3915249e 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 752fdc89aa 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 3b58adac4a 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new acd7d0a297 127: force: #27: : Failure after baseline build: no new commits new b87b6ef87b 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 660674b871 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 45693d1992 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 4910d938d9 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new 48190697c6 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 575bc195ea 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 5aaf1f4b0b 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new 9e6a971f18 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new efe11b3422 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 368322c120 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 588c71e391 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new f79e4debac 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new d54ab36920 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new eaa715bd66 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 2ea7e8ecf8 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new a571932d6a 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 4b7e4cdf1e 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new c5521171e6 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new fd93ac119d 146: onsuccess: #51: 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 (17ab5f46f5) \ 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 2084 -> 2056 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 35148 -> 35064 bytes 04-build_abe-gcc/console.log.xz | Bin 203728 -> 203288 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8508 -> 9068 bytes 07-build_abe-glibc/console.log.xz | Bin 241192 -> 241080 bytes 08-build_abe-gdb/console.log.xz | Bin 34788 -> 34744 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3884 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2912 -> 2824 bytes 11-check_regression/console.log.xz | Bin 5004 -> 4932 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 34 ++++++++++----------- 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/changes-list-long.txt | 56 ++++++++++++++++------------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 +++++++++++------------ manifest.sh | 36 +++++++++++----------- sumfiles/gdb.log.xz | Bin 14428 -> 14436 bytes sumfiles/gdb.sum | 4 +-- 26 files changed, 94 insertions(+), 98 deletions(-)