Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (f08d80e754 -> ca20ffa86c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards f08d80e754 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] discards 27244c2094 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] discards 5f72fd1772 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards b140feaf4d 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards a5f8028493 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards 81832dbab0 152: onsuccess: #903: 1: Success after linux: 22 commits discards 19d8d325cb 151: onsuccess: #902: 1: Success after glibc: 8 commits discards a0e1191bf9 150: onsuccess: #900: 1: Success after gcc: 11 commits discards b186e434a5 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 8c7ac9330a 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards 0b2ff656db 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards edddd2f8ea 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards cc02fa5d52 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 9355c2b91a 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 649ae8c297 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards fb4203398b 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 127bbdb7cc 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 1c8e5d9060 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 872f6c79eb 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 9d71f5c060 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards e94d02bfb1 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards e7d3d5ff93 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards f0a1e09709 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 10cdf8f5d1 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards f436131b53 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 764dc75fe3 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 34e997931b 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 68b536b044 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 743bfdcdea 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 2a01f95847 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 6f7b3a9b32 127: onsuccess: #874: 1: Success after linux: 219 commits discards 9c39293bef 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 08de00abf1 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 85174854fe 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 5203f45d72 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards e4314a84e9 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards d336250985 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 922e388771 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 806007dbe6 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards f11f58bfbb 118: onsuccess: #863: 1: Success after linux: 12 commits discards 347c8fa622 117: onsuccess: #861: 1: Success after binutils: 18 commits discards d8676dc079 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 064998585f 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards a2e9ae36a9 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards ffc81eff86 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 50e9f22642 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 34ad7c0ab6 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards ccd2f10d63 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 288a56f0af 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 3bee965fe4 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 0059e2a44e 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 07cb33288f 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 210ba9722a 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 3913e57a99 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 07e60e9951 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 436b151be3 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards b4195d6c0f 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards d6c1f7fc50 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 1d8c80fb56 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 985a464399 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 33110b8517 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards bd44758b13 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 9208058600 95: onsuccess: #835: 1: Success after binutils: 3 commits discards ed1b744bf5 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 5300aa903a 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards c47fdda8d1 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 7e4c3e8d27 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 2577fdb095 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 3a6667c38b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards a0b586b1ef 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards c34d254d74 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards a660a49063 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 9921648a69 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 0f9342d8f4 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 4f83b75dcf 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards f0f8160781 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 85fdf5363a 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 464f5020bf 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards cfd164c94c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 23d2a4fa8a 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards d43223910a 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards ebd53a99b4 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards d594343d3d 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 803db77a92 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards a4190a50b6 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 9dbe2813a8 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards ecf11f1a65 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 91d196749f 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 59d2791935 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 1b7378b957 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 90d2c3fae1 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 1aa973902a 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 821a35a79c 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 09cbe8d2d7 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards b6f98abc6a 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards cbb02519a3 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 2432a9e3da 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards b37382cef6 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 7485d3d220 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 51fc59de83 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 316cce851c 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new d6276e3d80 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 1ffe945b11 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 98bd9109d3 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new c5f0d3ccf2 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 54a4fff6c4 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 95e87f1546 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 3a14805787 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 6e751ea6aa 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new edf38fdd06 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new ae99759983 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new ed92eab36c 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 24314a4669 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 2558995dd0 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new e5d36ae38e 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 7af19e07e1 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new a83f5a4557 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 59ec1026eb 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 98e6345cee 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new c30931edb0 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 7477af49c7 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 3ba0919ac2 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 1e39524560 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 6c0aae16bb 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 84d9da20a9 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new a823617fc7 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new e85d037aa2 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 60bc26c86e 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 8390d85428 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new a3ec215a5b 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new db391896f0 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 5cd22ff804 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 74d74d4ab3 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 656f95d6cd 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 09b085bc31 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 5085772ef3 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 1546b5b34f 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new bb799c4cd2 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 54e7f8fca5 94: onsuccess: #832: 1: Success after binutils: 5 commits new 031244154d 95: onsuccess: #835: 1: Success after binutils: 3 commits new d5626a95fd 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new ae46d63fef 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new d58ab3bd53 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 6af3f4f8e6 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 1e512224a9 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new fd7655521e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 74ebcc5a24 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 62cc949475 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new f726184637 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new f05af8315a 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new fdb3aca946 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 4a98992bce 107: onsuccess: #849: 1: Success after binutils: 5 commits new 7af7543a81 108: onsuccess: #850: 1: Success after gcc: 2 commits new b1439aebc3 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new d3c0255e9e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new c530f97249 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 445622230c 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 32930f9379 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 1d1a0dcae6 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 32ab78759c 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new cb52e787fc 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 5728fc2690 117: onsuccess: #861: 1: Success after binutils: 18 commits new 2f62cf6626 118: onsuccess: #863: 1: Success after linux: 12 commits new 41c02868c4 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new ccb2702a22 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new a183d4a239 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new e3ef35171a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new e6a71289e5 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 6f37cb8f05 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new b921d73f89 125: onsuccess: #871: 1: Success after binutils: 26 commits new 2153d1d816 126: onsuccess: #873: 1: Success after glibc: 2 commits new 58f7c746d2 127: onsuccess: #874: 1: Success after linux: 219 commits new b4b14752b1 128: onsuccess: #876: 1: Success after binutils: 12 commits new 5e14b080d0 129: onsuccess: #878: 1: Success after linux: 3008 commits new 7bdd977de0 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new d86fe65ca5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new f7922e2e84 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new f0f78a1482 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 1326050cd7 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 12f71f01d3 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new a56fdee8f6 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 571267052a 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 67dbee9faf 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 97d1ad7375 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 50837cc2a2 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 9254847ddb 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 1e22e7139c 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 6c041b78c3 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new fc9fe679e2 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new a46fcc696b 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new b28441fd92 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 58df207f66 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new 5ce1bf8f1c 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new 79c97a1148 149: onsuccess: #899: 1: Success after binutils: 15 commits new 828bd8108f 150: onsuccess: #900: 1: Success after gcc: 11 commits new a7b7991f47 151: onsuccess: #902: 1: Success after glibc: 8 commits new 8451edf039 152: onsuccess: #903: 1: Success after linux: 22 commits new ea081b9422 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new 1e97c74d0e 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new dc8b096d68 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new 12d1dd5abf 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] new 34bf0f6c1c 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] new ca20ffa86c 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] 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 (f08d80e754) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] 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 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 39652 -> 39756 bytes 04-build_abe-gcc/console.log.xz | Bin 215016 -> 215296 bytes 06-build_abe-linux/console.log.xz | Bin 9104 -> 8548 bytes 07-build_abe-glibc/console.log.xz | Bin 245220 -> 244148 bytes 08-build_abe-gdb/console.log.xz | Bin 39484 -> 39564 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3884 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3156 -> 2364 bytes 11-check_regression/console.log.xz | Bin 6660 -> 6396 bytes 11-check_regression/fails.sum | 4 +- 11-check_regression/mail-body.txt | 42 + 11-check_regression/results.compare | 15 + 11-check_regression/results.compare2 | 37 +- 11-check_regression/results.regressions | 15 + 12-update_baseline/console.log | 46 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 15 + sumfiles/g++.log.xz | Bin 3742772 -> 3728756 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 3299336 -> 3297940 bytes sumfiles/gcc.sum | 4910 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1087712 -> 1078372 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 232008 -> 232200 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 457476 -> 455484 bytes sumfiles/libstdc++.sum | 2 +- 40 files changed, 2678 insertions(+), 2528 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (0089bac4ce -> 4f4b078198)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 0089bac4ce 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 28a7512df3 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards b7f906de7c 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 2d80f63085 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards 04aef8b811 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards eabea31e96 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 6b09e22cd4 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards dd9c274b11 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 69cea8253c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 42817d95c1 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 6bd2526cfc 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 1b89f0a965 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 6770b163ad 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 7140a5b4ec 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards d83dfc5433 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 1d523d3797 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards b1c600c199 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 2fc3d5d6e1 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 3988ebf686 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards ec6db4914b 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards fd999a18af 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 3df0c8a896 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards f6dbc87dd2 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 017a2feab3 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 33eba66d5c 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 1596047761 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 69a83d3f42 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards dab65adebe 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 53e8c78603 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 5b928dab8f 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 0b49138b19 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 0a1f2cfaf0 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 17a153b801 125: onsuccess: #614: 1: Success after linux: 12 commits discards 79285ff9c2 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 94defd3732 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards d4db8ebbe4 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 2c2bbebee4 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 75a4d8a98a 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 3dd023e0e8 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 966d8614a0 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards cfe7b3f8c3 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 041646730c 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards ef8817a135 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards d23bea1cf7 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 86c889080d 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards d8512567fa 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 0963878ee3 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards c9d08c8c43 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards edc850c344 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 8658f8f36f 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards f32fcc1cfb 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards ff27643755 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards fe1735d75b 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 1ec2e4b948 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards a3af7c1dc9 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 3aab742e4f 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 2bdd768534 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards a8673df144 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards bb9954faba 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards d4a1056920 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 6c4e1e7c23 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 8b95b9b3fe 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 6af01da432 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 633e38045a 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 1ef001b59d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 03cc324b15 92: onsuccess: #575: 1: Success after linux: 34 commits discards fcaacc0d9d 91: onsuccess: #574: 1: Success after glibc: 3 commits discards babd637a25 90: onsuccess: #572: 1: Success after binutils: 15 commits discards aebbd21e30 89: onsuccess: #570: 1: Success after linux: 11 commits discards 9ac66e9eb5 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 3d1113d9ce 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 7f7d9bfb98 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 48fe21d8f2 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards b0986d2edd 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 54a82a46e1 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards cf6491b419 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 62350a64ae 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards ece61495d2 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards fae05fb285 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 8630d88a29 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 8551e1ebb3 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 9e1be45622 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 7342fd1705 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards c73bc6ae79 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 78e336b680 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 02576d125a 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 712fa8aef2 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 1b8c65c3cf 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 973634e750 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards a56ef4f4e3 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 93601b100e 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards d0b9d984c8 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 437f614fca 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards fedaf60eda 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards ce4031e0d0 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 583d8cdec4 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 9574fc109d 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 9e31fec863 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 12a84e0f3b 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 927e3419c5 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 4d0950558d 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 2272b0f783 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 0a3d3556e5 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new a859185d90 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 9a3089f777 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new 2149c283ba 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new a34fe0ac89 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 924cdc4e23 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new e97c7f8e4f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 87bc07e5e9 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new c904efcd53 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new ca191f660c 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 15ff2e9c92 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new e3b509b3a8 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new e99961b78a 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new b710e34893 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 3d4a26df70 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 5dc294bf8d 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 81e4a32b1b 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 31de458dee 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 3c0b93572c 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 62c4449484 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 98268be0ba 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 97b3c138bf 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 8d984e1a7c 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 9a8f1dce37 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 1f42c945a1 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new ebbc418d0b 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 5210f033df 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new f86184cd60 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 587d1b65c8 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 40495f2c79 87: onsuccess: #567: 1: Success after binutils: 8 commits new aa56c828b9 88: onsuccess: #569: 1: Success after glibc: 10 commits new f60af8199c 89: onsuccess: #570: 1: Success after linux: 11 commits new 98638c9beb 90: onsuccess: #572: 1: Success after binutils: 15 commits new acc490ef17 91: onsuccess: #574: 1: Success after glibc: 3 commits new b2e23a812b 92: onsuccess: #575: 1: Success after linux: 34 commits new bd7a3683f2 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 81311c6390 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new fd67d2bf9d 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 0f1e703fa4 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new bba4b5429b 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 0b2a16f802 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new e6c51a5d58 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 3cea43d5ff 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 6c75477af8 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new c7539f646d 102: onsuccess: #586: 1: Success after binutils: 5 commits new da3e89376a 103: onsuccess: #589: 1: Success after binutils: 3 commits new d069c4ca57 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new def2fb6cb7 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new ae03c7db6b 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 38c207fbc2 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new fc255eec67 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new aa8549445a 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new b7b8883a62 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 23de232783 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new c19c06693b 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 677a1425ef 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new a1ba8c4421 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new bc2049ba6f 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 4bac94abf1 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 59eb1b6243 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 2e79bc64c9 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 19bfcd617b 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 7524bff372 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 8442384c60 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new da370a6294 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 265d0a69e5 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 92800b7753 124: onsuccess: #612: 1: Success after binutils: 18 commits new 6f7c12e384 125: onsuccess: #614: 1: Success after linux: 12 commits new 6345a01541 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 70ad50d6a4 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new c5fc9a30b6 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 62314e83fc 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 67a9382f52 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 334359832b 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new fab23ed906 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 74ceb12058 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new a78cf922a5 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 1696ee5748 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 516e34a9f7 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 06213c7c32 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 0464894aff 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 2bc9f9d3a3 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new cca1db3309 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 4b8dbd4894 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 0ec76b93fb 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new bce77df680 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 187d4bf4f4 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new f40e81a78a 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 68afd5e4b3 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new e5b03cc367 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new e4ac0bda4b 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new fd126d840d 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 30c1cff544 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new bc40cbac4a 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 6ed1b679a7 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new 62f3e8126a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 27e16d2511 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 073ea9d837 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new eee30d10e2 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 451a6e640a 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 4f4b078198 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] 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 (0089bac4ce) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 1732 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 52776 -> 52828 bytes 04-build_abe-gcc/console.log.xz | Bin 237864 -> 237620 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9048 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 235880 -> 236032 bytes 08-build_abe-gdb/console.log.xz | Bin 51508 -> 51784 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3856 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2144 -> 2208 bytes 11-check_regression/console.log.xz | Bin 9132 -> 14724 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 39 +- 11-check_regression/mail-body.txt | 180 +- 11-check_regression/results.compare | 100 +- 11-check_regression/results.compare2 | 3647 ++++++++++++- 11-check_regression/results.regressions | 100 +- 12-update_baseline/console.log | 62 +- 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 | 182 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 100 +- sumfiles/gdb.log.xz | Bin 1706020 -> 1845144 bytes sumfiles/gdb.sum | 8820 ++++++++++++++++++++++--------- 30 files changed, 10180 insertions(+), 3098 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (f9542deb98 -> 684b35311b)

by git＠git.linaro.org

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-aarch64 in repository toolchain/ci/base-artifacts. discards f9542deb98 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards c2de5ebc1e 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards 789ea81bc4 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 09e00ec94d 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards 808ce6d9d1 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards 82f3997cfc 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards f67ab49612 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards 183b2bd556 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards ed5c6bee37 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 052f4d34d9 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards c7fc4402f7 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards 0ee404037c 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards ec24dcefb1 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 2702317006 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards 2253dae359 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards 7f4b5830ae 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 08ea637b00 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards 196c1bb7b4 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards 8ca601ab55 305: force: #2006: 7: Success after gdb: 2 commits discards 40cda0079f 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards d77c990835 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards 14a665b99d 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards 71e2dde420 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards 430258c228 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards af97ea7b60 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards 841c8a2f75 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards 436a323f0e 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards 910dbd22f6 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards a9616637cd 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards cc5b510bb8 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards 83f486de70 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards d7c367cc81 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards c534ac0e1d 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards 30e6510661 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards 167905d59c 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards 12a6427289 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards 4094cbd190 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards f4d2f5aff6 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards 907a1aa2b4 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards cc6d85345e 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards 7b9bc88a91 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits discards 52ba6da5dd 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] discards fcbca93ce9 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] discards b0782f8bcf 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits discards 37c851f0a5 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards 68bcb2d72e 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards 99c814d6b8 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits discards dca23e298f 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 7501b4dd44 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] discards 95fd4aec04 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] discards a1a913570a 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits discards 26b3c79610 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] discards 16b6541b5e 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] discards 62ed3ace2b 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] discards 5f6324dc9f 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] discards 724fdae777 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards 5da2811900 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards 60b0d654a4 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards 92c5ff1fb6 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards 50951108e0 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards fa5628d417 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards 2d9594ae4c 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards fa19df5bdb 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards a0f72c9eab 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards 749818d642 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards 26ae237d1a 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards 359cff54de 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards f96f284e49 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards 49d57d8c66 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards 175a5d3f35 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards c4ed031b2c 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards 2d34e6a31a 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards 00ff6a30af 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards bb67716db8 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards f5a52469d1 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards acf5fe9c12 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards c6e9ff86e4 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards ca11928d83 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards 29c7713032 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards 45dc9fa138 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards 050e48f0cc 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards 030738e13a 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards c661294629 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards e3e96569d4 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards d533a6822d 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards 37d2d72f13 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards 9205847cc9 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards 4252d7f176 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 06846c3815 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] discards a47aec6af7 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] discards 298d1f3c60 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] discards efcfc8676b 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] discards bbad75ec01 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards 91f3fe5695 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] discards 01eb1b9365 229: force: #1926: 7: Success after gcc: 7 commits discards beffb74879 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] discards 6bed4bc3a7 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards 2c9931a569 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] discards 30e14c3d98 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] discards e2de3970cd 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] discards 153a3b88b1 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] new b92528f7f4 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] new cf8954648f 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] new 162dbc7f02 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] new 210340d69a 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] new ec2fdc4c26 227: onsuccess: #1906: 7: Success after binutils: 9 commits new 917d3ffe7d 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new f0455026d9 229: force: #1926: 7: Success after gcc: 7 commits new ee0200c064 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] new 076bc41015 231: onsuccess: #1928: 3: Success after gcc: 8 commits new a169f1a07d 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] new bb1e9bfc43 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] new 80f0c0d4f7 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] new 327717c567 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] new 0687a7c183 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new c4fcea23d6 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new 0163e9ff3e 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new e85e5d5911 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new c0a4baff9c 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new ce25bed0c2 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new f7ddd31f8e 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new fd69cead9b 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new 8e5d5fbfb5 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new 86d6d43c00 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new 9478e6d206 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new 2484369d30 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new ea328a5118 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new fbdb6b3c79 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new ae1f09d0b8 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new 3582af8c3b 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new bc031bfbbe 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new 2898e3936c 253: onsuccess: #1950: 7: Success after glibc: 2 commits new 5c25799577 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new a5c6425a3c 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new 5b076c6d8f 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new d23a254076 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new fccd8713b2 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new 5ccab47be1 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new dc0a62aeed 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new bf1912c764 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new 6a58bc0db9 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new fb9754054f 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new 2f1b6654ff 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new a522ec48b0 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new d283975c18 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new ee0b5fd010 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new c28898246d 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new 952e480e75 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] new e6687397bc 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] new 885786fd68 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] new 2e033d9c4c 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] new b239c61ce2 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits new 6c0206ebb4 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] new 31c3fd2244 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] new 7f1295c1bf 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new bca60b3116 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new 4831257dfb 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new a792ccd4e4 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new 86bc8a5c3d 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits new e91e8353cf 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] new 0dab7b9b7f 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] new 9c12ab41b2 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new 6af8e54561 284: onsuccess: #1981: 7: Success after gcc: 2 commits new 9eb88643a2 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new ef1a590c4e 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new 5db50b6e88 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new 38d2fd3fb5 288: onsuccess: #1985: 7: Success after gcc: 17 commits new bd03d9280f 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new 7ddc082390 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new 116a35d934 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new 854f5c1c11 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new e198e8bdf2 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new a40d173ce5 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new 5720e3ee25 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new d4333562bc 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new 52ca1b6e61 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new 4a7556aafc 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new a21334466b 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new b334d9b426 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new 0613c86b54 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new 1480ef2aeb 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new fbff3e2228 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 40164631c4 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 8fc140a735 305: force: #2006: 7: Success after gdb: 2 commits new 94a950a44b 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new efb538ee36 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new 12cf98e168 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new c1487fb419 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new 30c1f36a15 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new 44b8fd8abd 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 88260756eb 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new b6661f97d6 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new da73b429e4 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new 1ab6d6a211 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new f1eac3ae36 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new aa454a93e6 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new 1b3bc1b7de 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new 34a0dda3a5 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new b2c94c77af 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new 6e27ff670a 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new 642148c4f1 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new aa125a5d80 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new 684b35311b 324: onsuccess: #2025: 7: Success after linux/qemu: 35 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 (f9542deb98) \ 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 1768 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2804 bytes 04-build_abe-binutils/console.log.xz | Bin 32352 -> 32452 bytes 05-build_abe-stage1/console.log.xz | Bin 73516 -> 74280 bytes 07-build_abe-linux/console.log.xz | Bin 8684 -> 8716 bytes 08-build_abe-glibc/console.log.xz | Bin 245232 -> 247268 bytes 09-build_abe-stage2/console.log.xz | Bin 205828 -> 208168 bytes 10-build_abe-gdb/console.log.xz | Bin 40696 -> 40404 bytes 11-build_abe-qemu/console.log.xz | Bin 31692 -> 31572 bytes 12-check_regression/console.log.xz | Bin 3864 -> 3724 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +++++++-------- 18 files changed, 52 insertions(+), 52 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_tk1/gnu-master-arm-spec2k6-O3_LTO updated (80b9f2d245 -> 44460a8d49)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_tk1/gnu-master-arm-spec2k6-O3_LTO in repository toolchain/ci/base-artifacts. from 80b9f2d245 45: force: #12: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...] new 44460a8d49 46: force: #13: 1: [TCWG CI] 481.wrf failed to build after g [...] The 1 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 1816 -> 1840 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31964 -> 32936 bytes 04-build_abe-stage1/console.log.xz | Bin 92572 -> 93540 bytes 06-build_abe-linux/console.log.xz | Bin 8092 -> 8212 bytes 07-build_abe-glibc/console.log.xz | Bin 237592 -> 239944 bytes 08-build_abe-stage2/console.log.xz | Bin 213520 -> 220176 bytes 09-benchmark/benchmark-build.log | 112 +- 09-benchmark/benchmark.log | 110 +- 09-benchmark/console.log.xz | Bin 4032 -> 4024 bytes 10-check_regression/console.log.xz | Bin 6152 -> 6940 bytes .../csv-results-vs-first-1/perf.csv | 180 +- .../csv-results-vs-first-1/results.csv | 179284 +++--- .../csv-results-vs-first-1/size.csv | 517455 ++++++++-------- .../csv-results-vs-first-1/vect.csv | 31 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 184 +- .../csv-results-vs-prev-0/results.csv | 85434 ++- 10-check_regression/csv-results-vs-prev-0/size.csv | 566388 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/vect.csv | 38 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 180 +- .../csv-results-vs-prev-1/results.csv | 179284 +++--- 10-check_regression/csv-results-vs-prev-1/size.csv | 517455 ++++++++-------- 10-check_regression/csv-results-vs-prev-1/vect.csv | 31 +- 10-check_regression/exe.improvement | 1 + 10-check_regression/exe.regression | 2 +- 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/jira-body.txt | 2 +- 10-check_regression/mail-body.txt | 2 +- 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 188 +- 10-check_regression/results-vs-first-internal.csv | 80 +- 10-check_regression/results-vs-first.csv | 80 +- 10-check_regression/results-vs-first.log | 1389 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 2 +- 10-check_regression/results-vs-prev-full.csv | 192 +- 10-check_regression/results-vs-prev-internal.csv | 80 +- 10-check_regression/results-vs-prev.csv | 80 +- 10-check_regression/results-vs-prev.log | 1621 +- 10-check_regression/results.regressions | 4 +- 10-check_regression/trigger-bisect | 3 + dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../410.bwaves/results-metadata.json | 10 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../434.zeusmp/results-metadata.json | 10 +- .../435.gromacs/results-metadata.json | 10 +- .../436.cactusADM/results-metadata.json | 10 +- .../437.leslie3d/results-metadata.json | 10 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../447.dealII/results-metadata.json | 10 +- .../450.soplex/results-metadata.json | 10 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 10 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../471.omnetpp/results-metadata.json | 10 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-functional.json | 4 +- .../squad-vs-first/481.wrf/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 - .../482.sphinx3/results-metadata.json | 10 +- .../483.xalancbmk/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/Mean/results-metrics.json | 2 - dashboard/squad-vs-first/dashboard-push-squad.sh | 126 +- dashboard/squad-vs-first/summary-annotation.txt | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 10 +- mail/mail-body.txt | 10 +- mail/mail-subject.txt | 2 +- manifest.sh | 17 +- results | 4 +- results_id | 2 +- 93 files changed, 995382 insertions(+), 1055151 deletions(-) create mode 100644 10-check_regression/exe.improvement create mode 100644 10-check_regression/trigger-bisect -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_fx/llvm-master-aarch64-cpu2017rate-O3 updated (9dc5db4665 -> 12f1eabe82)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_llvm_fx/llvm-master-aarch64-cpu2017rate-O3 in repository toolchain/ci/base-artifacts. from 9dc5db4665 40: force: #8: 1: [TCWG CI] 520.omnetpp_r slowed down by 11% [...] new 12f1eabe82 41: force: #9: 1: [TCWG CI] 520.omnetpp_r slowed down by 14% [...] The 1 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 1996 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32196 -> 32432 bytes 04-build_abe-stage1/console.log.xz | Bin 73424 -> 73424 bytes 06-build_abe-linux/console.log.xz | Bin 8824 -> 8824 bytes 07-build_abe-glibc/console.log.xz | Bin 244968 -> 245028 bytes 08-build_abe-stage2/console.log.xz | Bin 178228 -> 178352 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 64108 -> 63932 bytes 10-benchmark/benchmark-build.log | 88 +- 10-benchmark/benchmark.log | 86 +- 10-benchmark/console.log.xz | Bin 4000 -> 4032 bytes 11-check_regression/console.log.xz | Bin 10032 -> 10116 bytes .../csv-results-vs-first-1/md5sum.csv | 589 +- .../csv-results-vs-first-1/perf.csv | 1132 +- .../csv-results-vs-first-1/results.csv | 1217 +- .../csv-results-vs-prev-0/md5sum.csv | 847 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 1183 +- .../csv-results-vs-prev-0/results.csv | 2073 +- 11-check_regression/csv-results-vs-prev-0/size.csv | 121968 +++++++++--------- .../csv-results-vs-prev-1/md5sum.csv | 589 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 1132 +- .../csv-results-vs-prev-1/results.csv | 1217 +- 11-check_regression/exe.regression | 8 +- 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/jira-body.txt | 12 +- 11-check_regression/mail-body.txt | 12 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results-vs-first-brief.csv | 26 +- 11-check_regression/results-vs-first-full.csv | 1135 +- 11-check_regression/results-vs-first-internal.csv | 89 +- 11-check_regression/results-vs-first.csv | 89 +- 11-check_regression/results-vs-first.log | 366 +- 11-check_regression/results-vs-prev-brief.csv | 26 +- 11-check_regression/results-vs-prev-compare.csv | 18 +- 11-check_regression/results-vs-prev-full.csv | 1225 +- 11-check_regression/results-vs-prev-internal.csv | 91 +- 11-check_regression/results-vs-prev.csv | 91 +- 11-check_regression/results-vs-prev.log | 386 +- 11-check_regression/results.regressions | 14 +- 11-check_regression/skipped-symbols.txt | 5 +- 11-check_regression/symbol.regression | 2 +- 11-check_regression/trigger-bisect | 4 +- 11-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 10 +- .../510.parest_r/results-metadata.json | 10 +- .../510.parest_r/results-metrics.json | 2 +- .../511.povray_r/results-metadata.json | 10 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 10 +- .../squad-vs-first/519.lbm_r/results-metrics.json | 2 +- .../520.omnetpp_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../results-functional.json | 0 .../results-metadata.json | 10 +- .../results-metrics.json | 0 .../525.x264_r/results-metadata.json | 10 +- .../526.blender_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 10 +- .../541.leela_r/results-metadata.json | 10 +- .../squad-vs-first/544.nab_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 78 +- git/binutils_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 169 + jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 19 +- mail/mail-body.txt | 19 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 14 +- results_id | 2 +- 81 files changed, 68787 insertions(+), 67437 deletions(-) create mode 100644 11-check_regression/trigger-notify rename dashboard/squad-vs-first/{500.perlbench_r => 523.xalancbmk_r}/results-funct [...] rename dashboard/squad-vs-first/{500.perlbench_r => 523.xalancbmk_r}/results-metad [...] rename dashboard/squad-vs-first/{500.perlbench_r => 523.xalancbmk_r}/results-metri [...] create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/interesting-commits] branch master updated (f072c5c7 -> 1de2ff75)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from f072c5c7 Add entry 4413365616e8c6024d1ff4e23309e5012ee33b9f from https [...] new 1de2ff75 Add entry 160a943ff8aa0dd9105164f10d4bfca9db872999 from https [...] The 1 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: binutils/gdb-13-branchpoint-99-g160a943ff8a | 1 + .../llvm-master-aarch64-cpu2017rate-O3/build_url | 1 + .../llvm-master-aarch64-cpu2017rate-O3/last_good | 1 + .../llvm-master-aarch64-cpu2017rate-O3/summary.txt | 13 +++++++++ .../tcwg_bmk_llvm_fx/status.txt | 34 ++++++++++++++++++++++ 5 files changed, 50 insertions(+) create mode 120000 binutils/gdb-13-branchpoint-99-g160a943ff8a create mode 100644 binutils/sha1/160a943ff8aa0dd9105164f10d4bfca9db872999/tcwg_bmk [...] create mode 100644 binutils/sha1/160a943ff8aa0dd9105164f10d4bfca9db872999/tcwg_bmk [...] create mode 100644 binutils/sha1/160a943ff8aa0dd9105164f10d4bfca9db872999/tcwg_bmk [...] create mode 100644 binutils/sha1/160a943ff8aa0dd9105164f10d4bfca9db872999/tcwg_bmk [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (be6f614b93 -> 9933a6cdf0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from be6f614b93 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 9933a6cdf0 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] The 1 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 1748 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39524 -> 39604 bytes 04-build_abe-gcc/console.log.xz | Bin 214336 -> 216020 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9172 -> 8380 bytes 07-build_abe-glibc/console.log.xz | Bin 246228 -> 246552 bytes 08-build_abe-gdb/console.log.xz | Bin 39948 -> 40032 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2488 -> 2556 bytes 11-check_regression/console.log.xz | Bin 5948 -> 5488 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- sumfiles/gdb.log.xz | Bin 14640 -> 14656 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 24 files changed, 46 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[linux] branch master updated (b7bfaa761d76 -> 1fe4fd6f5cad)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository linux. from b7bfaa761d76 Linux 6.2-rc3 new 26870c3f5b15 xfs: don't assert if cmap covers imap after cycling lock new d4542f314507 xfs: make xfs_iomap_page_ops static new c0f399ff5149 xfs: fix off-by-one error in xfs_btree_space_to_height new 817644fa4525 xfs: get root inode correctly at bulkstat new 4da112513c01 xfs: Fix deadlock on xfs_inodegc_worker new e195605ed28b xfs: xfs_qm: remove unnecessary ‘0’ values from error new 601a27ea09a3 xfs: fix extent busy updating new 1fe4fd6f5cad Merge tag 'xfs-6.2-fixes-2' of git://git.kernel.org/pub/sc [...] The 8 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: fs/xfs/libxfs/xfs_btree.c | 7 ++++++- fs/xfs/xfs_extent_busy.c | 1 + fs/xfs/xfs_icache.c | 10 ++++++++++ fs/xfs/xfs_ioctl.c | 4 ++-- fs/xfs/xfs_iomap.c | 2 +- fs/xfs/xfs_qm.c | 2 +- fs/xfs/xfs_reflink.c | 2 -- 7 files changed, 21 insertions(+), 7 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allnoconfig updated (3da79753c0 -> b44d461a5a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 3da79753c0 34: onsuccess: #421: all: Success after binutils/llvm/linux: [...] new b44d461a5a 35: onsuccess: #422: all: Success after binutils/llvm/linux/ [...] The 1 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 1756 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 32580 -> 32452 bytes 04-build_kernel_llvm/console.log.xz | Bin 65168 -> 65232 bytes 05-build_abe-qemu/console.log.xz | Bin 31276 -> 31212 bytes 06-build_linux/console.log.xz | Bin 3428 -> 3488 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3948 -> 4472 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (782e531cd3 -> 4b6768306d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-arm in repository toolchain/ci/base-artifacts. discards 782e531cd3 167: onsuccess: #590: 6: Success after binutils/gcc/linux/gl [...] discards 7e5148f6bf 166: onsuccess: #589: 6: Success after binutils/gcc/linux/gl [...] discards e1ee03c3dc 165: onsuccess: #588: 6: Success after binutils/gcc/linux/gl [...] discards 1c557c492d 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/gd [...] discards f544f7e036 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] discards 8487dc5935 162: onsuccess: #579: 6: Success after gcc: 11 commits discards e146bc2d63 161: onsuccess: #578: 6: Success after binutils: 15 commits discards e0ae5b5441 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] discards 91e647b7b2 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] discards 9e6210413d 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] discards c0fc12de0b 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits discards 75b56cde1d 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits discards 5067845fa9 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits discards 7ca36c8cea 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] discards bd592c98ba 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits discards b5711adbe6 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] discards bf003f758a 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] discards 75bdd379fc 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] discards 24a44b769f 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] discards 47c63dc948 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] discards 0b5860602d 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] discards e902834f51 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits discards 8f6da2b560 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] discards 85c28ff223 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] discards a84735b24f 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] discards 47b0d326bd 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] discards 5621511425 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] discards f3dab57116 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] discards 0a17664aeb 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] discards d8994595dc 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] discards 8842569e55 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] discards f41d9d094b 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] discards 059e9d7564 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] discards acdf2a6ae2 134: onsuccess: #544: 6: Success after binutils: 18 commits discards e442df6ac1 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] discards de1e19ba64 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] discards 31ce7d6d87 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] discards 43d233dd1d 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] discards 2c0a4dea46 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] discards 8877970cc9 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] discards 262cf415a3 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] discards 4686d29a75 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] discards 3f47b746bf 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] discards 3946252876 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] discards 8ebe66b6d9 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits discards 8fe7ec8f00 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits discards f7b56eb85c 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] discards 27e641a066 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] discards 8adb022c72 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] discards c0c638611c 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] discards 4d70be1cc6 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] discards 843cccaa35 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] discards 98e3602cab 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] discards 962f291310 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits discards d309f6d15b 113: onsuccess: #522: 1: Success after gcc: 12 commits discards c638c5938f 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] discards 5d39bdd66e 111: force: #520: 6: Success after gcc: 9 commits discards a440d3fe00 110: onsuccess: #518: 6: Success after binutils: 5 commits discards 814e50d35c 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards 5e0df23c51 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] discards de28d68ae2 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] discards bc7f40ec0c 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards d1657eb44f 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] discards 4da8a58e80 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards 5f58c61d7c 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards 27fb850801 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards d8a354989d 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] discards c5a1b5e3d4 100: onsuccess: #506: 4: Success after baseline build: no ne [...] discards 343cd30804 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] discards 391272cda1 98: force: #504: 6: Success after gcc: 18 commits discards f8467aa6ec 97: onsuccess: #503: 6: Success after linux: 11 commits discards de9913ad2e 96: onsuccess: #502: 6: Success after glibc: 10 commits discards fc2de2934d 95: onsuccess: #500: 6: Success after binutils: 8 commits discards 736b36b2e7 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] discards 5faf307010 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] discards 62fe23719f 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] discards ad960a2250 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards c2f1de58b1 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] discards 5613e06b59 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] discards 0e312e0948 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards aba19aa026 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] discards 64c9286956 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] discards d36cffffdc 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] discards a70c245d49 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] discards 7d82bf953f 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] discards 9eb677fb9d 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] discards 549e56d8b3 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] discards 30a375fdba 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] discards b44d27b9da 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] discards ef888a8dcc 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] discards 0b28bc49d1 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] discards 5960267d12 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] discards a1fe8b1213 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] discards 5e3288d0ec 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards 565e5438db 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards 6e26104682 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards 26c1924394 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] discards 59f134e220 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] discards 46aba0f03b 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] discards 7bcdee7ea5 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] discards 3edbc985c4 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new 9198212d4f 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new e1e2bf81f0 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] new 706fe7f97f 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new 14b9ff0c08 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new 3db9c38a4b 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] new 59c16ca99e 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new f26357e421 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new d555393fd8 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new f17de235cf 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] new c130f4af00 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] new 5e190b1596 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] new a1409d7f15 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] new 14c75227ea 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] new 9b43f53d38 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] new 8302492096 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] new ace38e0525 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] new 98e4bb30c7 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] new 339320487d 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] new d3a4c8b1c3 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] new 2ec551b096 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] new ac37e6e773 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] new 95b078ae8d 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new 622aeea334 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] new d25c17ce2c 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] new b671f7ce90 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new 676386e677 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] new b7a71f2cde 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] new 25d84444bd 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] new 348e628ca7 95: onsuccess: #500: 6: Success after binutils: 8 commits new 0eee2dbbd6 96: onsuccess: #502: 6: Success after glibc: 10 commits new 4c80711e55 97: onsuccess: #503: 6: Success after linux: 11 commits new 7f9053d4d5 98: force: #504: 6: Success after gcc: 18 commits new 49eebe5aa7 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] new 7ad9e854c0 100: onsuccess: #506: 4: Success after baseline build: no ne [...] new f5fcf1bcaa 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] new 1b4b13fb6a 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 0a41640fa0 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new c1bda0d079 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new f41f4ebc7d 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] new b31896607c 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new 27752d838e 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] new 64059eb4d9 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] new c1cbe1191e 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new c16919b216 110: onsuccess: #518: 6: Success after binutils: 5 commits new 707e6650b8 111: force: #520: 6: Success after gcc: 9 commits new e37f25792a 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] new fb49237e55 113: onsuccess: #522: 1: Success after gcc: 12 commits new 96fb23f034 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits new 5c57aa3818 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] new b6fb35c527 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] new e3dfe3ce8a 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] new 664a8771dc 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] new d2c43edbc4 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] new f2902d0523 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] new b50b6e7818 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] new 0910eb8e74 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits new d5dbf064d5 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits new 3d12ff237b 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] new b328a7b708 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] new f631ac43a6 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] new 05f6941ecc 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] new becb261bf2 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] new cfe4d156e7 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] new e569d1e23a 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] new 2ec66baa56 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] new 5469f3a5b9 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] new c5e97b5254 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] new beb873d1b4 134: onsuccess: #544: 6: Success after binutils: 18 commits new d6ea72152b 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] new 3312f71681 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] new 9e298eb4ec 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] new 1c6b51a9c1 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] new c44fc66432 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] new 90395bffb5 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] new 23d98e662a 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] new ef25f5e468 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] new 2e23861dbd 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] new 0e5a55fbdb 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] new bea6bc0824 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] new 93e9006772 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits new db027a1ad2 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] new a063ce415f 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] new 5eecb31041 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] new 112db01077 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] new ee9e134880 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] new c7ac466c55 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] new 07a64f82d9 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits new 3ff06d34db 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] new 7e9f6b6714 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits new 1ddc27a8e9 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits new 5e9b16903e 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits new a39e71c323 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] new b747d66fe0 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] new 45f6e8937d 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] new cdd854803f 161: onsuccess: #578: 6: Success after binutils: 15 commits new a1128fe0cb 162: onsuccess: #579: 6: Success after gcc: 11 commits new 44114c5219 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] new b072242cd5 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/gd [...] new cfad26e16c 165: onsuccess: #588: 6: Success after binutils/gcc/linux/gl [...] new 39148dbede 166: onsuccess: #589: 6: Success after binutils/gcc/linux/gl [...] new 51998f08d4 167: onsuccess: #590: 6: Success after binutils/gcc/linux/gl [...] new 4b6768306d 168: onsuccess: #591: 6: Success after binutils/gcc/linux/gd [...] 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 (782e531cd3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] 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 1724 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 52552 -> 52904 bytes 05-build_abe-gcc/console.log.xz | Bin 238548 -> 238280 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 9064 -> 8604 bytes 08-build_abe-glibc/console.log.xz | Bin 236536 -> 236556 bytes 09-build_abe-gdb/console.log.xz | Bin 52388 -> 52556 bytes 10-check_regression/console.log.xz | Bin 4316 -> 3912 bytes 11-update_baseline/console.log | 62 +++++++++++++++++------------------ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +++++++++--------- 19 files changed, 55 insertions(+), 55 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page: