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 7996c53f8c 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 739c705dbb 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 5e6ce1894f 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards cbad4cfdf3 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 6ccdc449c1 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 6587909b08 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards a60cdeb593 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards b93b64adc8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards fede1f1a11 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 6dc03c21d0 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 16009aeeec 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards e7d8b7fd80 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards de1d046ec3 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 1f78420c3b 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 6644b68643 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 46e94c8beb 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 15da311af1 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards c64610416e 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards c2376a2aa0 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 7c397071aa 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards c0219e1f1b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 909245781e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards d6065a8ff5 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards a701706b56 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 6a3740697b 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 80a5db4817 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards ccfb5700ce 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 2c5fd9bb5d 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 53627e4b34 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 9e98615099 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 76522a1c0b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards f9f31138c8 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 045e7b7fb8 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards adeeff7331 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 7222ddfb0d 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 8212db00b8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards fe47d65218 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 30a36b8540 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 8760599bd1 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards ca7fcbdea8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 907732a504 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 19bdf680a5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 264aa95cd9 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards db22686902 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards f992c6572c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards d628d5127a 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 23f1aef86f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 226cec3118 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards bb282dce99 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards ec659cdee8 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards e2b38ff740 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards cc510d185a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 78f7bf282f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards a2fd076206 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 808990ea28 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 0dc4d64e6b 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards ab30ed6397 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ebf56773e8 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d655b06a79 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 8a65161d44 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 3a79cedd21 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 036d4d5364 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards fe2d0d83b6 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards fc19e06693 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 271d055af0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 8e8c1d71d4 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c6298a144f 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 95b18aacee 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 9ce174d9f2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cbfd730abe 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ae15d47665 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards aea051dd27 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 157b000514 74: onsuccess: 1: Successful build after linux: 44 commits discards e2a4a23607 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards eef49b0ea7 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 142516c4d7 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 8cfac98ff2 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 6f93a8d30c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards d3cc8d7dcc 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 428c30c822 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ddc33ed6a8 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3650eddc40 65: onsuccess: 1: Successful build after gcc: 4 commits discards 129adc366a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 55283022a5 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1eae0ffe7c 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 8c9722a4ad 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 3fc39d8472 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b80a79b835 59: onsuccess: 1: Successful build after glibc: 2 commits discards 902919300f 58: onsuccess: 1: Successful build after binutils: 2 commits discards 8f04b89c3e 57: onsuccess: 1: Successful build after gcc: 7 commits discards 68d266ba97 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c00abce9ce 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 839cb53b5d 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 13a2a06b7b 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 01e61b996c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 9599ed7bec 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 063fb4f889 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a3cde4271c 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 362c3425d0 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards dde93d3159 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cd7c0358bb 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 91ca2f5b68 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 3010bda873 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 08bb27195c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 50419f56f5 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2108ac35b2 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bd4737eab6 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 62e3e38940 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new edd36246de 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 0531b34a39 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 45a8c35d78 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2fba437416 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4504a5d491 57: onsuccess: 1: Successful build after gcc: 7 commits new cfa78e3f0d 58: onsuccess: 1: Successful build after binutils: 2 commits new 472e50c11f 59: onsuccess: 1: Successful build after glibc: 2 commits new 2eb13c4887 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e78e9c869f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 3abdb8b078 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new f0f37f1557 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ce88bf9163 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9a15510758 65: onsuccess: 1: Successful build after gcc: 4 commits new dcaa6d8185 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bc0630a88b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 150a6b0a0e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 179e926b6b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 19cd1b5966 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new dc6c91118a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 84ca4c0489 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7222fb6191 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1c5bb0c3b8 74: onsuccess: 1: Successful build after linux: 44 commits new 2f9e476809 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 15f279974e 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new e7d50687ec 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5e7bab3c95 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2fa0f36625 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c869ca023d 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new ac6ac3e0c8 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 2ab5f7bfe0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new bd45238dcf 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 5fad5a2d39 84: onsuccess: 1: Success after gcc/glibc: 9 commits new ba8d7aaf69 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b3e2bdceba 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 89d4295089 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 2af8bf8a20 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new f424cb1249 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 41424d79b5 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 7cb8d33dec 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new d4a5d9b33e 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 98c92eeefe 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new cdbe3ca52c 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new ba8dc622d3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 11e749815b 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 7bd818a9a1 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 4357bc2c00 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new fa39ebdc74 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new bce34a74bf 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new e7372ac4cf 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 6a190a5c77 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 00a3d15faa 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 6e38b16556 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 9ec49e605c 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new b8b9830ddc 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 3ce2a181d8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new d0ab181c7e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 829786e21f 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 3c1841be1b 110: onsuccess: #1703: 1: Success after gcc: 6 commits new e7fba326bf 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 95c76b2b10 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new ed8bb9ecdd 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new b882bf8dfd 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new a4d5662b2a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 69bedf934e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 9661acff43 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 1d93f05c60 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new d5bceed6b3 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new ac7d577305 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new cd3984760d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new e4a565b4b6 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 97c7b954bf 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 39f03e09b1 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new ed8d9c139c 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 5592b86198 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new ec48df4b0c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new e7d3a46864 128: onsuccess: #1723: 1: Success after linux: 12 commits new 6c28f0b41c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 339164b8aa 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 3cacbb311e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 32835372e2 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 32c715c6b4 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 10638ef600 134: onsuccess: #1730: 1: Success after binutils: 2 commits new de9aad1186 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 78fb0aa2e8 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 2c92c18364 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 9c2dc5a22c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 9a612caa9d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 10dfc2d8cf 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 756d0ee525 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 669554203e 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new fdd4cb18ad 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new a4a5a708bc 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 616028e5cf 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 874198af85 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 6e01019417 147: onsuccess: #1746: 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 (7996c53f8c) \ 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 1680 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30516 -> 29912 bytes 04-build_abe-stage1/console.log.xz | Bin 90712 -> 90360 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9304 -> 8432 bytes 07-build_abe-glibc/console.log.xz | Bin 233952 -> 233124 bytes 08-build_abe-stage2/console.log.xz | Bin 223188 -> 223648 bytes 09-build_abe-gdb/console.log.xz | Bin 37624 -> 37240 bytes 10-build_abe-qemu/console.log.xz | Bin 31424 -> 31424 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3844 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2732 -> 2428 bytes 13-check_regression/console.log.xz | Bin 7968 -> 6528 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 13 - 13-check_regression/mail-body.txt | 69 +- 13-check_regression/results.compare | 46 +- 13-check_regression/results.compare2 | 242 +-- 13-check_regression/results.regressions | 47 - 14-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 71 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 47 - sumfiles/g++.log.xz | Bin 2686552 -> 2671680 bytes sumfiles/g++.sum | 133 +- sumfiles/gcc.log.xz | Bin 2197536 -> 2236828 bytes sumfiles/gcc.sum | 2636 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 892680 -> 889400 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201096 -> 201272 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432276 -> 433956 bytes sumfiles/libstdc++.sum | 10 +- 44 files changed, 1635 insertions(+), 1842 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions