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 390112ff174 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gc [...] discards 331a2218435 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...] discards 0c2ae2a6c6f 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] discards 1aefa1f665f 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] discards 4d9794c4c90 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards 8ac56c77108 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 3f4f6906e9a 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards a1c2cd5caf6 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] discards 097e488279f 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards 3cca2620e00 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards bfd8de60c33 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 99b7cf2ae3f 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards f4d011201c7 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 1030d4792cf 121: force: #26: : Failure after baseline build: no new commits discards 610f311fb24 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards ca225985c46 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 84324bddbab 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 6e1e414ae5d 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 817152559b0 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 707e5295f66 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards e83a4528aca 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 9d061c36c6e 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards f3643e15d14 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 1bda8a0fc98 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 0a3553ca996 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 1dba6e56f94 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 89844d3060e 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 5e8f6591b5a 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards d1a871b2d36 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 74d50ca1088 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 2416d58de51 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards e42911c42a2 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 46e7ffcf26f 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 80f24429c26 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 9c325b27712 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 33f1b7a593f 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards a0a440b262f 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards da667ceecc0 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards d40e3acd169 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 57706eda5da 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 4ffffaf406c 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 6f344e4aa8c 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 67587602287 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 8c9e6a03168 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 44ad35548e1 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards fab54c118c2 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 1fe2bba32a0 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards b87b0c0213f 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 2f1acee0dff 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards f6468ca907b 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 4e84cb15ec8 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards ca0d51f1096 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards e8c54418763 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 95e18701034 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 9965a465fec 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 4ea796c03ee 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 00822fb3e93 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 07ad76c6383 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards c6818468565 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 04816d697b6 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 6465ccc6b45 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 9ffbd0cd255 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 5129c0a7e11 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards c681b93379c 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards c3ae8bae6c3 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards b2f42d2f7ec 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 97af98b5cd4 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 8edb37c7d78 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 9e63aae1a1b 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 46faf7ce9af 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards c4dbd150c42 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards b548fba4507 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 69793bd60f4 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards b748451ff45 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 37bec791a41 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards c5bab59edbd 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 481e9637d7f 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 88759fe0342 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 0976e535ffb 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 91cdaf15401 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards d8c9dacb006 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 5d4f0f97206 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards fbf53982965 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 0dc774965e3 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards b019579283b 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 4765257052a 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards a770e42874a 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 111493841e4 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 40ff1fdce38 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 4f7efe6d897 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 3fa5ad4a5bc 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 57bc5dccd42 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 51b586a8527 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 81f63ca427d 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 4b21fd7313a 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards fc8450000db 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 228b0c68d5c 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards fa8224aa1f2 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards a6c681d9c27 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 355989a38d9 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards c64cb16afb5 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 52130ec5145 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 377e5465ae0 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 189ecf89b5e 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new aeb786b7629 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 942439c95d8 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new 7f1f9145206 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 5923b0a5add 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 1ad59195c84 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new d309de0785c 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 6f272455ccf 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 4f57c42f95c 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new ec36a4de5aa 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 37a83bc31dc 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 1324e05e147 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 1dedcf05751 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new fcd99f09bf6 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new 6332d4805bf 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 59ec2509f9f 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new f5c57158621 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new ebafd8312db 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 7da9349ca66 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 8670e6efd63 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new bbf32614044 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 8909a96b487 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 8fb1829c839 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 225039253f2 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 44fe0c2f3ea 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 61068faec27 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 31e3ae4c25b 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new a4e2c7e9fec 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new aae1083b8ce 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 6ad3faf3fb2 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 67dbad02437 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 74225ec19e5 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 660f8429d71 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new c060b1080b2 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 3a41927f8ef 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 98e6a474637 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 35183e982c8 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 350cfecb6f1 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new ff42b7cd673 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new adb654e92b3 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new b0adefc4dfe 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new a60a2fd61a3 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 8008376acf0 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 4ae5505d1fd 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 918fa27347b 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 1ae520f8420 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 7659102c4de 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 17aa4ab4109 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new bef107ae224 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new d1d01691ca0 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 1de5ac1045a 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new a483a810444 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new be75d75e2a7 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 190c58b6d27 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 57e2775619e 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 94980f68b6c 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 077cdcd9b56 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 973e0f7caf5 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new f32125fd136 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 2794d96f315 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new 617b2999e3f 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 27ac92cb757 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 2653088bd97 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new ec0c4b00c52 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new e7bb52403fd 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 912238b29bb 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 61281c2d447 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new b33d3397df2 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new bdab367d8c1 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new d204d111a4b 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 7f3a081de9a 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 6153cac8fd3 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 987ced8baa2 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 5b528280ccc 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new b8b262e744c 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 54091d3d90b 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 6be9741fdb7 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 511e9575dd5 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new e52f20e8a6e 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 63ca03c7917 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 996f752b1ab 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 3532865343c 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 55aa67d7a84 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new df5137b7efe 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 5441d068440 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new abec3ad70a7 121: force: #26: : Failure after baseline build: no new commits new 7f002bff595 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 40a5e288b5d 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new f98019f81f8 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 080d4e1b964 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 2fae21e9e06 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new 77ebe6846f8 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] new 0a7ebfc8aca 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new add1bd10c27 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 4d195c88431 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new 90f8f88b6c5 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] new fd2b251f85e 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] new c091f26751c 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...] new c3172196fd5 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gc [...] new 8fd120587c8 135: onsuccess: #42: 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 (390112ff174) \ 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 2072 -> 2256 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 49164 -> 50064 bytes 04-build_abe-gcc/console.log.xz | Bin 237720 -> 235576 bytes 06-build_abe-linux/console.log.xz | Bin 8664 -> 8596 bytes 07-build_abe-glibc/console.log.xz | Bin 231948 -> 232544 bytes 08-build_abe-gdb/console.log.xz | Bin 47568 -> 47400 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2728 -> 3000 bytes 11-check_regression/console.log.xz | Bin 5068 -> 4868 bytes 11-check_regression/results.compare2 | 4 +-- 12-update_baseline/console.log | 44 ++++++++++++++-------------- 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 | 53 +++++++++++++++------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++++++------------ manifest.sh | 36 +++++++++++------------ sumfiles/gdb.log.xz | Bin 14448 -> 14428 bytes sumfiles/gdb.sum | 4 +-- 24 files changed, 94 insertions(+), 99 deletions(-)