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 f3437bbff7 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards a8d5a8c3f3 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 9531665ac0 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 91106e13fe 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards d144b94807 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 06b44bb7da 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 1f6b4e58d9 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 3c049bd5a7 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 09592d60cd 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 5473377bd8 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 844f8f92a6 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 24524e40e3 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards a82657e550 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 5caf9fe4d5 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 03a75e89ef 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 4eb9b99c40 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 89ee0ddd6c 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 7db46ac5a5 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards a2dc6146ac 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 1cbdbf240f 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 31028abd64 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 494dc06eda 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 4333413703 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 6ebcfeeb33 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 21d461739c 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards f990eb2cf2 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards bf87e2eed3 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards d499027470 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards c7b639b842 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards ddfc0c2d98 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards e389529448 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 5e276eba4b 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards ab3a8cbf2f 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards baf8183c06 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 40dcf9c84c 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 5bc3453677 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 98d87ea7e9 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 69d4ee46f7 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 9563610cfa 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 049a876880 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards e31128d762 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards f7a82e51e6 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 18c929eb2f 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 08df0b1e68 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards dce176b710 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 2041c3099c 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards ec62d53b0a 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards c2df094a7c 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 638ab8f651 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 8614bb1d0d 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 8932ff0cdc 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 9957e07d65 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 5518397756 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards e552a97011 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards b8dcdd3369 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards bcd4758acc 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 9d5528f444 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 4cc6a2f65d 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards bc549c8efc 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 8edf02cdc8 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 3414988978 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards dbd01bfe3c 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 97bbb116fa 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c35723eff8 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 97bab3b931 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards f2bb3bc33e 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards dec27674f8 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 1626e7dda5 85: onsuccess: 7: Success after gcc: 9 commits discards 7d3d98ecab 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 36295794cf 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 0ab8bb3c05 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards ab739e0484 81: onsuccess: 7: Successful build after gcc: 2 commits discards e15f14f53b 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 5281d6b44e 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 27f8eeca3f 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7c45ecc8fb 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 9782c52a66 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9ad0dfa44f 75: onsuccess: 7: Successful build after linux: 44 commits discards 7e9a9604a9 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 02b7329753 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 311815273c 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 411730b886 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards b7ac6a2be8 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards f6237e9dfd 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9a164f6069 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5185ba1200 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7ef9e9a81b 66: onsuccess: 7: Successful build after gcc: 3 commits discards 4bbfdf95bc 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ff2ac65922 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0e0b377751 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 72c1010d69 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 4502d4ecfe 61: onsuccess: 4: Successful build after gcc: 15 commits discards 5f81c4560e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 4a8e656b86 59: force: 7: Successful build after gcc: 2 commits discards 7ee66451e4 58: onsuccess: 7: Successful build after glibc: 2 commits discards 624274d0f6 57: onsuccess: 7: Successful build after gcc: 7 commits discards 7857a50269 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards fa6d5cf4ae 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 11e8e05164 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards fb1ec742db 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 5752b93a2b 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new a938cb114d 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 321f930f20 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 8058d1e8b1 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 37319fb8d5 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d12a77da9d 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5114a66362 57: onsuccess: 7: Successful build after gcc: 7 commits new ed6c27d200 58: onsuccess: 7: Successful build after glibc: 2 commits new e15f665d1c 59: force: 7: Successful build after gcc: 2 commits new 5bf2693bcf 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 198e09d311 61: onsuccess: 4: Successful build after gcc: 15 commits new 2f7a271c11 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 627d77c4ac 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 725014b541 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b19b0aa063 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4f64d88022 66: onsuccess: 7: Successful build after gcc: 3 commits new b32a16ac42 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 03c74ed2c0 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d6bbfafa0b 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 741f672110 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new e9f3581f6d 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 3111aacf0b 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 4116ef8d4c 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2fc788ddfe 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 2cc0088fed 75: onsuccess: 7: Successful build after linux: 44 commits new 49d223f6fc 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 90c7ebef9e 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new f571f97776 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 01660047b9 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b65c76e55a 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new f6c6a151a5 81: onsuccess: 7: Successful build after gcc: 2 commits new b22be48b82 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new fb18f8332e 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 2680a09c67 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new e79afc6b7b 85: onsuccess: 7: Success after gcc: 9 commits new 3c027b9cb7 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new ec3c77c950 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new af9a07e901 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 8aa1e239c1 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 7f8c122c66 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b67f7d213a 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 63aa5b74ed 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new b80f6c8fd9 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 969273a753 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 5f920633df 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 51b833ec55 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 9529e3f7dc 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 7ce1a6b5f5 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new d13ad8edd9 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 54c5381310 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new b6eeb0c0db 101: onsuccess: #1609: 7: Success after binutils: 78 commits new a8ef7d27a3 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 9b89ecf76a 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new c391e16528 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 897c3e12b9 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 78df0cf1b5 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 82a2c2ff3b 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 5b495eaeca 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new deaedeb5d7 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 80f6a40674 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new ae383b6383 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 9a9c014c39 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 909ea7f256 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 90049d123d 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 337f344f69 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 0efdf4cb46 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 08c7a0aae0 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 323c3ee87b 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 9bb4877ca0 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 2c2599aa98 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 63656b1866 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new dc0c2e42e2 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 113691f8a0 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new ea81fc5db1 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 6aaee169dd 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new daea0ec246 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 3ef077ab60 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new ff19260914 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 433004a0f7 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 64594196e9 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 0868ee2e90 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 918d8c17f2 132: onsuccess: #1645: 7: Success after linux: 23 commits new a81d900f65 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new f3d3938413 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 99da78d9ab 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new dade1915db 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 85d71ca1de 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new ee5ee2b355 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new a8ed850e08 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 1ce24dfdba 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 95004054df 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 8815e8c20e 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 5b770f7de5 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 18f6c7c0b2 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 258a03de2b 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 830441d135 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 313315b69b 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new e18d9c2074 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 5919cae3a7 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 3f828e3c21 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new 065b36b7bf 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 068ba79527 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new e514d07682 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...]
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 (f3437bbff7) \ 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 1664 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30228 -> 30424 bytes 05-build_abe-stage1/console.log.xz | Bin 91164 -> 91508 bytes 07-build_abe-linux/console.log.xz | Bin 8472 -> 8492 bytes 08-build_abe-glibc/console.log.xz | Bin 234220 -> 235636 bytes 09-build_abe-stage2/console.log.xz | Bin 224088 -> 225880 bytes 10-build_abe-gdb/console.log.xz | Bin 37440 -> 37120 bytes 11-build_abe-qemu/console.log.xz | Bin 31584 -> 31804 bytes 12-check_regression/console.log.xz | Bin 3820 -> 3996 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++++++++++---------- 19 files changed, 57 insertions(+), 57 deletions(-)