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_check_gcc/master-arm in repository toolchain/ci/base-artifacts.

discards b3a3eda6d3 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards cd1476d2ff 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 48281eb9fc 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards ef3940e156 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 6c7b32e490 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 604ea28b7d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 1247ce43f5 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 82e0cf73e0 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 98585fa269 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 274efb7543 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 2027e73ee8 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 4547d0653d 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 4c0a87fef4 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards a197939054 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 4ef8f496eb 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 79634f672f 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 47f5b4b18a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 73d756dc16 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 351fbd6001 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 600564e810 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards a56e504664 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards a60d90b19a 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 41e460cbfb 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 9abae44c4e 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards e6e1039018 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 3d6e6fd3e1 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 8c362f4a71 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 478311b062 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 6bfa4391a1 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 12a8623527 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 74cda48d2c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards a10cbad86f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 3c628c7570 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 76bbe6403c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 91d5299be2 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 24178bf72c 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards e3d833e7ac 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards ddb8cc6711 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards fbe9ae9613 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 7a85376ae6 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards d3a210355a 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 8b5b1bfdf8 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards f3d583b9e0 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 30a6d55f2c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards b779edb46e 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards a1d28eb9f7 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 265f9593f9 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards c8cec07c41 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 9cb4f6456e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 50f5454927 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards c371120b3b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards c7382f5076 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 6a645fd8af 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards fe4a1797fc 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 67eca9c795 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards e2d0c4c5b1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 740efe8f33 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 349e2f6b7e 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 0d0de87a90 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 25350e8523 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 413adb07e2 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 551455183a 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards cba390dde4 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 568f9af514 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a5b9795816 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c75900cec8 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards d2d515a769 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ffa685b59c 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 23163b8a6e 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c7574b31e6 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards b729e6ff33 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 564dd1b825 74: onsuccess: 1: Successful build after linux: 44 commits discards c872ba969c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 480ee871f6 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9e0c672c91 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 652bc1f8f0 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 45a8afc39f 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards b498021980 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7a0f5e6848 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8653184f9d 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5b980fcdc4 65: onsuccess: 1: Successful build after gcc: 4 commits discards 4c7fca1d0f 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ea8e97acf3 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 550f38123f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 46a063874e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 9c69f3243d 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 8145fb89ef 59: onsuccess: 1: Successful build after glibc: 2 commits discards 157e52e7e5 58: onsuccess: 1: Successful build after binutils: 2 commits discards 3371a33d13 57: onsuccess: 1: Successful build after gcc: 7 commits discards 10e868562e 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c9d7f03c01 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 42e9663b57 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 59cf0a1927 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 1d58eee885 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 113e03b9bf 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4823d07ac3 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 10901925c3 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ce30b6eb82 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards f9144999a3 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5610f5c660 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 91792a0685 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0b02bb6282 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cd7c0358bb 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new dde93d3159 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 362c3425d0 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new a3cde4271c 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 063fb4f889 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9599ed7bec 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 01e61b996c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 13a2a06b7b 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 839cb53b5d 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new c00abce9ce 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 68d266ba97 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8f04b89c3e 57: onsuccess: 1: Successful build after gcc: 7 commits new 902919300f 58: onsuccess: 1: Successful build after binutils: 2 commits new b80a79b835 59: onsuccess: 1: Successful build after glibc: 2 commits new 3fc39d8472 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 8c9722a4ad 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 1eae0ffe7c 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 55283022a5 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 129adc366a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3650eddc40 65: onsuccess: 1: Successful build after gcc: 4 commits new ddc33ed6a8 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 428c30c822 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d3cc8d7dcc 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6f93a8d30c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 8cfac98ff2 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 142516c4d7 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new eef49b0ea7 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e2a4a23607 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 157b000514 74: onsuccess: 1: Successful build after linux: 44 commits new aea051dd27 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ae15d47665 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new cbfd730abe 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9ce174d9f2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 95b18aacee 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c6298a144f 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 8e8c1d71d4 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 271d055af0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new fc19e06693 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new fe2d0d83b6 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 036d4d5364 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 3a79cedd21 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 8a65161d44 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new d655b06a79 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ebf56773e8 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ab30ed6397 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0dc4d64e6b 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 808990ea28 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new a2fd076206 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 78f7bf282f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new cc510d185a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new e2b38ff740 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new ec659cdee8 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new bb282dce99 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 226cec3118 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 23f1aef86f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new d628d5127a 101: onsuccess: #1693: 1: Success after glibc: 14 commits new f992c6572c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new db22686902 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 264aa95cd9 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 19bdf680a5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 907732a504 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new ca7fcbdea8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 8760599bd1 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 30a36b8540 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new fe47d65218 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 8212db00b8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 7222ddfb0d 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new adeeff7331 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 045e7b7fb8 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new f9f31138c8 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 76522a1c0b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 9e98615099 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 53627e4b34 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 2c5fd9bb5d 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new ccfb5700ce 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 80a5db4817 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 6a3740697b 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new a701706b56 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new d6065a8ff5 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 909245781e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new c0219e1f1b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 7c397071aa 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new c2376a2aa0 128: onsuccess: #1723: 1: Success after linux: 12 commits new c64610416e 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 15da311af1 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 46e94c8beb 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 6644b68643 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 1f78420c3b 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new de1d046ec3 134: onsuccess: #1730: 1: Success after binutils: 2 commits new e7d8b7fd80 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 16009aeeec 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 6dc03c21d0 137: onsuccess: #1736: 1: Success after gcc: 5 commits new fede1f1a11 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new b93b64adc8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new a60cdeb593 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 6587909b08 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 6ccdc449c1 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new cbad4cfdf3 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 5e6ce1894f 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 739c705dbb 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 7996c53f8c 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/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 (b3a3eda6d3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]

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 1696 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29976 -> 30516 bytes 04-build_abe-stage1/console.log.xz | Bin 90404 -> 90712 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 9304 bytes 07-build_abe-glibc/console.log.xz | Bin 233500 -> 233952 bytes 08-build_abe-stage2/console.log.xz | Bin 223708 -> 223188 bytes 09-build_abe-gdb/console.log.xz | Bin 37104 -> 37624 bytes 10-build_abe-qemu/console.log.xz | Bin 31188 -> 31424 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2784 -> 2732 bytes 13-check_regression/console.log.xz | Bin 6116 -> 7968 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 14 +- 13-check_regression/mail-body.txt | 65 +- 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 204 ++- 13-check_regression/results.regressions | 38 +- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 67 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 38 +- sumfiles/g++.log.xz | Bin 2662716 -> 2686552 bytes sumfiles/g++.sum | 123 +- sumfiles/gcc.log.xz | Bin 2225572 -> 2197536 bytes sumfiles/gcc.sum | 2142 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 883416 -> 892680 bytes sumfiles/gfortran.sum | 7 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201160 -> 201096 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 421504 -> 432276 bytes sumfiles/libstdc++.sum | 8 +- 44 files changed, 1633 insertions(+), 1237 deletions(-)