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 18a1c0b44e3 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards bf5fe9e7daa 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards a1d97a3e7ba 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 19e4a6b33c6 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] discards c92a4da488d 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards 70ba82c0aac 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 239800b4ae9 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards d4aef146ab7 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 0a9464910a4 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards e5a38d0fb6e 121: force: #26: : Failure after baseline build: no new commits discards 0bda7606cca 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 7bd0f20d683 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards c883dac57b4 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards aa6fe3db6f4 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 9a6ab17e192 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 5536e33ead3 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards f3850d21d91 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 9c93d30d90c 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 2738057983f 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 9f97e98843b 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 62355fe431c 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a3e3b4c0170 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards b83720ed557 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards cf5c4162892 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 3488504744c 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 0b5967f6615 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 201782c0d64 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 886e960b5f8 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 8dd9557d451 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 851302c3521 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 9e5a63feda6 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards c007aae7fcc 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards f2c4f085d20 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards e9dd6953170 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards 24d27fb6ce4 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 7934eb6a205 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards c8d0c8f8148 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 29d77b2e378 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 0cc6122638b 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 288686ff9c4 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 59d012a87d7 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 19b234b2fd8 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 0ba70d3acb9 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 224bf700c14 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 632f664117c 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards d625f53fb55 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 67360f4c159 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 2c8014090ae 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 8228d42ca60 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards a3586ac6190 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 0073342f420 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards ec7396083f9 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 1645c3bc379 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 27d3bd12db4 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 6e8cd800548 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards fb158c40fa0 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards f1c38995df4 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards e2ae7e671a7 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards a52cf8fd98f 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 0420fcdc3f4 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards c7225ac8dcd 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 93799149a71 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 0677da0fcbd 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards fc6a03be23a 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 2010f7f0dab 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards ba83df4879c 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards e3fc2d49d38 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 6e509b99d1c 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 7caa6e901b4 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 9d8523a74d0 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 4da3667b7a1 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 243a1d38c1b 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 3d868769817 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 985a83686ec 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 97dfd458cb6 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 53a651350a6 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 06e358258da 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards b172de582ca 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 3f8a626cf4a 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 954e84eda23 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 21f8b0773ce 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 18b7732277b 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 33999877020 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 9ed345e7bf2 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 1cbc568b4d3 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 762b86593f2 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards c3278c7b316 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 87a25d88d34 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards b453c2995a7 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards f1d470897cd 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 5fda655ee88 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards 3baad45a799 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 73ae1b4e7f4 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 4a75b1d860d 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 26553265b8a 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 7e18cc7a993 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards fbe4c2d9f87 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 1e0ef6994ec 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 0f27c978ac1 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 4fe8d0ae705 31: onsuccess: #38: 1: Success after linux: 14 commits discards d8013488c2f 30: onsuccess: #36: 1: Success after binutils: 18 commits new 231cefe48e4 30: onsuccess: #36: 1: Success after binutils: 18 commits new 82818de69cf 31: onsuccess: #38: 1: Success after linux: 14 commits new 0b43e433e02 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new f9d9d7544d5 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 055c7bdcf2c 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 9b2d4ae25d2 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 5a1374b2455 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new c377413b353 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 8e0c12a4f9d 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new c096e5f04a5 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 3302a9b1ca9 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 661decd8c74 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 2b7e9102ff2 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new b1f864c0939 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 43c6cc68b74 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new bb122ffe110 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 46304be2a48 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 08ec21b8cdf 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 4978299584b 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new d03c3a3d64d 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new a586b6a7c1b 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new e2167028ea9 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new dc47058663e 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new fe122f93653 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new e3bd3de71da 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 9a3294bec35 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 7991d914d45 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 87ed52aa4f2 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 7c04df0347a 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 3e7c7f08623 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 1950dc22a18 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new effd588c80e 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 06339428b13 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 475e053f47a 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new a75808e067b 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 72c283d4bf5 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 30355328e44 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 125d55919de 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new c5d8712bbda 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new a86c6dee708 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 84a553107fe 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 6f852a1e2de 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 5f4bd08221e 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new b39f21eb0f0 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 2985bc11459 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new e192ee60281 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 98315b1f4e7 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 63f504de5b6 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 766006296cb 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 316039bfb2c 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 3dd53f0ae5c 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 753a0a22aa9 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 2f19d5eef8d 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 85a0cb0bc5f 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 29de1b0d680 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 98c2fd58bcb 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 942acd838fc 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new df1d79cd74f 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 3bc324dfdaf 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 34d6f3b1365 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new c63caa13d4d 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new ae001d0f266 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new b8c1c43e9f9 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 0e0c69ef1e0 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new f9484783012 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 915b3da164c 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new 57cf6c5c512 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 1e5f6f920a7 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 457dccf59e1 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 157647e71e3 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new c3a7e8e72c0 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 6fc3a2c3cc5 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 4d8b53c6aa9 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new a5257db7559 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 9bc65a9e2b3 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 955fe62214f 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new f7d70113383 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new d35299b8155 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 4fbe4186c07 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 2e63262bb9e 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 335255acbb9 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 469233c8d93 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new ac65c509fcb 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 3e0f808ce68 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new a2eb30f504f 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 67907a82a4d 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new ac88dc028a3 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 73583a00bd6 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 44cb068010d 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 07eaba07a61 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new bdeacf83496 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new ac0a62f3723 121: force: #26: : Failure after baseline build: no new commits new 7cd17810b98 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 2d1fd746d13 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 8276ab3d7f9 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 363a035607d 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new b1393e358df 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new 8464d592922 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] new 9d960cea1bb 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new 28878b87fd0 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new cfd62d8c456 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new f64c901f4c3 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...]

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 (18a1c0b44e3) \ 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 2060 -> 2040 bytes 02-prepare_abe/console.log.xz | Bin 2540 -> 2576 bytes 03-build_abe-binutils/console.log.xz | Bin 48976 -> 49244 bytes 04-build_abe-gcc/console.log.xz | Bin 237032 -> 235312 bytes 06-build_abe-linux/console.log.xz | Bin 8508 -> 9064 bytes 07-build_abe-glibc/console.log.xz | Bin 232960 -> 232684 bytes 08-build_abe-gdb/console.log.xz | Bin 46468 -> 47160 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3796 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2672 -> 3072 bytes 11-check_regression/console.log.xz | Bin 4468 -> 4452 bytes 11-check_regression/results.compare2 | 4 ++-- 12-update_baseline/console.log | 38 +++++++++++++++++----------------- 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/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++++++++++++++++---------------- sumfiles/gdb.log.xz | Bin 14472 -> 14456 bytes sumfiles/gdb.sum | 4 ++-- 23 files changed, 49 insertions(+), 49 deletions(-)