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 86e31f073d 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 2e176a9d79 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards e86812fba1 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 3cf0e058d3 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 2cb29b1f0f 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 551b652fcc 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 5ba4640dea 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards b0f6e7eec3 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 26ddbf3956 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 7272169185 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 558b6bd901 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 311c5c5134 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 73dae855d6 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards bcdf1dc159 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 52e6d67f0f 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 130d47d6bd 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 6b03ee4c66 127: force: #27: : Failure after baseline build: no new commits discards 2eaba67fc2 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards deee2ce611 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 23812b20de 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards e26c1f3d95 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards b6313b153e 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards a4dfd2ca3a 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards e0a7557c97 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 3ca0f6f5f9 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 6d06775f20 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards cb7fcb708e 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards c4ce5cfcbc 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards b4ee6044e9 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 957cd3a0ef 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 001bf4e86a 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards a0f63d707b 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 7375c7b5b7 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 7d6e7ad049 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 5894f61883 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards af13217cfa 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 813335c379 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 7476310dfd 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards 67055c7fe3 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards dda73bbbdf 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards 59a1c86501 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards e890042138 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 7f6b8a671e 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards cdb78be664 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 032a23def6 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 6ad05c3771 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 1f92df610f 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 5149facaa8 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards b125f326e1 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards c335bd605f 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 894cb39a0c 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards eb625901e6 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 333e0f5912 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 9a000ca5ff 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 9b80971431 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards 292b49b1b8 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards ec927c64af 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 525e0902aa 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards f320f9353f 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 3e81162f85 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 60d4c19f4b 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards af211af4a1 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 573d5e2120 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 954d94747a 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards b10d1fa591 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards db24291e2a 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 265cf009f2 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards d6fff489be 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards f98e3404ce 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards e49402a4c1 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 0b6ce11e8c 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards e8189ce47b 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 640e6d6ed4 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards 4b5bc342e7 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 101acb5a23 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 3fc9b07772 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards fc1f4727f6 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards fb726b4130 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards c481846ca4 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 7786339b96 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 386a2f2b9a 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 5f9bd41026 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 7fd06b41f2 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards b2a6debf06 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards 475a23eac1 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards ed1ae25f79 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 96df4680df 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards a60c661e9e 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 23997efe2f 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards 0e62253208 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards fa2451be83 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 27895151d7 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 511e8bda85 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] discards 97e373012e 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] discards 6a1fc34f12 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] discards 9aa063bb8b 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] discards 5f7ef4a568 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards c047bd7dd1 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards 4fe72bbea5 45: onsuccess: #56: 1: Success after binutils/gcc/linux/glib [...] discards 5f36a7f902 44: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards 717c24fb1e 43: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new f0cb8cea32 43: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new fc7a81305b 44: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new a7a72a61a5 45: onsuccess: #56: 1: Success after binutils/gcc/linux/glib [...] new 8908922cac 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new e9b9b9beb3 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 3461e3a911 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] new ce39a08da0 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] new 5633829b83 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] new 808f4f4831 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] new c6f1424336 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 299174342b 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 962327872e 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new d3d2ac1b39 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 48011546f8 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 4a17cc9811 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new e963f0513b 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new a0b360d2c8 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new d56639f634 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 6bf1ffed86 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new b195e8e883 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 3dc701396b 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 6649e29f6b 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 8915c99171 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new ee4dc8e7c5 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new bef5e67d85 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new dd223c8c80 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 59a68b04ee 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 560c659d27 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 0189bc0608 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 9b63e580ec 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 9afcb6a015 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 75c2f503b0 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new c651f493c6 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 58dd13dd33 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new 2458094bb1 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new a9fe535090 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 032922ed64 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 5b5182cf6e 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new c8a38a6e6f 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 5037a22158 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new bce9c40756 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 3985e49ee4 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 85f822eddb 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 14486496a4 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new b1c0407717 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new f084859afb 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new d9d2ebcb58 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 58b6dbcd74 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 85626d74e3 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new a076ad6128 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new b78d6c6f7a 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 1ec878135b 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 2c9dd84589 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new bd6c874ee4 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 6b621df35e 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 063761feb7 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 33b522e6ec 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new dbe2897a6d 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 261f57ad85 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new a64940eae2 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new e3af45ea3d 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 43aa7e422c 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new bc89355d5c 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new ee883a71a2 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 8ae109a2d9 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new ed7f729e89 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 57572f6418 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 4d40aeb455 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 6844784267 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 1a4623d169 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 857235f932 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 2260eccf7b 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new ed6dc80703 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new fd96170f88 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 5d7da5cd73 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 58086e1f9f 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 1ef0886240 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 8e983767f7 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 3412018103 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 6512758a4d 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 414e9ca324 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 226ac45d25 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 842f7ea2f8 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 6b200a12ce 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 6d4173f8c8 127: force: #27: : Failure after baseline build: no new commits new 779093c7fe 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 39247226b4 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new a7fcc141a2 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new d5f29469f4 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new 0dbb733d53 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 99e6d1eb74 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 0282f93911 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new 06572b6958 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new 21e86c1867 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new b1e57cc806 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 02ea236da2 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 0a204afb37 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new bd535620a0 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 1c6d6aeae3 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 2f44b26765 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 5678669e85 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 6bc65dd90c 144: onsuccess: #48: 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 (86e31f073d) \ 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 2032 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 35672 -> 34988 bytes 04-build_abe-gcc/console.log.xz | Bin 203200 -> 204344 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8724 -> 9500 bytes 07-build_abe-glibc/console.log.xz | Bin 241260 -> 241104 bytes 08-build_abe-gdb/console.log.xz | Bin 35036 -> 34832 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3776 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3320 -> 2840 bytes 11-check_regression/console.log.xz | Bin 4876 -> 5176 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 | 52 ++++++++++++++++++++-------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++++++------------- manifest.sh | 38 ++++++++++++------------- sumfiles/gdb.log.xz | Bin 14620 -> 14620 bytes sumfiles/gdb.sum | 4 +-- 26 files changed, 99 insertions(+), 91 deletions(-)