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

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap in repository toolchain/ci/base-artifacts.

discards b721a53d64 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards 6686a2cca7 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards 60d42435ef 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards 3bf2cdcb54 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards 8f31cf030e 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 787df8d6d6 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards eeeae63b7f 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards 46fc25c5fe 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 816b54f8ce 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards e3dc3263a6 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards 4a3d6a598f 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 95ecfe5d38 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards a1072df597 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards f81385134f 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 61d2e43fb9 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards e9c3847eda 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 2f45cad5ac 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 6959193559 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 334a74405e 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards c5e487bc0b 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards a70152c538 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards be50ea5e24 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 4023415c52 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards f3869da67b 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards efad3665d5 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 83cf4376dd 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 935571ad1d 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 41e65df0da 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards bfac9a1fec 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 37fabfd79b 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 96e3f4a1cc 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards caf4f9af2f 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards d8164a8a45 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 0b71ac8643 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 6fc9a2be25 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 669f8c689e 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 9137420bea 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards a685304c92 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 4333429aff 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 57e28253ed 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 6db0bdbb1f 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 654d968bfd 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards a7486bdffd 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 41e03433e7 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards d8948cda8d 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards f736f1f98c 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 9e5fc61408 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 4e1b8d523a 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 8020a54b39 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards b04940768e 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 996d3c4887 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 6c0fba64f9 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 9efdb80e6f 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 15c77bbf8e 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 91d79f3538 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards ac87c3d470 88: onsuccess: 1: Success after gcc: 20 commits discards 22db97d9fd 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 597d5bae0f 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards b3533c1cfe 85: onsuccess: 2: Success after binutils: 4 commits discards 9f9d7a0c33 84: onsuccess: 2: Success after gcc: 9 commits discards 28b471ff0a 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 1c788a79cc 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 40a8fcf668 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards f241733788 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 0ec2b1aecc 79: onsuccess: 1: Successful build after gcc: 3 commits discards b018776a85 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 3f9b94e076 77: force: 2: Successful build after gcc: 32 commits discards f3e5e06dbf 76: onsuccess: 2: Successful build after binutils: 10 commits discards 934c73b244 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 8549b36f9d 74: onsuccess: 2: Successful build after gcc: 13 commits discards 25d6b2d336 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 2da2369004 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 7abd7065f8 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c7140e48b3 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards f77e97724c 69: onsuccess: 2: Successful build after baseline build: no [...] discards 776859926b 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 68fda19d4f 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d119904856 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 5c64e704ae 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 9ef0685b0e 64: onsuccess: 2: Successful build after gcc: 7 commits discards 645d55db21 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards a105c79cb9 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a1ef177779 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 799a54e448 60: onsuccess: 1: Successful build after gcc: 15 commits discards 3e6dfd59b9 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 59c4c0c747 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 8bab4aea72 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards d723014e30 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 16b9478125 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 302df28d35 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8859bd7423 53: onsuccess: 2: Successful build after gcc: 5 commits discards a92791edc4 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards c3ff845b96 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 2681a96aca 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 0b80d778e8 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards a4e7c553aa 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards ce85bff53a 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a88c518f96 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards f11ef52def 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards d6015fd7b5 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8ebc7de16b 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 37b9a75ee9 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 1532d99ed4 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8a3d6d1b4b 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new d295b4ae19 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 4e480f3e44 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3dbec75355 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 06930f8297 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 1366f69ddb 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 5386f73c8d 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 3242b09525 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new ce96fa0662 53: onsuccess: 2: Successful build after gcc: 5 commits new 1f01494fb3 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e1e28d31c8 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8eab788108 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 22d20b86f0 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new f4dc731767 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new d318d8d8cb 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 0ef4bea712 60: onsuccess: 1: Successful build after gcc: 15 commits new 5b56c692e3 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 5b862e1697 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 08f1b2aa74 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 26b3176a6e 64: onsuccess: 2: Successful build after gcc: 7 commits new 470450dbed 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 3a1068f8ba 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 6d3b1be02f 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 719f732a11 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 9d548d8d96 69: onsuccess: 2: Successful build after baseline build: no [...] new e539379257 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 8caa253f83 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7bd44acb3a 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new cea596ad04 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 74e9f7ed5c 74: onsuccess: 2: Successful build after gcc: 13 commits new cfb9eab28b 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 4788067e50 76: onsuccess: 2: Successful build after binutils: 10 commits new 727249cbb3 77: force: 2: Successful build after gcc: 32 commits new 79b07110c1 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 9693732298 79: onsuccess: 1: Successful build after gcc: 3 commits new 899055e5a5 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new f8e152c383 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 1eb4c35a78 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 0199180fb4 83: onsuccess: 2: Success after binutils/gcc: 7 commits new dc9cc1f6d9 84: onsuccess: 2: Success after gcc: 9 commits new 8a85dcd14d 85: onsuccess: 2: Success after binutils: 4 commits new accd0785d6 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new df19746e4d 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 7d5054890b 88: onsuccess: 1: Success after gcc: 20 commits new bfd1d0fb3a 89: onsuccess: 2: Success after binutils/gcc: 39 commits new f79fb68897 90: onsuccess: #1472: 2: Success after gcc: 2 commits new a9bccf7ddc 91: onsuccess: #1473: 2: Success after gcc: 2 commits new c32d83cec0 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 80c6c74124 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new f8660f567c 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 9f8747e81b 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new a0c028c5b9 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 2a6bb15751 97: onsuccess: #1481: 2: Success after gcc: 8 commits new b1b2703e78 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new cecb35ac25 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 02465e095b 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 5a9cb72da5 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 5799181ab1 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new eeb2cf9a38 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 6556d37fa4 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new da97157abb 105: onsuccess: #1526: 2: Success after gcc: 2 commits new ccf7534114 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 0741e2e988 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new f14a01bb45 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 5584aa5011 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 005af6feee 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 9cf6f7fea0 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 1cf971cd9f 112: onsuccess: #1533: 2: Success after gcc: 5 commits new f1d0d76322 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new ba0f469dd0 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 7d524cd6e2 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 476455da13 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 6715c165c0 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new ac9ef75b6d 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 8a147f8b16 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new edbede8ab4 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 9e01213964 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new aab460dffb 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 3f12e5af96 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 712bcfbd73 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new c6617cf137 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new e0a319038c 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 3e120b1959 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new b7a413f575 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 0f7c0c3c5c 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 3c2f592864 130: onsuccess: #1554: 2: Success after gcc: 9 commits new f8f17c7afc 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new e4070f3925 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 1ee692072b 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new fe429ac68c 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 058717bb5b 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new b209ee9feb 136: onsuccess: #1561: 2: Success after binutils: 3 commits new d61500f37c 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 9dab17a7dc 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new a90bbef6f7 139: onsuccess: #1566: 1: Success after gcc: 5 commits new 704a4654fd 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 1bf4835291 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new 2c5cab1aed 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new db33f9a08b 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new e2df2325a5 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits

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 (b721a53d64) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...]

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 1740 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2708 bytes 04-build_abe-binutils/console.log.xz | Bin 37652 -> 37924 bytes 05-build_abe-bootstrap/console.log.xz | Bin 272200 -> 270884 bytes 06-check_regression/console.log.xz | Bin 2844 -> 2888 bytes 06-check_regression/mail-body.txt | 2 +- 07-update_baseline/console.log | 38 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++++++-------- 14 files changed, 36 insertions(+), 36 deletions(-)