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 6bc65dd90c 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards 5678669e85 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 2f44b26765 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 1c6d6aeae3 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards bd535620a0 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 0a204afb37 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 02ea236da2 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards b1e57cc806 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 21e86c1867 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 06572b6958 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 0282f93911 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 99e6d1eb74 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 0dbb733d53 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards d5f29469f4 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards a7fcc141a2 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 39247226b4 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 779093c7fe 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 6d4173f8c8 127: force: #27: : Failure after baseline build: no new commits discards 6b200a12ce 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 842f7ea2f8 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 226ac45d25 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 414e9ca324 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 6512758a4d 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 3412018103 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 8e983767f7 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 1ef0886240 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 58086e1f9f 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 5d7da5cd73 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards fd96170f88 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards ed6dc80703 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 2260eccf7b 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 857235f932 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 1a4623d169 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 6844784267 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 4d40aeb455 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 57572f6418 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards ed7f729e89 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 8ae109a2d9 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards ee883a71a2 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards bc89355d5c 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 43aa7e422c 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards e3af45ea3d 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards a64940eae2 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 261f57ad85 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards dbe2897a6d 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 33b522e6ec 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 063761feb7 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 6b621df35e 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards bd6c874ee4 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 2c9dd84589 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 1ec878135b 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards b78d6c6f7a 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards a076ad6128 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 85626d74e3 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 58b6dbcd74 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards d9d2ebcb58 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards f084859afb 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards b1c0407717 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 14486496a4 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 85f822eddb 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 3985e49ee4 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards bce9c40756 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 5037a22158 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards c8a38a6e6f 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 5b5182cf6e 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 032922ed64 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards a9fe535090 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 2458094bb1 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 58dd13dd33 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards c651f493c6 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 75c2f503b0 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 9afcb6a015 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 9b63e580ec 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 0189bc0608 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards 560c659d27 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 59a68b04ee 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards dd223c8c80 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards bef5e67d85 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards ee4dc8e7c5 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 8915c99171 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 6649e29f6b 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 3dc701396b 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards b195e8e883 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 6bf1ffed86 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards d56639f634 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards a0b360d2c8 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards e963f0513b 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 4a17cc9811 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 48011546f8 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards d3d2ac1b39 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards 962327872e 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 299174342b 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards c6f1424336 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 808f4f4831 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] discards 5633829b83 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] discards ce39a08da0 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] discards 3461e3a911 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] discards e9b9b9beb3 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 8908922cac 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards a7a72a61a5 45: onsuccess: #56: 1: Success after binutils/gcc/linux/glib [...] discards fc7a81305b 44: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new 50a34bd892 44: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new be8159fc31 45: onsuccess: #56: 1: Success after binutils/gcc/linux/glib [...] new 8850723015 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new 0800476b2b 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new afcb4c6158 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] new b7bffcc15e 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] new abb4b80db2 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] new d5d539f922 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] new 43ee39e07b 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new e8ccb2b710 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 23a7dc3d57 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 2ffdf36830 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new df05fdca28 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 4669d8611b 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 2eb2a40494 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new b4df3618dc 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new bde592ce21 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 76792a8be8 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 22e9190697 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 3e89243709 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new aa29773a99 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 5709fe8795 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 85de96835e 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new ca070b2ff3 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 889bb65a07 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new dc7b24a9e3 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new e7de64e36b 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 7e9c86ceee 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 0ca14b229c 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 9cbadc128e 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new e56dd83baf 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 1cfea823a0 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new c208f3afb5 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new 74ebb74f8e 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new ba8272c7a1 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new a681e329f7 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new a97d62c3b4 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 8cb42fb21d 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 9ccf1dfcb3 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new ad4a02ea66 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 9224f00c68 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new a8b07c9ad2 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new c42ed735cb 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 9c6bba3866 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new da62282443 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new ba885ee6a4 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new c6dd73d33e 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new f21e755e95 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 6b7118e6a5 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 4fbb35ff88 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new b6fbd47bc1 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 7fc84f3e38 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 03376ad3c3 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 4709e5f6bd 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new c0aa971c96 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 19f3029f86 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 9e7a50e9c2 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new abaa76ac06 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new 71503d485b 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new 5157c1b6a9 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 1d1214ee64 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new 2970912bdf 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 132e224459 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new dc11217299 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 2619025d82 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 541e68ae24 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 77597d69a2 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 1e96a768c4 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new b2e7d27ca2 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new f24e525e91 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 68f10bf3ef 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new e2ac913eb5 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new fc9145c01c 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new ac0951e884 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 9b68c3d43d 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new bf5abb2d2a 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new a52796888e 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 8daaf7697d 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new f55fa99a93 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 5ae3786656 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 6ea938e3cb 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new cc9f029cc5 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 71ab5874cf 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 9030b6e87e 127: force: #27: : Failure after baseline build: no new commits new 598116a9c4 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 02a08c07fc 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 11e82b9386 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 7e84030f04 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new ae9e87a4ff 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 9b26ec26a4 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 50966c6549 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new bfa4d67e6f 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new f3dce5992c 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 6433d1e893 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 4927b0cb94 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new ba5ca0bf7d 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new eb419a3826 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 5e970fb746 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 0711594577 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new da6076f98f 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 925e075ada 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 17ab5f46f5 145: onsuccess: #50: 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 (6bc65dd90c) \ 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 -> 2084 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 34988 -> 35148 bytes 04-build_abe-gcc/console.log.xz | Bin 204344 -> 203728 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9500 -> 8508 bytes 07-build_abe-glibc/console.log.xz | Bin 241104 -> 241192 bytes 08-build_abe-gdb/console.log.xz | Bin 34832 -> 34788 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3776 -> 3876 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2840 -> 2912 bytes 11-check_regression/console.log.xz | Bin 5176 -> 5004 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 | 60 +++++++++++++++++----------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++++----------- manifest.sh | 38 ++++++++++----------- sumfiles/gdb.log.xz | Bin 14620 -> 14428 bytes sumfiles/gdb.sum | 4 +-- 26 files changed, 99 insertions(+), 99 deletions(-)