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 d140356a1797 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 491572ca4106 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards e2f3e285fb3a 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards b5887c13b0df 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 95f1ab8251c2 135: onsuccess: #38: 1: Success after binutils/gcc/linux/g [...] discards c2cd8b4eea5e 134: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards 0c503a1f84ab 133: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 6379d9e8fc13 132: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 6af5bd1c776f 131: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 113b639d4f67 130: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards d846cb89ca91 129: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 31b7ecc821d1 128: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 28661b75459f 127: force: #27: : Failure after baseline build: no new commits discards 08141ccb5c54 126: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards d3418878004a 125: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 6c0db8c78852 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 532257b8c16a 123: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards a06837637e3a 122: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 00082e23e45c 121: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 24f225e98189 120: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 66cc94171087 119: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards b65398078be9 118: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 62b1492294e9 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards d5d0de39d4e2 116: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 6daffb6134e8 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 6cce5bae1329 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards b840a176c41d 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] discards 581b69d3262b 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 92362d1443d2 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 305dbb2382d4 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 8516b26fc5dc 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards b05f09b6f1f1 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards 53ff55751c19 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 26b1ba3a5e91 106: onsuccess: #121: 1: Success after binutils/gcc/linux/ [...] discards 3ee879af5ed9 105: onsuccess: #120: 1: Success after binutils/gcc/linux/ [...] discards 1448feb85c21 104: onsuccess: #119: 1: Success after binutils/gcc/linux/ [...] discards b19d504bc388 103: onsuccess: #118: 1: Success after binutils/gcc/linux/ [...] discards 04f53f85798d 102: onsuccess: #117: 1: Success after binutils/gcc/linux/ [...] discards 9f25e6d118c8 101: onsuccess: #116: 1: Success after binutils/gcc/linux/ [...] discards 31ccacffda90 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 3 [...] discards 0955f431f336 99: onsuccess: #114: 1: Success after binutils/gcc/linux/g [...] discards f455520edf84 98: onsuccess: #112: 1: Success after binutils/gcc/linux/g [...] discards fcc57396a9b0 97: onsuccess: #111: 1: Success after binutils/gcc/linux/g [...] discards 6ccca008ad75 96: onsuccess: #110: 1: Success after binutils/gcc/linux/g [...] discards e2af4453a4fa 95: onsuccess: #109: 1: Success after binutils/gcc/linux/g [...] discards 4d1fe2beebcc 94: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] discards e6917ee77596 93: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] discards dc33dab3d59a 92: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] discards b046bbd44a42 91: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] discards 864fabb8813c 90: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] discards 11fadd9eb256 89: onsuccess: #102: 1: Success after binutils/gcc/linux/g [...] discards 8b6fe32fa584 88: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] discards 9e0db45b7549 87: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] discards 19b8c1c18ca6 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gl [...] discards 0c54b7ab4dfe 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gd [...] discards 3ad58f405969 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] discards 3caa16c136fb 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 [...] discards 111b36e84a03 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gd [...] discards ac28f7820ce7 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] discards 5a84e2ddd537 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] discards edb20a3676b2 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] discards c5d56892a1b1 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] discards d3ddd0eabe66 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gd [...] discards 05edb73c0538 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gd [...] discards 076354864bf1 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gl [...] discards c585ef21418b 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] discards 0f35efc59d69 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] discards 033a1e6ce92c 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gl [...] discards 6179cd95230f 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gl [...] discards c202aa351051 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gl [...] discards 61b66f2711ab 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] discards f35e235c1a6d 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gd [...] discards 1847ac334204 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] discards d46fac7c9ae4 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gd [...] discards ce5e6f26560a 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gl [...] discards e23612ae8f03 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gd [...] discards 740aae7996e1 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] discards 30cbef4ffe40 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gl [...] discards a50592fb0562 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gd [...] discards 84fa510ec712 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gd [...] discards f875299f97c2 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gl [...] discards 69eb1ee7bc72 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 251a03484251 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards f5a2bd0a2e7a 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 93c0f43eb2e6 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gd [...] discards a7fa0fe47bea 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 93f275fe1748 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] discards 1c1d17a6dc70 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] discards 706c96f73345 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gl [...] discards db8a80b139ad 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gl [...] discards 5cc4538958a3 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gl [...] discards 62b1622c9e4d 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gl [...] discards bb8f1342bd38 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 71697df86578 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] discards 801eebc3bc4a 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gl [...] discards ba77dd3b7c5e 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] discards f70bd4757eb4 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] discards 3d41c0d26b7c 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 4ca06828887f 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 0ab1adb2de7c 40: onsuccess: #49: 1: Success after linux: 219 commits discards 318e260674fb 39: onsuccess: #48: 1: Success after glibc: 2 commits new 048e01974cb3 39: onsuccess: #48: 1: Success after glibc: 2 commits new 63b7ed5b3cd0 40: onsuccess: #49: 1: Success after linux: 219 commits new 5b0985a972b0 41: onsuccess: #51: 1: Success after binutils: 12 commits new 060820fe9571 42: onsuccess: #53: 1: Success after linux: 3008 commits new 8f6ff8df81bf 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] new 96f02302ee5e 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] new bdfcab9434bc 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gl [...] new 0c6f303e7511 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new f9e146682c9f 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 9e126613c3b9 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gl [...] new 29c21d42267a 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gl [...] new 8a94b8a826ba 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gl [...] new ce478e6437e7 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gl [...] new dfcc1f913ebc 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] new c71639009a9b 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] new 20a1cc2d29df 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new ea638fb289b5 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gd [...] new 3eb6a4d6309f 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 1d4e6161e48f 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 29e4f8223b3d 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 01bfd16a85ef 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gl [...] new b4e2655c87e8 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gd [...] new 20625dbeb72f 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gd [...] new a785c293fd57 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gl [...] new 0595efedf140 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] new 9e07c2f0ebec 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gd [...] new 96dc423f6bf4 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gl [...] new bc822777f43f 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gd [...] new e8905fd18b02 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] new 1270d6211e6b 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gd [...] new 6040aae1eea0 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] new 2cff7b7c20c9 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gl [...] new 808687d7fc3a 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gl [...] new 07d47486aadf 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gl [...] new 38ad7cd14b2c 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] new bfef8d68343e 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] new 09d0346fc060 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gl [...] new d4d678d6ffd2 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gd [...] new a2bbd65a7037 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gd [...] new 00bf8327de3b 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] new efaa3aaf9286 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] new 7521a7c88ede 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] new e29a6eed5bf1 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] new cf09917cc161 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gd [...] new 99dc68d3edb3 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 [...] new 97e958045dfc 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] new 94ee140ec3d1 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gd [...] new d4f0f9006a4f 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gl [...] new 4527c82d1c3d 87: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] new 4cb19e3e3ae8 88: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] new b90704d21fc7 89: onsuccess: #102: 1: Success after binutils/gcc/linux/g [...] new 85b23a909868 90: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] new d10a3ea3ac0f 91: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] new 2a781877f56a 92: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] new d7e7a2a28ad2 93: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] new d90110ea83bc 94: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] new c8430449304b 95: onsuccess: #109: 1: Success after binutils/gcc/linux/g [...] new e9f2cdddd8ed 96: onsuccess: #110: 1: Success after binutils/gcc/linux/g [...] new 87fcf0091914 97: onsuccess: #111: 1: Success after binutils/gcc/linux/g [...] new b123ac3cda60 98: onsuccess: #112: 1: Success after binutils/gcc/linux/g [...] new c67ec38df192 99: onsuccess: #114: 1: Success after binutils/gcc/linux/g [...] new b6f8adac2277 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 3 [...] new 69577644536c 101: onsuccess: #116: 1: Success after binutils/gcc/linux/ [...] new 7c8fe3c0de3b 102: onsuccess: #117: 1: Success after binutils/gcc/linux/ [...] new 8e69714ca7ca 103: onsuccess: #118: 1: Success after binutils/gcc/linux/ [...] new e5973097892c 104: onsuccess: #119: 1: Success after binutils/gcc/linux/ [...] new 077e0f26381a 105: onsuccess: #120: 1: Success after binutils/gcc/linux/ [...] new 93bfc222588b 106: onsuccess: #121: 1: Success after binutils/gcc/linux/ [...] new 3f794f7a3ba8 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 357808b6d690 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new ee1377e0b27b 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 50a82b284c6c 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new dd63dd99fdcc 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new fadaaadb0757 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 6a9454d028df 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] new 1b0d6beb12f5 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new d72ed6625f97 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 723fe021fa19 116: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new b6393a7cef56 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 314224ffa78d 118: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new df9a4b4b5260 119: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 7a03f66fcb44 120: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 2a7bad263440 121: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 0b7427d17355 122: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 8701290cdfa7 123: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new ce1276afdb8f 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 2b55d19da753 125: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 0d90b548f0d3 126: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 05cfd2a91000 127: force: #27: : Failure after baseline build: no new commits new be2d28a0fa69 128: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 907eb82901bd 129: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new e67d1e980a46 130: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 8831311674ef 131: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new f7020a014cd2 132: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new e464ad234d3a 133: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new b98779a10d3d 134: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new 298e415e787e 135: onsuccess: #38: 1: Success after binutils/gcc/linux/g [...] new 1c61f29d8faf 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new d98626a730a6 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new a0246767cd8f 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new b0620cf68fc5 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new d9af66e8ab0e 140: onsuccess: #44: 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 (d140356a1797) \ 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 2064 -> 2036 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2492 bytes 03-build_abe-binutils/console.log.xz | Bin 35160 -> 35840 bytes 04-build_abe-gcc/console.log.xz | Bin 204236 -> 203772 bytes 06-build_abe-linux/console.log.xz | Bin 8556 -> 8604 bytes 07-build_abe-glibc/console.log.xz | Bin 241076 -> 241236 bytes 08-build_abe-gdb/console.log.xz | Bin 34920 -> 35320 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3776 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2976 -> 3340 bytes 11-check_regression/console.log.xz | Bin 4932 -> 4464 bytes 11-check_regression/results.compare2 | 4 ++-- 12-update_baseline/console.log | 36 ++++++++++++++-------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 43 ++++++++++++++-------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 ++++++++++++++-------------- manifest.sh | 32 ++++++++++++------------- sumfiles/gdb.log.xz | Bin 14636 -> 14620 bytes sumfiles/gdb.sum | 4 ++-- 23 files changed, 79 insertions(+), 88 deletions(-)