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 54955ccb3f7 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gl [...] discards 59e6dffdbde 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gd [...] discards 579bf51beda 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards ffe8aac3cb7 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 8206be55e41 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gl [...] discards ea54621a601 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards d59cefc8443 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards a85c04dbb65 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 3bc1e4d5c6f 127: force: #27: : Failure after baseline build: no new commits discards 66f54e5e8a3 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 83181454610 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards b631558e420 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 19c3b081bce 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards eedb95ec3f6 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards a4080dc92d3 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 65f6a225df6 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards d0611ce7f15 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 3db78a06129 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 7fe366b30a7 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 649b2a6d59d 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 4d7aceb7e9d 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 43a38cf9639 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 158b148278b 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards a99d1ba5013 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 2aac504853d 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 97e33459ed0 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 48a1ee09bd4 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 3e5ea2b28c8 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 302748b7971 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e6e5c8478fa 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards c55415a1020 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 4fdea68cb00 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards e604f09d28d 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards 5e4b4d791e0 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards c275eac6135 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards 24ffe8d1540 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards 1156ea0a3bb 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards 4a9bd653a3c 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards 30acd4e1820 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards 1fc09f9cded 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards 80cf6db92e5 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards fa332402fc3 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards ef4b8c55303 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 478e19755d4 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards 0c1e52bc512 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards cbfc34f21ef 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 8aeaacd3f3a 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards 6dc3d0e014e 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 1957feeea46 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards a9ccbca1a32 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards df64d47f86d 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards dbd5ea53691 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 7e3a61116b1 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 8692cff91c7 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards 76e2d6833db 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 8dfe94e2c37 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards d07768cf324 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards b79c6ff804c 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards def66ec8900 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards 7dc5c8d136f 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards 6eb50a9cf61 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards 8ff33eb12a1 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 57381f64834 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 0defb7a9366 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards e655faf2187 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards 21a9a6e76c9 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards 5b266fe2a69 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 6e0eba2c93c 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards e4da660a61f 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 8724458290f 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards 94b47fddd4e 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards 5fd204b2e7b 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards 1d7bac9cd33 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards af99b6e33c3 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards a63af07a76c 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards 8f5b31f0b6e 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards 462ac882a08 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards d296ced5e85 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 4dd93c2f11b 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 32b1b647aa1 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 861cc7b26ce 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards b54b18c9ace 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 1b2d4f2ff98 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards cf5a62d0253 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards f613e1d9803 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards b45ea336fb0 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards b5aad7a75f1 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards 25bfe7ac98f 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards 4773e6cef9f 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 8278d8b9568 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 14f49d2c77d 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards 3207acaf125 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 49ab6480b85 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 2984c680c0e 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 6ee7038111c 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 3efcc8e43a7 40: onsuccess: #49: 1: Success after linux: 219 commits discards 7fc6e21345e 39: onsuccess: #48: 1: Success after glibc: 2 commits discards cb5cb79d8c2 38: onsuccess: #46: 1: Success after binutils: 26 commits discards 2ba92a7fcc6 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards da658c1a8b0 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 7f72447fa70 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 00318e9f4cd 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 04300f4becf 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new a2b99a4dac9 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 8d3b184c4fe 38: onsuccess: #46: 1: Success after binutils: 26 commits new e9ac21c35c2 39: onsuccess: #48: 1: Success after glibc: 2 commits new 9953469d6d9 40: onsuccess: #49: 1: Success after linux: 219 commits new a27f6ac5ad4 41: onsuccess: #51: 1: Success after binutils: 12 commits new d8a8dbedd6c 42: onsuccess: #53: 1: Success after linux: 3008 commits new 0783c8a5e0b 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new c82e2d7d6aa 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 4c8b4e1428b 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new e98a2809c30 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 1d25e828d0e 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 8098cd653a6 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new bb25361188a 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new 4d5c4cba527 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new 46479b0a959 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new 03b7fdb9990 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 73727850868 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new fbfb779d5c0 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 07c2f2bdf21 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new 3c40c72af31 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 5a0cdcd97d3 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new c035bd618cc 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new a6ed2fc9893 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new aeee0741b11 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new e7d9276cc94 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 945a8e8e5ca 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new 7ffbd70114d 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 949e35d320b 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new 25552e1bc76 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new f4a5a98e1b6 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new 6ede976fe9e 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new a6b5089c651 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new 83ff95001f9 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 24abec1767e 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new b3625a3ed14 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new e79bfde3f2e 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new 1054137f69a 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new c45dce4fcc9 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new cf0a4ea8dc8 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new 98af8664cb1 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new 2583bb7391d 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new 0f210ccbfb6 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 9b62b3aa3f6 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 51ff4223c0e 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 20ac2c3d556 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new b62a51b4622 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new 5cf8d59ff37 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 4f4b91d3cfb 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new fd4eda80156 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new d526a7a706e 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new d92cfc3c326 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 60da04e83b1 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 5afa91fa35f 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new bf2484fe134 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new f9c514a5030 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 9853b0ac207 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new ea8802d6005 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new fdbc75325d5 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 541db7f7f8e 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new 2941bff4c36 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new e9458c4265c 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new dcc5c460b4d 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new 38476735cf9 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new c3e703bfe26 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new 417cdc36efc 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new 0f821f416bb 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new 4aecfeb489b 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new 1b38871b7ad 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new 440dc8e0944 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new ae0c0d92cf0 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new 13b3aa5e867 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new b1a7fdf121a 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new beca89f944c 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 0fbd8a4a2a5 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new f10afd8ea94 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 2a698ea02f7 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new d7b228d65ec 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 5fde1ae3ea1 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 307171f5c7e 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 95692aaf623 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new df0865e0beb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 96b6cfbf498 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 3676781b106 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 72024347c12 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 4d8fc27c9ec 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 536cbfee095 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 4df1cd1cf62 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 962d68c9ee8 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 1e36aa84273 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 2ab325e084d 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 8bd066596cd 127: force: #27: : Failure after baseline build: no new commits new 5cc1c760a3e 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 5ce6a48ae55 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new ccf90c9e2d8 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 275a9a038bd 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gl [...] new e352a6a71e4 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 92c9b82b76a 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new a6c6e41dbdd 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gd [...] new c1db9fcd211 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gl [...] new 6da2ef63c1e 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...]

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 (54955ccb3f7) \ 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 2016 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 35352 -> 35064 bytes 04-build_abe-gcc/console.log.xz | Bin 203872 -> 204092 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8176 -> 8576 bytes 07-build_abe-glibc/console.log.xz | Bin 241448 -> 240948 bytes 08-build_abe-gdb/console.log.xz | Bin 34780 -> 34844 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3840 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3068 -> 2716 bytes 11-check_regression/console.log.xz | Bin 4660 -> 5100 bytes 11-check_regression/mail-body.txt | 35 ------------------- 11-check_regression/mail-subject.txt | 1 - 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 62 +++++++++++++++++----------------- 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 | 32 ++++++++++++++++++ mail/changes-list-short.txt | 1 + mail/mail-body.txt | 35 ------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 38 ++++++++++----------- sumfiles/gdb.log.xz | Bin 14652 -> 14644 bytes sumfiles/gdb.sum | 4 +-- 30 files changed, 97 insertions(+), 135 deletions(-) delete mode 100644 11-check_regression/mail-body.txt delete mode 100644 11-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt