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 623b60f46796 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards 78488bd3609d 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 0ed08b14a268 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards e5f80627e8fb 135: onsuccess: #38: 1: Success after binutils/gcc/linux/g [...] discards 09775ca6037d 134: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards b3f0a0b89594 133: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 56af099e2f05 132: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 23a7278647b9 131: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 1911e4416564 130: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 5c25c60eb621 129: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 74b183609c6a 128: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 30ae2e103fb5 127: force: #27: : Failure after baseline build: no new commits discards e0305d02d706 126: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards b7c050dbaf36 125: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 41af42bff492 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards baeebe7f1f9f 123: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 582e683eea85 122: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 0fdf703408b2 121: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 7a832836e490 120: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards eb04281a082c 119: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 558f89ca1381 118: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 9183b000241b 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 2d569c2981ea 116: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 6bb2f5260abd 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards b1a64347d29e 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 8407d0f6adfb 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] discards b5d54f5ff109 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 55d94c922623 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 056a32159b28 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards c9f793e60c4a 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards ed9f2ef30764 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards 45d557984adf 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 9c91c733f9a8 106: onsuccess: #121: 1: Success after binutils/gcc/linux/ [...] discards 8396ed7f445f 105: onsuccess: #120: 1: Success after binutils/gcc/linux/ [...] discards 048715d8ed72 104: onsuccess: #119: 1: Success after binutils/gcc/linux/ [...] discards 47026f4abbb5 103: onsuccess: #118: 1: Success after binutils/gcc/linux/ [...] discards 44181ed49cf3 102: onsuccess: #117: 1: Success after binutils/gcc/linux/ [...] discards cb0c37431960 101: onsuccess: #116: 1: Success after binutils/gcc/linux/ [...] discards fcceab61f6b9 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 3 [...] discards b3c674d4ec26 99: onsuccess: #114: 1: Success after binutils/gcc/linux/g [...] discards af970fc09246 98: onsuccess: #112: 1: Success after binutils/gcc/linux/g [...] discards 686ad94f143e 97: onsuccess: #111: 1: Success after binutils/gcc/linux/g [...] discards 481702caec7c 96: onsuccess: #110: 1: Success after binutils/gcc/linux/g [...] discards c576f0344e3e 95: onsuccess: #109: 1: Success after binutils/gcc/linux/g [...] discards 40ab3383836e 94: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] discards f6278ca6aebe 93: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] discards d9b131ea8589 92: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] discards 7b4cfdb661cc 91: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] discards d701690b2f77 90: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] discards 27d127db49eb 89: onsuccess: #102: 1: Success after binutils/gcc/linux/g [...] discards 857772504add 88: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] discards 066652545f7c 87: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] discards 741442a05f7b 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gl [...] discards 81891581f8ef 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gd [...] discards c46ef2a6a2cb 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] discards 7a044078bd3c 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 [...] discards e169d2dd4dc8 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gd [...] discards 5ffa89dc4514 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] discards f436d57ad1c9 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] discards 04da1587bb77 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] discards ab321a9c0539 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] discards 2f32d8a41afd 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gd [...] discards f7804f1dd613 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gd [...] discards c74142733e86 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gl [...] discards b8938c673eaa 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] discards ab1cc1121b13 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] discards 128a70a8a095 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gl [...] discards 1bc13f6304e3 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gl [...] discards 5b6ff1ba5c1a 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gl [...] discards 0bb98ddb57fe 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] discards 8bfa6a26c13d 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gd [...] discards 1ce9558a0ae8 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] discards 01309922788a 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gd [...] discards a77ac29fce17 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gl [...] discards cfd52aaa3239 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gd [...] discards 740c0c0f670b 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] discards 03cfa842dd28 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gl [...] discards 5e5978ced8be 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gd [...] discards 989b2dc45f6a 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gd [...] discards 2d5f2dff3215 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gl [...] discards d9c98ba36690 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 257b7ee94365 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards bc8757eeeb2e 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards ff0ffd9c12ab 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gd [...] discards afd12d3ad063 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards ff98c86b0c97 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] discards cd18625d0f2c 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] discards 1da4214a84fc 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gl [...] discards 892c49955217 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gl [...] discards 8d2156478586 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gl [...] discards a238d8753a08 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gl [...] discards c39fc834ff4a 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 7039eb990782 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] discards cd940a38dbcc 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gl [...] discards c22f5a5bf2c9 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] discards 19c5c7a46e47 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] discards 902b8f7bf53b 42: onsuccess: #53: 1: Success after linux: 3008 commits discards e971c279dbb9 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 3a2d53e9255a 40: onsuccess: #49: 1: Success after linux: 219 commits discards ece40cfa14a2 39: onsuccess: #48: 1: Success after glibc: 2 commits discards e2658f80868a 38: onsuccess: #46: 1: Success after binutils: 26 commits new 6aaecacf3e72 38: onsuccess: #46: 1: Success after binutils: 26 commits new 318e260674fb 39: onsuccess: #48: 1: Success after glibc: 2 commits new 0ab1adb2de7c 40: onsuccess: #49: 1: Success after linux: 219 commits new 4ca06828887f 41: onsuccess: #51: 1: Success after binutils: 12 commits new 3d41c0d26b7c 42: onsuccess: #53: 1: Success after linux: 3008 commits new f70bd4757eb4 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] new ba77dd3b7c5e 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] new 801eebc3bc4a 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gl [...] new 71697df86578 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new bb8f1342bd38 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 62b1622c9e4d 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gl [...] new 5cc4538958a3 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gl [...] new db8a80b139ad 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gl [...] new 706c96f73345 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gl [...] new 1c1d17a6dc70 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] new 93f275fe1748 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] new a7fa0fe47bea 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 93c0f43eb2e6 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gd [...] new f5a2bd0a2e7a 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 251a03484251 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 69eb1ee7bc72 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new f875299f97c2 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gl [...] new 84fa510ec712 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gd [...] new a50592fb0562 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gd [...] new 30cbef4ffe40 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gl [...] new 740aae7996e1 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] new e23612ae8f03 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gd [...] new ce5e6f26560a 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gl [...] new d46fac7c9ae4 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gd [...] new 1847ac334204 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] new f35e235c1a6d 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gd [...] new 61b66f2711ab 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] new c202aa351051 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gl [...] new 6179cd95230f 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gl [...] new 033a1e6ce92c 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gl [...] new 0f35efc59d69 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] new c585ef21418b 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] new 076354864bf1 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gl [...] new 05edb73c0538 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gd [...] new d3ddd0eabe66 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gd [...] new c5d56892a1b1 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] new edb20a3676b2 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] new 5a84e2ddd537 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] new ac28f7820ce7 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] new 111b36e84a03 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gd [...] new 3caa16c136fb 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 [...] new 3ad58f405969 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] new 0c54b7ab4dfe 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gd [...] new 19b8c1c18ca6 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gl [...] new 9e0db45b7549 87: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] new 8b6fe32fa584 88: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] new 11fadd9eb256 89: onsuccess: #102: 1: Success after binutils/gcc/linux/g [...] new 864fabb8813c 90: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] new b046bbd44a42 91: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] new dc33dab3d59a 92: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] new e6917ee77596 93: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] new 4d1fe2beebcc 94: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] new e2af4453a4fa 95: onsuccess: #109: 1: Success after binutils/gcc/linux/g [...] new 6ccca008ad75 96: onsuccess: #110: 1: Success after binutils/gcc/linux/g [...] new fcc57396a9b0 97: onsuccess: #111: 1: Success after binutils/gcc/linux/g [...] new f455520edf84 98: onsuccess: #112: 1: Success after binutils/gcc/linux/g [...] new 0955f431f336 99: onsuccess: #114: 1: Success after binutils/gcc/linux/g [...] new 31ccacffda90 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 3 [...] new 9f25e6d118c8 101: onsuccess: #116: 1: Success after binutils/gcc/linux/ [...] new 04f53f85798d 102: onsuccess: #117: 1: Success after binutils/gcc/linux/ [...] new b19d504bc388 103: onsuccess: #118: 1: Success after binutils/gcc/linux/ [...] new 1448feb85c21 104: onsuccess: #119: 1: Success after binutils/gcc/linux/ [...] new 3ee879af5ed9 105: onsuccess: #120: 1: Success after binutils/gcc/linux/ [...] new 26b1ba3a5e91 106: onsuccess: #121: 1: Success after binutils/gcc/linux/ [...] new 53ff55751c19 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new b05f09b6f1f1 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 8516b26fc5dc 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 305dbb2382d4 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 92362d1443d2 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 581b69d3262b 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new b840a176c41d 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] new 6cce5bae1329 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 6daffb6134e8 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new d5d0de39d4e2 116: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 62b1492294e9 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new b65398078be9 118: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 66cc94171087 119: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 24f225e98189 120: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 00082e23e45c 121: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new a06837637e3a 122: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 532257b8c16a 123: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 6c0db8c78852 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new d3418878004a 125: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 08141ccb5c54 126: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 28661b75459f 127: force: #27: : Failure after baseline build: no new commits new 31b7ecc821d1 128: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new d846cb89ca91 129: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 113b639d4f67 130: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 6af5bd1c776f 131: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 6379d9e8fc13 132: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 0c503a1f84ab 133: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new c2cd8b4eea5e 134: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new 95f1ab8251c2 135: onsuccess: #38: 1: Success after binutils/gcc/linux/g [...] new b5887c13b0df 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new e2f3e285fb3a 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 491572ca4106 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new d140356a1797 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...]

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 (623b60f46796) \ 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 -> 2064 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 35992 -> 35160 bytes 04-build_abe-gcc/console.log.xz | Bin 203940 -> 204236 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9600 -> 8556 bytes 07-build_abe-glibc/console.log.xz | Bin 240612 -> 241076 bytes 08-build_abe-gdb/console.log.xz | Bin 35712 -> 34920 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3796 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3712 -> 2976 bytes 11-check_regression/console.log.xz | Bin 4876 -> 4932 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 42 ++++++++++++++-------------- 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 | 51 +++++++++++++++++----------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++++++------------- manifest.sh | 36 ++++++++++++------------ sumfiles/gdb.log.xz | Bin 14624 -> 14636 bytes sumfiles/gdb.sum | 4 +-- 26 files changed, 97 insertions(+), 98 deletions(-)