This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts.

discards 1b84d773a8fe 499: onsuccess: #45: 7: [TCWG CI] Success after binutils/g [...] discards 6737cb713bdf 498: onsuccess: #44: 7: [TCWG CI] Success after binutils/g [...] discards 4e03c589ea58 497: onsuccess: #43: 7: [TCWG CI] Success after binutils/g [...] discards 63093672dbb1 496: onsuccess: #42: 7: [TCWG CI] Success after binutils/g [...] discards 54f7a6ea34e6 495: onsuccess: #41: 7: [TCWG CI] Success after binutils/g [...] discards deaf3d5bf997 494: onsuccess: #40: 7: [TCWG CI] Success after binutils/g [...] discards 4e5aa8e8f1b5 493: onsuccess: #39: 7: [TCWG CI] Success after binutils/g [...] discards d6494414f685 492: onsuccess: #37: 7: Success after binutils/gcc/linux/g [...] discards 0419eada9588 491: onsuccess: #35: 7: Success after binutils/gcc/linux/g [...] discards bd0d8b468f4b 490: onsuccess: #34: 7: Success after binutils/gcc/linux/g [...] discards 3ad3fe46b7d6 489: onsuccess: #33: 7: Success after binutils/gcc/linux/g [...] discards 05ec8b887807 488: onsuccess: #32: 7: Success after binutils/gcc/linux/g [...] discards 0416a745adf0 487: onsuccess: #31: 7: Success after binutils/gcc/linux/g [...] discards f0f531ac8271 486: onsuccess: #30: 7: Success after binutils/gcc/linux/g [...] discards a1398058b333 485: onsuccess: #29: 7: Success after binutils/gcc/linux/g [...] discards d893359676a0 484: onsuccess: #28: 7: Success after binutils/gcc/linux/g [...] discards 9e228ab0636d 483: onsuccess: #27: 7: Success after binutils/gcc/linux/g [...] discards 76e18c31bf3c 482: onsuccess: #26: 7: Success after binutils/gcc/linux/g [...] discards 092a1da930f2 481: onsuccess: #25: 7: Success after binutils/gcc/linux/g [...] discards 8d545b5538c2 480: onsuccess: #24: 7: Success after binutils/gcc/linux/g [...] discards b209fe5538b8 479: onsuccess: #23: 7: Success after binutils/gcc/linux/g [...] discards b109f8071714 478: onsuccess: #22: 7: Success after binutils/gcc/linux/g [...] discards 9552149abc75 477: onsuccess: #21: 7: Success after binutils/gcc/linux/g [...] discards 3a19bb6c2dd4 476: onsuccess: #20: 7: Success after binutils/gcc/linux/g [...] discards a7499a822519 475: onsuccess: #19: 7: Success after binutils/gcc/linux/g [...] discards 7f61014b4a81 474: onsuccess: #18: 7: Success after binutils/gcc/linux/g [...] discards 9c9f331a464a 473: onsuccess: #17: 7: Success after binutils/gcc/linux/g [...] discards 014898b49e21 472: onsuccess: #16: 7: Success after binutils/gcc/linux/g [...] discards 1c66cd5c48c8 471: onsuccess: #15: 7: Success after binutils/gcc/linux/g [...] discards dc2fd6f59bde 470: onsuccess: #14: 7: Success after binutils/gcc/linux/g [...] discards f8f97b11c60c 469: onsuccess: #13: 7: Success after binutils/gcc/linux/g [...] discards 6cdeb4e84fb3 468: onsuccess: #12: 7: Success after binutils/gcc/linux/g [...] discards e1f080a83cd9 467: onsuccess: #11: 7: Success after binutils/gcc/linux/g [...] discards bfb88fbbf4f3 466: onsuccess: #10: 7: Success after binutils/gcc/linux/g [...] discards 40be4cc3d2bd 465: onsuccess: #9: 7: Success after binutils/gcc/linux/gd [...] discards 7927756dc24a 464: onsuccess: #8: 7: Success after binutils/gcc/linux/gl [...] discards 2cdca0ef3e20 463: onsuccess: #7: 7: Success after binutils/gcc/gdb: 5 commits discards a41a2b525aa0 462: onsuccess: #6: 7: Success after gcc/linux: 385 commits discards 0f813b2b9f19 461: onsuccess: #5: 7: Success after binutils/gcc/linux/gl [...] discards c28c434878ba 460: onsuccess: #4: 7: Success after binutils/gcc/gdb: 5 commits discards 6b6868d22701 459: onsuccess: #3: 7: Success after binutils/gcc/glibc/gd [...] discards 13eed1472595 458: onsuccess: #2: 7: Success after gcc/linux/glibc: 581 commits discards 2a17e4a9073a 457: onsuccess: #2194: 7: Success after binutils/gcc/linux [...] discards c8e8095e248d 456: onsuccess: #1: 7: Success after binutils/gcc/linux/gl [...] discards 82bbae1a3fab 455: onsuccess: #2193: 7: Success after binutils/gcc/gdb: [...] discards a6bdd481d007 454: onsuccess: #2192: 7: Success after binutils/linux/gli [...] discards e0d19dc13e04 453: onsuccess: #2191: 7: Success after binutils/gcc/linux [...] discards 1189fce1fd04 452: onsuccess: #2190: 7: Success after binutils/gcc/linux [...] discards c8bdcb0ec64d 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: [...] discards eff9d687d877 450: onsuccess: #2188: 7: Success after binutils/gcc/linux [...] discards 20049d4b15c3 449: onsuccess: #2186: 7: Success after binutils/gcc/linux [...] discards 1874176fb0dc 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/q [...] discards 607eb5979d06 447: onsuccess: #2184: 7: Success after binutils/gcc/linux [...] discards 220e5bfe44e3 446: onsuccess: #2183: 7: Success after binutils/gcc/linux [...] discards 61500b6a067f 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc [...] discards 987476666cad 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc [...] discards 260b17908fb6 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits discards a0bdd1cdbe2e 442: onsuccess: #2179: 7: Success after binutils/gcc/linux [...] discards 192cfb92ac36 441: onsuccess: #2178: 7: Success after binutils/linux/gdb [...] discards bc72d41641f5 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: [...] discards 7a9d6f919f90 439: onsuccess: #2176: 7: Success after linux: 11 commits discards 67f50f4e0898 438: onsuccess: #2175: 7: Success after gcc: 7 commits discards d438a3ba37db 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits discards 732333ba5630 436: onsuccess: #2173: 7: Success after binutils/gcc/linux [...] discards 2cbe861c2b0c 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc [...] discards a9ea61af21c0 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits discards 8dba7884d493 433: onsuccess: #2170: 7: Success after binutils/gcc/linux [...] discards fbbc3842af69 432: onsuccess: #2169: 7: Success after binutils/gcc/linux [...] discards e01a48774895 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/q [...] discards dd5ccc644bfc 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/q [...] discards 12d59abd0324 429: onsuccess: #2166: 7: Success after binutils/gcc/linux [...] discards 9d39de225c1a 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc [...] discards 9f4d6c9d5a8e 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits discards 60ba6942c713 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: [...] discards 31c86f648dc7 425: onsuccess: #2161: 7: Success after binutils/gcc/linux [...] discards a7b5ac0ac4a8 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc [...] discards 2631cb0dd75a 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: [...] discards 566ffe437d50 422: onsuccess: #2158: 7: Success after binutils/gcc/linux [...] discards 4ab0e60e5310 421: onsuccess: #2157: 7: Success after binutils/gcc/linux [...] discards 149d5756d862 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: [...] discards 95abae9e346e 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: [...] discards fc783e218c9f 418: onsuccess: #2154: 7: Success after binutils/gcc/linux [...] discards 3e6a46e1e91b 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits discards 8df0fa6746a0 416: onsuccess: #2152: 7: Success after gcc: 50 commits discards fc44cbd96915 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: [...] discards 7f9c63abe485 414: onsuccess: #2150: 7: Success after binutils/gcc/linux [...] discards b1fe49d04c99 413: onsuccess: #2149: 7: Success after binutils/gcc/linux [...] discards 398739dc0b40 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: [...] discards a118ac7e7fb6 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: [...] discards 45db92fccfc2 410: onsuccess: #2146: 7: Success after binutils/gcc/linux [...] discards b0d4e75efac7 409: onsuccess: #2145: 7: Success after binutils/gcc/linux [...] discards 8b2217dc8f28 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/q [...] discards 7661183776a8 407: onsuccess: #2143: 7: Success after binutils/gcc/linux [...] discards b624c9ff580a 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: [...] discards 02851af51689 405: onsuccess: #2141: 7: Success after binutils/gcc/linux [...] discards ed318a13ad11 404: onsuccess: #2139: 7: Success after basepoints/gcc-13- [...] discards 1f4fcbebcfb9 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: [...] discards cc0bbf5c1e9f 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: [...] discards 2ca204e05a42 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc [...] discards 27ca8410b394 400: onsuccess: #2135: 7: Success after binutils/gcc/linux [...] discards 724a964bd352 399: onsuccess: #2134: 7: Success after binutils/gcc/linux [...] new 46568ed5cfbc 399: onsuccess: #2134: 7: Success after binutils/gcc/linux [...] new 8707bb976d18 400: onsuccess: #2135: 7: Success after binutils/gcc/linux [...] new d113f40014ea 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc [...] new 232dd52c767a 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: [...] new 4f96af25d799 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: [...] new a562b3cb3b18 404: onsuccess: #2139: 7: Success after basepoints/gcc-13- [...] new af9f04535137 405: onsuccess: #2141: 7: Success after binutils/gcc/linux [...] new 40c1350cc828 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: [...] new 209e5818ce7a 407: onsuccess: #2143: 7: Success after binutils/gcc/linux [...] new 8fb707f18bd5 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/q [...] new 50a51c3f170f 409: onsuccess: #2145: 7: Success after binutils/gcc/linux [...] new 3dd4d9ef9ca4 410: onsuccess: #2146: 7: Success after binutils/gcc/linux [...] new 5a7817c1e6f3 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: [...] new c98f0535b41c 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: [...] new 0b991a474082 413: onsuccess: #2149: 7: Success after binutils/gcc/linux [...] new 2ae474e0784d 414: onsuccess: #2150: 7: Success after binutils/gcc/linux [...] new d60a53f11877 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: [...] new bebf56f033e0 416: onsuccess: #2152: 7: Success after gcc: 50 commits new 14c852627309 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits new 33eb392b0721 418: onsuccess: #2154: 7: Success after binutils/gcc/linux [...] new 8fdbd16462d3 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: [...] new 26f43377b814 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: [...] new dcc1cf3c7701 421: onsuccess: #2157: 7: Success after binutils/gcc/linux [...] new 40541de9fbec 422: onsuccess: #2158: 7: Success after binutils/gcc/linux [...] new c7f784f4b89c 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: [...] new 887c7e74a6aa 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc [...] new f6ba407533c9 425: onsuccess: #2161: 7: Success after binutils/gcc/linux [...] new 3d7782291641 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: [...] new 3184b4831ef5 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits new f03f52c19b4c 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc [...] new 64e434fa7961 429: onsuccess: #2166: 7: Success after binutils/gcc/linux [...] new ba22bb2cae2b 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/q [...] new ac2ad1a5c9e1 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/q [...] new 0636bb2daa2a 432: onsuccess: #2169: 7: Success after binutils/gcc/linux [...] new 8d19e8bd7949 433: onsuccess: #2170: 7: Success after binutils/gcc/linux [...] new 0de80ef7bd5e 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits new fe965714262d 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc [...] new a8517c6ed4c3 436: onsuccess: #2173: 7: Success after binutils/gcc/linux [...] new 70ea70b22179 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits new d114ca57cc2e 438: onsuccess: #2175: 7: Success after gcc: 7 commits new 0fe7c7ffba8e 439: onsuccess: #2176: 7: Success after linux: 11 commits new b9644b4f48f0 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: [...] new 2a6369a3cde7 441: onsuccess: #2178: 7: Success after binutils/linux/gdb [...] new 9cdc72a2b624 442: onsuccess: #2179: 7: Success after binutils/gcc/linux [...] new 213bd43e5984 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits new 1ead395a1b8f 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc [...] new c9b7cafcacfc 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc [...] new b98c79bd8f67 446: onsuccess: #2183: 7: Success after binutils/gcc/linux [...] new 121d10f4f02b 447: onsuccess: #2184: 7: Success after binutils/gcc/linux [...] new 3e7b42d00832 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/q [...] new fe8fa8290b4d 449: onsuccess: #2186: 7: Success after binutils/gcc/linux [...] new 33fbf3d24917 450: onsuccess: #2188: 7: Success after binutils/gcc/linux [...] new 8a51888686a4 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: [...] new 63cbddbe411d 452: onsuccess: #2190: 7: Success after binutils/gcc/linux [...] new bde3fd9c37e6 453: onsuccess: #2191: 7: Success after binutils/gcc/linux [...] new 634c7fd6255f 454: onsuccess: #2192: 7: Success after binutils/linux/gli [...] new 1a89f306b50c 455: onsuccess: #2193: 7: Success after binutils/gcc/gdb: [...] new 034f7d8635cf 456: onsuccess: #1: 7: Success after binutils/gcc/linux/gl [...] new 083069d4ecd6 457: onsuccess: #2194: 7: Success after binutils/gcc/linux [...] new 4409d95c8b06 458: onsuccess: #2: 7: Success after gcc/linux/glibc: 581 commits new 896a6690cb26 459: onsuccess: #3: 7: Success after binutils/gcc/glibc/gd [...] new e0ae958f5461 460: onsuccess: #4: 7: Success after binutils/gcc/gdb: 5 commits new 7ab6821630a4 461: onsuccess: #5: 7: Success after binutils/gcc/linux/gl [...] new 422ec3f39a0c 462: onsuccess: #6: 7: Success after gcc/linux: 385 commits new 291b0621d2a9 463: onsuccess: #7: 7: Success after binutils/gcc/gdb: 5 commits new c691b3dca433 464: onsuccess: #8: 7: Success after binutils/gcc/linux/gl [...] new 6d52f73bd3fe 465: onsuccess: #9: 7: Success after binutils/gcc/linux/gd [...] new aa5399e3804a 466: onsuccess: #10: 7: Success after binutils/gcc/linux/g [...] new cab14d992f3b 467: onsuccess: #11: 7: Success after binutils/gcc/linux/g [...] new 03e6a34915fa 468: onsuccess: #12: 7: Success after binutils/gcc/linux/g [...] new a316743799d8 469: onsuccess: #13: 7: Success after binutils/gcc/linux/g [...] new b4a5a80a072a 470: onsuccess: #14: 7: Success after binutils/gcc/linux/g [...] new ad1c9a876726 471: onsuccess: #15: 7: Success after binutils/gcc/linux/g [...] new dec82961166b 472: onsuccess: #16: 7: Success after binutils/gcc/linux/g [...] new dd528287bf00 473: onsuccess: #17: 7: Success after binutils/gcc/linux/g [...] new 82a8bc57c88f 474: onsuccess: #18: 7: Success after binutils/gcc/linux/g [...] new dccd33041471 475: onsuccess: #19: 7: Success after binutils/gcc/linux/g [...] new aae377386eff 476: onsuccess: #20: 7: Success after binutils/gcc/linux/g [...] new 4b9cea1aee19 477: onsuccess: #21: 7: Success after binutils/gcc/linux/g [...] new a6d52a6678f3 478: onsuccess: #22: 7: Success after binutils/gcc/linux/g [...] new 124410c7bce2 479: onsuccess: #23: 7: Success after binutils/gcc/linux/g [...] new 3512204fcfbf 480: onsuccess: #24: 7: Success after binutils/gcc/linux/g [...] new 092c026ff972 481: onsuccess: #25: 7: Success after binutils/gcc/linux/g [...] new da945fd7354e 482: onsuccess: #26: 7: Success after binutils/gcc/linux/g [...] new 8526d73213a9 483: onsuccess: #27: 7: Success after binutils/gcc/linux/g [...] new 235223f737b9 484: onsuccess: #28: 7: Success after binutils/gcc/linux/g [...] new 805016bb37a1 485: onsuccess: #29: 7: Success after binutils/gcc/linux/g [...] new 86d64e1f78dd 486: onsuccess: #30: 7: Success after binutils/gcc/linux/g [...] new 2a46b25f82a1 487: onsuccess: #31: 7: Success after binutils/gcc/linux/g [...] new 5d1739d7323f 488: onsuccess: #32: 7: Success after binutils/gcc/linux/g [...] new a128b290bbbc 489: onsuccess: #33: 7: Success after binutils/gcc/linux/g [...] new 365ce0d50035 490: onsuccess: #34: 7: Success after binutils/gcc/linux/g [...] new a4fd02995fc7 491: onsuccess: #35: 7: Success after binutils/gcc/linux/g [...] new 42b8800b6c95 492: onsuccess: #37: 7: Success after binutils/gcc/linux/g [...] new 6c996712bb18 493: onsuccess: #39: 7: [TCWG CI] Success after binutils/g [...] new 1aae008ffa16 494: onsuccess: #40: 7: [TCWG CI] Success after binutils/g [...] new ece9613476fd 495: onsuccess: #41: 7: [TCWG CI] Success after binutils/g [...] new 46d35c680f17 496: onsuccess: #42: 7: [TCWG CI] Success after binutils/g [...] new 70be15e75db4 497: onsuccess: #43: 7: [TCWG CI] Success after binutils/g [...] new 09a05da74b2c 498: onsuccess: #44: 7: [TCWG CI] Success after binutils/g [...] new affa20bc00ea 499: onsuccess: #45: 7: [TCWG CI] Success after binutils/g [...] new 14e678f8ec0f 500: onsuccess: #46: 7: [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 (1b84d773a8fe) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]

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 2092 -> 2088 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2520 bytes 04-build_abe-binutils/console.log.xz | Bin 27124 -> 26620 bytes 05-build_abe-stage1/console.log.xz | Bin 89084 -> 89260 bytes 07-build_abe-linux/console.log.xz | Bin 8740 -> 8752 bytes 08-build_abe-glibc/console.log.xz | Bin 233776 -> 232404 bytes 09-build_abe-stage2/console.log.xz | Bin 226608 -> 224284 bytes 10-build_abe-gdb/console.log.xz | Bin 34552 -> 34156 bytes 11-build_abe-qemu/console.log.xz | Bin 32024 -> 30984 bytes 12-check_regression/console.log.xz | Bin 4580 -> 4828 bytes 13-update_baseline/console.log | 70 +++++++++++++++++------------------ 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 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 61 +++++++++++++++--------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 44 +++++++++++----------- manifest.sh | 48 ++++++++++++------------ 22 files changed, 120 insertions(+), 119 deletions(-)