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-arm in repository toolchain/ci/base-artifacts.
discards 901fd9a0bdd 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards c44be7a07cf 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards ab5087d96ef 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] discards b48b813ea36 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards aecc8000b46 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards ecfcd7d8fb4 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 858c50116cb 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 31d0f742e14 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards f7a55088645 121: force: #26: : Failure after baseline build: no new commits discards eb1aa109345 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards bcbc831b479 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 1c68a47b501 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 6cc15afb343 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 926e2fb8716 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 6c351e85381 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards a12d42e5057 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 305b38d4e26 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 65a80cd26f8 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards efd35a73f8e 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 7f755b711bd 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 53e6f5b2287 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 1ce478081be 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 5996746087c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 09c9244cab2 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 26f094cbf66 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 7e5245dee44 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards c8b5391fc17 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards c848be235f6 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 592b40ae6f5 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 6e4f14ff090 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 3eded8240be 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards d80e55aeba3 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards ec6dd6402cd 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards e793127ed58 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards d9c531247f4 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards e9f51367d3f 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 235603842d2 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards c36e20a12f5 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 9e1e55c45b5 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards abdd9a7466f 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 223bcc98e00 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 948f34ec191 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards e3041d454eb 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards db63d2ccc34 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 5ed93b6b5a2 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 5311b3f6cf0 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 2d03af9b4f4 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards b1b7e453ab2 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 11bf85fb6f2 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards ec87ca43542 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 4c5442aea82 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 759e8a663d2 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards d813bb1b809 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards caaec1366a5 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards f7a78ac200a 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards c91dbb8e5fa 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 91e065d0986 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 7d51dfc5e7e 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards a5827e1d75f 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards a9b5ab545c7 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards c8f58499c42 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 6ca66fcb263 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 971d8d0c0a3 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 2cbc897ef72 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards fcebec6752d 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 9dba788fe77 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards b044735b594 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 5e0bf5e7e99 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 3c1a2ff7b5e 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards e0a884065f6 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 2dc83b8b878 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 67630247210 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards c7d818ca081 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards df76d0bb720 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards e928022507a 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 3ed11cf5afb 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 1de56612bf8 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards c18028ee2e2 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards ac018208eb3 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 79eac3e07b8 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 060508a3798 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 6f3e943e995 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 66583623cbd 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 4a44f230d42 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 62891e113dd 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards db0693d050a 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 0cb2e5db611 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 796f67194e1 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 8841c4df4d7 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 068807d348d 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards bbd2182dbb5 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 1a060dd4885 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards b502168c5e5 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 9d3303d9fab 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards e91ae6a326a 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards b1837702cbc 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 80bff201de8 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 6fdd9cb2a68 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 0cd2e4f4372 31: onsuccess: #38: 1: Success after linux: 14 commits discards c872b31e784 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 83bc2bf650a 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 2fe0bc45bd7 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new d8013488c2f 30: onsuccess: #36: 1: Success after binutils: 18 commits new 4fe8d0ae705 31: onsuccess: #38: 1: Success after linux: 14 commits new 0f27c978ac1 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 1e0ef6994ec 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new fbe4c2d9f87 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 7e18cc7a993 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 26553265b8a 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 4a75b1d860d 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 73ae1b4e7f4 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new 3baad45a799 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 5fda655ee88 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new f1d470897cd 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new b453c2995a7 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 87a25d88d34 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new c3278c7b316 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 762b86593f2 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 1cbc568b4d3 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 9ed345e7bf2 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 33999877020 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 18b7732277b 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new 21f8b0773ce 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 954e84eda23 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 3f8a626cf4a 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new b172de582ca 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 06e358258da 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 53a651350a6 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 97dfd458cb6 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 985a83686ec 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 3d868769817 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 243a1d38c1b 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 4da3667b7a1 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 9d8523a74d0 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 7caa6e901b4 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 6e509b99d1c 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new e3fc2d49d38 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new ba83df4879c 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 2010f7f0dab 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new fc6a03be23a 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 0677da0fcbd 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 93799149a71 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new c7225ac8dcd 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 0420fcdc3f4 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new a52cf8fd98f 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new e2ae7e671a7 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new f1c38995df4 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new fb158c40fa0 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 6e8cd800548 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 27d3bd12db4 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 1645c3bc379 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new ec7396083f9 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 0073342f420 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new a3586ac6190 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 8228d42ca60 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 2c8014090ae 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 67360f4c159 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new d625f53fb55 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 632f664117c 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 224bf700c14 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 0ba70d3acb9 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 19b234b2fd8 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 59d012a87d7 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 288686ff9c4 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 0cc6122638b 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 29d77b2e378 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new c8d0c8f8148 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 7934eb6a205 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new 24d27fb6ce4 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new e9dd6953170 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new f2c4f085d20 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new c007aae7fcc 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 9e5a63feda6 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 851302c3521 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 8dd9557d451 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new 886e960b5f8 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 201782c0d64 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 0b5967f6615 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 3488504744c 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new cf5c4162892 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new b83720ed557 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new a3e3b4c0170 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 62355fe431c 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 9f97e98843b 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 2738057983f 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 9c93d30d90c 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new f3850d21d91 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 5536e33ead3 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 9a6ab17e192 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new aa6fe3db6f4 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new c883dac57b4 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 7bd0f20d683 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 0bda7606cca 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e5a38d0fb6e 121: force: #26: : Failure after baseline build: no new commits new 0a9464910a4 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new d4aef146ab7 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 239800b4ae9 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 70ba82c0aac 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new c92a4da488d 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new 19e4a6b33c6 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] new a1d97a3e7ba 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new bf5fe9e7daa 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 18a1c0b44e3 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...]
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 (901fd9a0bdd) \ 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 -> 2060 bytes 02-prepare_abe/console.log.xz | Bin 2568 -> 2540 bytes 03-build_abe-binutils/console.log.xz | Bin 49288 -> 48976 bytes 04-build_abe-gcc/console.log.xz | Bin 238024 -> 237032 bytes 06-build_abe-linux/console.log.xz | Bin 8452 -> 8508 bytes 07-build_abe-glibc/console.log.xz | Bin 233736 -> 232960 bytes 08-build_abe-gdb/console.log.xz | Bin 47124 -> 46468 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3768 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2836 -> 2672 bytes 11-check_regression/console.log.xz | Bin 4708 -> 4468 bytes 11-check_regression/results.compare2 | 4 ++-- 12-update_baseline/console.log | 32 ++++++++++++++++---------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 14464 -> 14472 bytes sumfiles/gdb.sum | 4 ++-- 22 files changed, 44 insertions(+), 44 deletions(-)