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 1139d8ac3b 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 463c766e66 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards bc891b5142 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 3b5f35ecd7 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 9d218c2a3d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 80aa576bab 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 39f72b6698 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 158071ea41 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards b9632f663a 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 8ed8d32624 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards ca4d6a6510 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 0da1a44124 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 0e23b05463 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 671003c5c2 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 866dbb0d68 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 5ca3ee394e 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 9b0b1126ab 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 334d891da9 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 4a37007b09 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 0f9d9b1723 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 4a14d4b46d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards aebdf38b4d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 0579d8a661 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 54a61dbdbe 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards e24f858d82 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 6e2493710e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 9bbe76e978 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards b466195bda 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 5484c39d43 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards d47cdf8ccd 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 6d85b2fc45 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 41126571a4 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards b6061acb2c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 3c88a53a57 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards a7855cdba0 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards c315f8eac1 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards e11aeb06fe 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 98eb215c0a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 63b0fbbfd9 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards f77a9b92ad 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 5e8f5447f0 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 88ee46ad07 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards faffd6ae1a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards fbd01253f9 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards c5619311d7 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 71d9cb2fb1 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 0fe6f1395d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards a54dbe5655 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards a708f21d00 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 0ec5dda0d4 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards b661267529 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 8a251fcaed 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards c109b84786 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards f41b4ee6bc 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 78563de238 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 0c43d5dc4c 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards a0fa58a3d4 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 72e536a5e6 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 53151de7f2 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards d89313c804 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 215f852926 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards a1c6a74bbd 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 12a022585a 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 5e28550051 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 03c0446036 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards be06f36853 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 373f42b739 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2020e67970 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d7151ff46f 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 9b340b71e9 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 92128c097f 74: onsuccess: 1: Successful build after linux: 44 commits discards d9349784b2 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 98fd3995e7 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e3486a7870 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 90433f65c6 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 42892ec333 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 041a5ce933 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 60a24b5f50 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f63fb509da 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2f7cb3b3ef 65: onsuccess: 1: Successful build after gcc: 4 commits discards 507147954a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 91df097aa8 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f0f5b3b4c8 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 9d0884c8fa 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b0a4cf828c 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 0cedca4746 59: onsuccess: 1: Successful build after glibc: 2 commits discards 89cfa01365 58: onsuccess: 1: Successful build after binutils: 2 commits discards 8f26877a37 57: onsuccess: 1: Successful build after gcc: 7 commits discards 63acfad8e2 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 943dae5422 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b72b8a190c 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 5e2f7eacd0 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 544e84aabe 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 76f85c34a9 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 694635dd55 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0ba2e9e9ec 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b35490f38b 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 0220b075c2 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 554f22c21b 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 2e71989c2b 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d2d281ad8b 44: onsuccess: 1: Successful build after linux: 34 commits new 1920b959e7 44: onsuccess: 1: Successful build after linux: 34 commits new 91792a0685 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5610f5c660 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new f9144999a3 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ce30b6eb82 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 10901925c3 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4823d07ac3 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 113e03b9bf 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1d58eee885 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 59cf0a1927 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 42e9663b57 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new c9d7f03c01 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 10e868562e 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3371a33d13 57: onsuccess: 1: Successful build after gcc: 7 commits new 157e52e7e5 58: onsuccess: 1: Successful build after binutils: 2 commits new 8145fb89ef 59: onsuccess: 1: Successful build after glibc: 2 commits new 9c69f3243d 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 46a063874e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 550f38123f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new ea8e97acf3 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4c7fca1d0f 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5b980fcdc4 65: onsuccess: 1: Successful build after gcc: 4 commits new 8653184f9d 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7a0f5e6848 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b498021980 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 45a8afc39f 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 652bc1f8f0 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 9e0c672c91 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 480ee871f6 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c872ba969c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 564dd1b825 74: onsuccess: 1: Successful build after linux: 44 commits new b729e6ff33 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c7574b31e6 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 23163b8a6e 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ffa685b59c 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d2d515a769 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c75900cec8 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new a5b9795816 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 568f9af514 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new cba390dde4 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 551455183a 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 413adb07e2 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 25350e8523 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 0d0de87a90 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 349e2f6b7e 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 740efe8f33 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new e2d0c4c5b1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 67eca9c795 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new fe4a1797fc 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 6a645fd8af 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new c7382f5076 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new c371120b3b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 50f5454927 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 9cb4f6456e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new c8cec07c41 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 265f9593f9 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new a1d28eb9f7 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new b779edb46e 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 30a6d55f2c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new f3d583b9e0 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 8b5b1bfdf8 104: onsuccess: #1697: 1: Success after gcc: 4 commits new d3a210355a 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 7a85376ae6 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new fbe9ae9613 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new ddb8cc6711 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new e3d833e7ac 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 24178bf72c 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 91d5299be2 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 76bbe6403c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 3c628c7570 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new a10cbad86f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 74cda48d2c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 12a8623527 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 6bfa4391a1 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 478311b062 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 8c362f4a71 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 3d6e6fd3e1 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new e6e1039018 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 9abae44c4e 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 41e460cbfb 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new a60d90b19a 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new a56e504664 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 600564e810 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 351fbd6001 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 73d756dc16 128: onsuccess: #1723: 1: Success after linux: 12 commits new 47f5b4b18a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 79634f672f 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 4ef8f496eb 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new a197939054 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 4c0a87fef4 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 4547d0653d 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 2027e73ee8 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 274efb7543 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 98585fa269 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 82e0cf73e0 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 1247ce43f5 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 604ea28b7d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 6c7b32e490 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new ef3940e156 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 48281eb9fc 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new cd1476d2ff 144: onsuccess: #1743: 1: Success after glibc: 2 commits new b3a3eda6d3 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...]
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 (1139d8ac3b) \ 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 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30072 -> 29976 bytes 04-build_abe-stage1/console.log.xz | Bin 90416 -> 90404 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 233824 -> 233500 bytes 08-build_abe-stage2/console.log.xz | Bin 223580 -> 223708 bytes 09-build_abe-gdb/console.log.xz | Bin 37208 -> 37104 bytes 10-build_abe-qemu/console.log.xz | Bin 31400 -> 31188 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2444 -> 2784 bytes 13-check_regression/console.log.xz | Bin 5344 -> 6116 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 + 13-check_regression/mail-body.txt | 53 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 65 +- .../results.regressions | 60 +- 14-update_baseline/console.log | 40 +- 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 | 55 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 27 + sumfiles/g++.log.xz | Bin 2656996 -> 2662716 bytes sumfiles/g++.sum | 53 +- sumfiles/gcc.log.xz | Bin 2191892 -> 2225572 bytes sumfiles/gcc.sum | 2310 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 881792 -> 883416 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201280 -> 201160 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427888 -> 421504 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 1400 insertions(+), 1360 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy mail/mail-body.txt => 13-check_regression/results.regressions (73%)