Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (5e0321de6e66 -> 29f8cf0bebbd)

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 5e0321de6e66 133: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] discards c7c9af9a1790 132: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] discards 24e9ea2f5f5a 131: onsuccess: #880: 1: Success after binutils/gcc/linux/ [...] discards 9d75104dd4a4 130: onsuccess: #879: 1: Success after binutils/gcc/linux/ [...] discards f4e739c2c37e 129: onsuccess: #878: 1: Success after linux: 3008 commits discards f9a0e4bbd76f 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 7d6eb0e7da34 127: onsuccess: #874: 1: Success after linux: 219 commits discards f6e1a362aed2 126: onsuccess: #873: 1: Success after glibc: 2 commits discards aee078522342 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 7df7160e8544 124: onsuccess: #869: 1: Success after binutils/gcc/linux/ [...] discards b1b2738c77de 123: onsuccess: #868: 1: Success after binutils/gcc/linux/ [...] discards 2c115de04fe5 122: onsuccess: #867: 1: Success after binutils/gcc/linux/ [...] discards 1259d5fb9a8a 121: onsuccess: #866: 1: Success after binutils/gcc/linux/ [...] discards 05aee1a0146a 120: onsuccess: #865: 1: Success after binutils/gcc/linux/ [...] discards c999135a3dd4 119: onsuccess: #864: 1: Success after binutils/gcc/linux/ [...] discards f79c3d121b38 118: onsuccess: #863: 1: Success after linux: 12 commits discards c47602f86a58 117: onsuccess: #861: 1: Success after binutils: 18 commits discards b869f9191c5f 116: onsuccess: #859: 1: Success after binutils/gcc/linux/ [...] discards 7babce8f62e2 115: onsuccess: #858: 1: Success after binutils/gcc/linux/ [...] discards f201ae473f57 114: onsuccess: #857: 1: Success after binutils/gcc/linux/ [...] discards fdf049936e5c 113: onsuccess: #856: 1: Success after binutils/gcc/linux/ [...] discards 789bc7b4a658 112: onsuccess: #855: 1: Success after binutils/gcc/linux/ [...] discards d442b041a0be 111: onsuccess: #854: 1: Success after binutils/gcc/linux/ [...] discards 0cce8bbb8992 110: onsuccess: #853: 1: Success after binutils/gcc/linux/ [...] discards bd9c2d3dca1a 109: onsuccess: #852: 1: Success after binutils/gcc/linux/ [...] discards 1c6a30a2dd67 108: onsuccess: #850: 1: Success after gcc: 2 commits discards a9b98a70ebc5 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 54ecb52bc97f 106: onsuccess: #847: 1: Success after binutils/gcc/linux/ [...] discards b287ac99fb5a 105: onsuccess: #846: 1: Success after binutils/gcc/linux/ [...] discards f12002ffb47f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 6 [...] discards 0136f8e9a48e 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 5 [...] discards 923450ae222e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/ [...] discards 0f829e5d1e9e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/ [...] discards 44ba5237a355 100: onsuccess: #841: 1: Success after binutils/gcc/linux/ [...] discards 9d99aea9449d 99: onsuccess: #840: 1: Success after binutils/gcc/linux/g [...] discards 81ebcf37e46e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] discards 2ba0e9ef64b6 97: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] discards 89a0617acc2b 96: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] discards 52573bb364ba 95: onsuccess: #835: 1: Success after binutils: 3 commits discards f24d7e217214 94: onsuccess: #832: 1: Success after binutils: 5 commits discards abb6ca043624 93: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] discards 8855e87bd871 92: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] discards 84036d7417ff 91: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] discards 6abcbb58712a 90: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] discards 49b4ada55151 89: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] discards 5ce2eacab4da 88: onsuccess: #825: 1: Success after binutils/gcc/linux/g [...] discards 94bbf066e3bc 87: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] discards 2a6e6598264d 86: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] discards 5c529dfa3a57 85: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] discards 520ea277e5bd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] discards b3253fc0cc55 83: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] discards 77ac7852d246 82: onsuccess: #819: 1: Success after binutils/gcc/linux/g [...] discards a0572be38be8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/g [...] discards 3f5202ef17e9 80: onsuccess: #817: 1: Success after binutils/gcc/linux/g [...] discards b18e27f329f2 79: onsuccess: #816: 1: Success after binutils/gcc/linux/g [...] discards fac912fb1bc3 78: onsuccess: #815: 1: Success after binutils/gcc/linux/g [...] discards 1a9f08f804d2 77: onsuccess: #814: 1: Success after binutils/gcc/linux/g [...] discards 6d2f47b3a063 76: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] discards f5e9b4f1d96c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] discards 4bbb8af650e5 74: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] discards b098af5e22f9 73: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] discards 5ff2cbae832a 72: onsuccess: #809: 1: Success after binutils/gcc/linux/g [...] discards ce5e494b352e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/g [...] discards a62bd6aae765 70: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] discards 77ede52d4c8b 69: onsuccess: #806: 1: Success after binutils/gcc/linux/g [...] discards a1ceb19b4657 68: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] discards 66769c4ba918 67: onsuccess: #804: 1: Success after binutils/gcc/linux/g [...] discards 6a34e61aee27 66: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] discards c8714d65e525 65: onsuccess: #802: 1: Success after binutils/gcc/linux/g [...] discards 94e69529bd55 64: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] discards ca68c5fb0006 63: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] discards 2390c71ed5a4 62: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] discards bdfa50354f04 61: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] discards bfaf9eacd4d3 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/g [...] discards 9cc0b5d39d5c 59: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] discards 4f1e70e7eb1a 58: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] discards 542ada0e68bc 57: onsuccess: #794: 1: Success after binutils/gcc/linux/g [...] discards 03166b882100 56: onsuccess: #793: 1: Success after binutils/gcc/linux/g [...] discards 8f6e6efe8f07 55: onsuccess: #792: 1: Success after binutils/gcc/linux/g [...] discards 058fbd3a444a 54: onsuccess: #791: 1: Success after binutils/gcc/linux/g [...] discards d04d2f4d744b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/g [...] discards 989149b3bb22 52: onsuccess: #789: 1: Success after binutils/gcc/linux/g [...] discards 3bf71fe45954 51: onsuccess: #788: 1: Success after binutils/gcc/linux/g [...] discards 62eabc7b454e 50: onsuccess: #787: 1: Success after binutils/gcc/linux/g [...] discards f71b9febad57 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 63b9c67e5edb 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 5c0c15deb56b 47: onsuccess: #780: 1: Success after binutils/gcc/linux/g [...] discards 31829f6d11fa 46: onsuccess: #779: 1: Success after binutils/gcc/linux/g [...] discards f74ed0f6993e 45: onsuccess: #778: 1: Success after binutils/gcc/linux/g [...] discards 29f5cf20a0f7 44: onsuccess: #777: 1: Success after binutils/gcc/linux/g [...] discards e5a687314258 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/g [...] discards 2db70cd37857 42: onsuccess: #775: 1: Success after binutils/gcc/linux/g [...] discards 86ee1da059d7 41: onsuccess: #774: 1: Success after binutils/gcc/linux/g [...] discards 278ab2f351a7 40: onsuccess: #773: 1: Success after binutils/gcc/linux/g [...] discards b0dd20ec0fe4 39: onsuccess: #772: 1: Success after binutils/gcc/linux/g [...] discards cecef3f2daf9 38: onsuccess: #771: 1: Success after binutils/gcc/linux/g [...] discards eeb43d0c13ea 37: onsuccess: #770: 1: Success after binutils/gcc/linux/g [...] discards 87695ceb80bd 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 [...] discards b2c0ceda00a4 35: onsuccess: #768: 1: Success after binutils/gcc/linux/g [...] discards c130043281cb 34: onsuccess: #767: 1: Success after binutils/gcc/linux/g [...] discards 596656f2d565 33: onsuccess: #766: 1: Success after binutils/gcc/linux/g [...] new bd69dd1b6b7f 33: onsuccess: #766: 1: Success after binutils/gcc/linux/g [...] new 27d65ae2e633 34: onsuccess: #767: 1: Success after binutils/gcc/linux/g [...] new ab68993c2ade 35: onsuccess: #768: 1: Success after binutils/gcc/linux/g [...] new 5a64352c09aa 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 [...] new e9d5c32d7a62 37: onsuccess: #770: 1: Success after binutils/gcc/linux/g [...] new 81647035f936 38: onsuccess: #771: 1: Success after binutils/gcc/linux/g [...] new 5304389251cd 39: onsuccess: #772: 1: Success after binutils/gcc/linux/g [...] new da0ef418f2e5 40: onsuccess: #773: 1: Success after binutils/gcc/linux/g [...] new 375eefd0baf3 41: onsuccess: #774: 1: Success after binutils/gcc/linux/g [...] new e839f9547ace 42: onsuccess: #775: 1: Success after binutils/gcc/linux/g [...] new 246b59ce80c4 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/g [...] new 338de786816c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/g [...] new 0fec7ecd60b9 45: onsuccess: #778: 1: Success after binutils/gcc/linux/g [...] new 0c5d83aa4d53 46: onsuccess: #779: 1: Success after binutils/gcc/linux/g [...] new 674e44e682a3 47: onsuccess: #780: 1: Success after binutils/gcc/linux/g [...] new 8095efef9a95 48: onsuccess: #782: 1: Success after binutils: 8 commits new 4c2c5da32801 49: onsuccess: #785: 1: Success after binutils: 12 commits new 36689f0cfe3c 50: onsuccess: #787: 1: Success after binutils/gcc/linux/g [...] new 22e1ee8b89e5 51: onsuccess: #788: 1: Success after binutils/gcc/linux/g [...] new 508bca81723b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/g [...] new bf1fe12f5dd5 53: onsuccess: #790: 1: Success after binutils/gcc/linux/g [...] new 65bf19a0db05 54: onsuccess: #791: 1: Success after binutils/gcc/linux/g [...] new 9cff69a8203c 55: onsuccess: #792: 1: Success after binutils/gcc/linux/g [...] new 93ecab29ff82 56: onsuccess: #793: 1: Success after binutils/gcc/linux/g [...] new 925941682607 57: onsuccess: #794: 1: Success after binutils/gcc/linux/g [...] new 5580696988cd 58: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] new c5d38d06dd30 59: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] new b5dc836b59a7 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/g [...] new c51e0a5f89d7 61: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] new 7b87c2fbce8f 62: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] new 65b52a5e9c0b 63: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] new 927bf970f49e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] new ffcc9ef65ce7 65: onsuccess: #802: 1: Success after binutils/gcc/linux/g [...] new ade6a2ac2e93 66: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] new 789849d4f66b 67: onsuccess: #804: 1: Success after binutils/gcc/linux/g [...] new d181d033fdfe 68: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] new f697697123fd 69: onsuccess: #806: 1: Success after binutils/gcc/linux/g [...] new 51ea99acd448 70: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] new 9fca8b692e02 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/g [...] new 628818ef49f0 72: onsuccess: #809: 1: Success after binutils/gcc/linux/g [...] new 7304346bb4b0 73: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] new a0a60a30bf59 74: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] new e71e1b6307a6 75: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] new ede35b7f1cb4 76: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] new 1d15bdbf04cf 77: onsuccess: #814: 1: Success after binutils/gcc/linux/g [...] new 880bd3c26409 78: onsuccess: #815: 1: Success after binutils/gcc/linux/g [...] new 9f21f75db370 79: onsuccess: #816: 1: Success after binutils/gcc/linux/g [...] new def9ceb2e600 80: onsuccess: #817: 1: Success after binutils/gcc/linux/g [...] new 58ab8e05f267 81: onsuccess: #818: 1: Success after binutils/gcc/linux/g [...] new 1a3d15dac8fa 82: onsuccess: #819: 1: Success after binutils/gcc/linux/g [...] new 7b47f0fde196 83: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] new 7f4c5c874d44 84: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] new adede0396a70 85: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] new a786031d1983 86: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] new 0f84d7d1dcdd 87: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] new c59798e08641 88: onsuccess: #825: 1: Success after binutils/gcc/linux/g [...] new 98469d5f99fc 89: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] new 2c56f6ba3b6c 90: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] new 1e1aed82e5ed 91: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] new 418be8dc3465 92: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] new eb0828b656ad 93: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] new fae4a08e2809 94: onsuccess: #832: 1: Success after binutils: 5 commits new 1986ba9aacf6 95: onsuccess: #835: 1: Success after binutils: 3 commits new 563e58ab3b84 96: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] new a07132afa8b1 97: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] new 989894dc0fe6 98: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] new 1c9b0f0d3e59 99: onsuccess: #840: 1: Success after binutils/gcc/linux/g [...] new 0ed91aac84f4 100: onsuccess: #841: 1: Success after binutils/gcc/linux/ [...] new 7cb44923d978 101: onsuccess: #842: 1: Success after binutils/gcc/linux/ [...] new 96d1a19dd98a 102: onsuccess: #843: 1: Success after binutils/gcc/linux/ [...] new cc8366115c48 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 5 [...] new 2cb7c522db2d 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 6 [...] new bfddafce3347 105: onsuccess: #846: 1: Success after binutils/gcc/linux/ [...] new fee4496bbb00 106: onsuccess: #847: 1: Success after binutils/gcc/linux/ [...] new 838b66bf868f 107: onsuccess: #849: 1: Success after binutils: 5 commits new 800dcd390b6e 108: onsuccess: #850: 1: Success after gcc: 2 commits new d03a67202752 109: onsuccess: #852: 1: Success after binutils/gcc/linux/ [...] new 23e587552656 110: onsuccess: #853: 1: Success after binutils/gcc/linux/ [...] new 81d8e2705d04 111: onsuccess: #854: 1: Success after binutils/gcc/linux/ [...] new db7c0c61ef16 112: onsuccess: #855: 1: Success after binutils/gcc/linux/ [...] new e202054f5307 113: onsuccess: #856: 1: Success after binutils/gcc/linux/ [...] new dc08643f7434 114: onsuccess: #857: 1: Success after binutils/gcc/linux/ [...] new f217ed25f590 115: onsuccess: #858: 1: Success after binutils/gcc/linux/ [...] new f714dc57d65c 116: onsuccess: #859: 1: Success after binutils/gcc/linux/ [...] new 167aede51582 117: onsuccess: #861: 1: Success after binutils: 18 commits new 9dbd15b77470 118: onsuccess: #863: 1: Success after linux: 12 commits new 39729cd83401 119: onsuccess: #864: 1: Success after binutils/gcc/linux/ [...] new 0fa44e5129ba 120: onsuccess: #865: 1: Success after binutils/gcc/linux/ [...] new 366650701cd3 121: onsuccess: #866: 1: Success after binutils/gcc/linux/ [...] new e9453833e0e7 122: onsuccess: #867: 1: Success after binutils/gcc/linux/ [...] new 3754b08e7b1d 123: onsuccess: #868: 1: Success after binutils/gcc/linux/ [...] new 957bd3f22e92 124: onsuccess: #869: 1: Success after binutils/gcc/linux/ [...] new a29c60738a7c 125: onsuccess: #871: 1: Success after binutils: 26 commits new 8ba61e98848f 126: onsuccess: #873: 1: Success after glibc: 2 commits new d47a33246e3b 127: onsuccess: #874: 1: Success after linux: 219 commits new be2ee99674be 128: onsuccess: #876: 1: Success after binutils: 12 commits new 4ba25fd69773 129: onsuccess: #878: 1: Success after linux: 3008 commits new 297fd3c17816 130: onsuccess: #879: 1: Success after binutils/gcc/linux/ [...] new b0097f590674 131: onsuccess: #880: 1: Success after binutils/gcc/linux/ [...] new b4f7244f4af5 132: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] new abffac468fc0 133: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] new 29f8cf0bebbd 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 1 [...] 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 (5e0321de6e66) \ 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 1752 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 40388 -> 39580 bytes 04-build_abe-gcc/console.log.xz | Bin 215716 -> 213428 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8568 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 244260 -> 243672 bytes 08-build_abe-gdb/console.log.xz | Bin 39840 -> 39336 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2980 -> 2604 bytes 11-check_regression/console.log.xz | Bin 6808 -> 5776 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 27 + 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 137 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 27 + sumfiles/g++.log.xz | Bin 3773596 -> 3769764 bytes sumfiles/g++.sum | 116 +- sumfiles/gcc.log.xz | Bin 3291492 -> 3315620 bytes sumfiles/gcc.sum | 5082 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1087616 -> 1081820 bytes sumfiles/gfortran.sum | 98 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232352 -> 232456 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 447492 -> 456808 bytes sumfiles/libstdc++.sum | 10 +- 41 files changed, 2860 insertions(+), 2831 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-defconfig updated (e1888711ee0f -> e648a5d7f1bc)

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-release-arm-lts-defconfig in repository toolchain/ci/base-artifacts. from e1888711ee0f 30: onsuccess: #284: boot: Success after binutils/linux/qe [...] new e648a5d7f1bc 31: onsuccess: #285: boot: Success after binutils/qemu: 21 [...] 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 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30092 -> 30060 bytes 04-build_kernel_llvm/console.log.xz | Bin 64248 -> 63040 bytes 05-build_abe-qemu/console.log.xz | Bin 30568 -> 30180 bytes 06-build_linux/console.log.xz | Bin 3468 -> 3560 bytes 07-boot_linux/console.log.xz | Bin 5800 -> 5804 bytes 08-check_regression/console.log.xz | Bin 3504 -> 3404 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +++++++++++----------- 16 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allnoconfig updated (8f9381daed48 -> f284c727c553)

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-next-allnoconfig in repository toolchain/ci/base-artifacts. from 8f9381daed48 28: onsuccess: #420: all: Success after binutils/llvm/linu [...] new f284c727c553 29: onsuccess: #421: all: Success after binutils/llvm/linu [...] 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 1784 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 32148 -> 32084 bytes 04-build_kernel_llvm/console.log.xz | Bin 66304 -> 65404 bytes 05-build_abe-qemu/console.log.xz | Bin 30592 -> 31476 bytes 06-build_linux/console.log.xz | Bin 3100 -> 3172 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4296 -> 4420 bytes 09-update_baseline/console.log | 8 ++++---- 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 +++++++++++++++--------------- 18 files changed, 27 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (8d1bad0d12da -> 73ad7a096667)

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 8d1bad0d12da 136: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] discards 9f24fa81e2b2 135: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] discards 1b2bed4710e1 134: onsuccess: #624: 1: Success after binutils/gcc/linux/ [...] discards a27bebb0162c 133: onsuccess: #623: 1: Success after binutils/gcc/linux/ [...] discards 99799456f576 132: onsuccess: #622: 1: Success after binutils/gcc/linux/ [...] discards 15e1f92c5445 131: onsuccess: #621: 1: Success after binutils/gcc/linux/ [...] discards 74b63e201b98 130: onsuccess: #620: 1: Success after binutils/gcc/linux/ [...] discards 257e3fc88fab 129: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] discards c871033ebd89 128: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] discards 8059d90f4fa7 127: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] discards 23ccda65691c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] discards 8ae99bc6710f 125: onsuccess: #614: 1: Success after linux: 12 commits discards 274724f40bc0 124: onsuccess: #612: 1: Success after binutils: 18 commits discards e034254441c7 123: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] discards 6dbd90036732 122: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] discards 4d90aeb070b8 121: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] discards ee0931668b22 120: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] discards e258cb744f6e 119: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] discards 699f03773739 118: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] discards 77681ec86e5d 117: onsuccess: #604: 1: Success after binutils/gcc/linux/ [...] discards f00344563c7a 116: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards 0f8d2141dda2 115: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards 624af24346be 114: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] discards a966505bdf8f 113: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] discards 5f8cd20c99af 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 6 [...] discards f3c92060cd6b 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 4 [...] discards 1bd72757639b 110: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] discards e044c3584ec0 109: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] discards 12bf965ac8c5 108: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] discards 8680788cc41c 107: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] discards 3638ed342953 106: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] discards d89a3e7e413c 105: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] discards ff0696761325 104: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] discards fb6e7c0d637f 103: onsuccess: #589: 1: Success after binutils: 3 commits discards c599f763a171 102: onsuccess: #586: 1: Success after binutils: 5 commits discards eeb36e1d6e00 101: onsuccess: #584: 1: Success after binutils/gcc/linux/ [...] discards 7c7894cce3d5 100: onsuccess: #583: 1: Success after binutils/gcc/linux/ [...] discards b937f2018907 99: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] discards 7102b59de623 98: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] discards 76772c7489bc 97: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] discards 6844351407f5 96: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 2c4a16083f69 95: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 1433d41f6b2a 94: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards e25944fa9901 93: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards b7cf17fdb2ea 92: onsuccess: #575: 1: Success after linux: 34 commits discards 9d4638671f6a 91: onsuccess: #574: 1: Success after glibc: 3 commits discards faf5c7854dc1 90: onsuccess: #572: 1: Success after binutils: 15 commits discards f3e79a104148 89: onsuccess: #570: 1: Success after linux: 11 commits discards f0624cb245a0 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 0db1ab241500 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 385811eb0648 86: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 154a51773817 85: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 699946e3553c 84: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] discards 7d1fd98b6620 83: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 7861ba2ac9f8 82: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 23dc3a8633a1 81: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 9ccc36f13d45 80: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards d6c33bc0edae 79: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards c0debca8eeaa 78: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards c015185c1b13 77: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 3c9815e7b73e 76: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 9b9c8b1c7c73 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/g [...] discards 84d05351f060 74: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards a4f60299b6a9 73: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards aedab17ee50f 72: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 7731dee4f4c4 71: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 204d87546ef6 70: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards d54f440e3ad0 69: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 30de51523ea7 68: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 36bc17e0608c 67: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 0aebc60734aa 66: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 34fe4ccf6a41 65: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards fab0ce2efcdd 64: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 62fa684fa02f 63: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards c9a3bd2e91b9 62: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 7277531631d1 61: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] discards aed7af02a037 60: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards a7e91963aa34 59: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 10db658e1444 58: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] discards 397cc64cf345 57: onsuccess: #536: 1: Success after binutils/gcc/linux/g [...] discards d9e628466be0 56: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards 4cdf73f3a6ab 55: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards 7ba6bc8b9b11 54: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards d9b542f010ec 53: onsuccess: #531: 1: Success after binutils: 12 commits discards ffda9b5348cb 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 392353d46f6d 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 1a971bb4cc12 50: onsuccess: #523: 1: Success after binutils/gcc/linux/g [...] discards 8519bf9803c4 49: onsuccess: #522: 1: Success after binutils/gcc/linux/g [...] discards 540d891072d4 48: onsuccess: #521: 1: Success after binutils/gcc/linux/g [...] discards a4d2d66c1528 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/g [...] discards 984734f1465c 46: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards ceef3ad94a9f 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/g [...] discards a30676c5ccb7 44: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards f7d949c947ef 43: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] discards ae31c907fb95 42: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] discards 8c35383a45ce 41: onsuccess: #514: 1: Success after linux: 64 commits discards c824af99d162 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121- [...] discards 563bac594d7c 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 44b2b5604120 38: onsuccess: #508: 1: Success after binutils: 3 commits discards bf1734e781dc 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb6 [...] discards 2fc8337749bd 36: onsuccess: #505: 1: Success after glibc: 3 commits new d0266ba8247c 36: onsuccess: #505: 1: Success after glibc: 3 commits new 566a42a05d68 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb6 [...] new 947bdf4f0a1a 38: onsuccess: #508: 1: Success after binutils: 3 commits new 06981c62d604 39: onsuccess: #511: 1: Success after binutils: 8 commits new 9db18993ec43 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121- [...] new 03cf51095d29 41: onsuccess: #514: 1: Success after linux: 64 commits new 46d629e44944 42: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] new dad64e4e178c 43: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] new 93cd72b88a71 44: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new f3b0e53eb396 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/g [...] new 88eda296cd6c 46: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new c73952eedbc9 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/g [...] new 2ee8910e3de1 48: onsuccess: #521: 1: Success after binutils/gcc/linux/g [...] new d74b8dd02650 49: onsuccess: #522: 1: Success after binutils/gcc/linux/g [...] new d7bb9a248b29 50: onsuccess: #523: 1: Success after binutils/gcc/linux/g [...] new 9c5327970635 51: onsuccess: #525: 1: Success after binutils: 8 commits new 0dfa61522a40 52: onsuccess: #528: 1: Success after binutils: 8 commits new b1469f6598a7 53: onsuccess: #531: 1: Success after binutils: 12 commits new b1760338235a 54: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new b7d647c55cd1 55: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new 583038f94fd8 56: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new c68e1c24cda6 57: onsuccess: #536: 1: Success after binutils/gcc/linux/g [...] new e1cbaca80a1d 58: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] new 139bb5e093e7 59: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new d0ae92ac7711 60: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 50ab7de426b4 61: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] new 1fbaa127f2bb 62: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new bec57b5cf334 63: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new c338c1e8051f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 83792d4a43dd 65: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new fac769de6f0e 66: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new cf46e002ef8a 67: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new bd9d95553be2 68: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 52873c42bc9e 69: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new b2e8d4608fa3 70: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 6218b4dce9be 71: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 5a65c3a229b3 72: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new f56e7de8014f 73: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 5490f9a887e8 74: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new de23a18f753d 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/g [...] new 0aa897eee5ff 76: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new bcf86cc3ccd6 77: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new c9da5d93e999 78: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 228fa8e2a5dc 79: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 8ce574a8337c 80: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 63572995cec9 81: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new e5e78138cfc3 82: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new caf19bfe1a57 83: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new d08f3b0cbd4a 84: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] new e902966d6951 85: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 503d0dda13c4 86: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 1b008fdc8f98 87: onsuccess: #567: 1: Success after binutils: 8 commits new aa05f4cc9d0b 88: onsuccess: #569: 1: Success after glibc: 10 commits new fb5127aa46b8 89: onsuccess: #570: 1: Success after linux: 11 commits new 5e40c8360427 90: onsuccess: #572: 1: Success after binutils: 15 commits new 3eccb6076e75 91: onsuccess: #574: 1: Success after glibc: 3 commits new e598b2ff3d3e 92: onsuccess: #575: 1: Success after linux: 34 commits new 7050c95b2bc7 93: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 3ddc5a004689 94: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 36f9d86d026f 95: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new ad4869e04fb2 96: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 90ea17655d48 97: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] new fc5bcff757dc 98: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] new 79b416f2b24a 99: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] new 1205fc736a0b 100: onsuccess: #583: 1: Success after binutils/gcc/linux/ [...] new 59c8772f8ce3 101: onsuccess: #584: 1: Success after binutils/gcc/linux/ [...] new 89e71f9c1bcf 102: onsuccess: #586: 1: Success after binutils: 5 commits new 51db3811ce18 103: onsuccess: #589: 1: Success after binutils: 3 commits new e983b50b5903 104: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] new 9d2ef79331c6 105: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] new 9961e4affc16 106: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] new 58057a3dcf33 107: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] new 53a27273aa08 108: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] new aeaeacac12c8 109: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new 90af7f2e0b3c 110: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new 7673cfca600b 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 4 [...] new e9e0216f9832 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 6 [...] new 25b744bf1730 113: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] new c1e500ea9e27 114: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] new 40a71d6547bd 115: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new b68ad0f923d0 116: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new d7aeec9c40e1 117: onsuccess: #604: 1: Success after binutils/gcc/linux/ [...] new 7223d393ee6f 118: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] new ec4efbdc991e 119: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] new 2a3c4e272bea 120: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] new 90b82079de57 121: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] new f8d6a6e528fc 122: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] new ee8925abf2cb 123: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] new 777f695eb49e 124: onsuccess: #612: 1: Success after binutils: 18 commits new 2dc24fd96709 125: onsuccess: #614: 1: Success after linux: 12 commits new 6552daddfccc 126: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] new 34bb89ce0bc5 127: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] new e04192f29499 128: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] new a9d6bb01fd62 129: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] new b6b52713b0c8 130: onsuccess: #620: 1: Success after binutils/gcc/linux/ [...] new db056d89f401 131: onsuccess: #621: 1: Success after binutils/gcc/linux/ [...] new 8af2f9948013 132: onsuccess: #622: 1: Success after binutils/gcc/linux/ [...] new 8e88ada1239a 133: onsuccess: #623: 1: Success after binutils/gcc/linux/ [...] new 8fc191085379 134: onsuccess: #624: 1: Success after binutils/gcc/linux/ [...] new 989401c654dd 135: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] new deee451d6beb 136: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] new 73ad7a096667 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 1 [...] 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 (8d1bad0d12da) \ 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 1800 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 55168 -> 53120 bytes 04-build_abe-gcc/console.log.xz | Bin 237972 -> 235504 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8696 -> 8596 bytes 07-build_abe-glibc/console.log.xz | Bin 236912 -> 235180 bytes 08-build_abe-gdb/console.log.xz | Bin 53064 -> 52004 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2696 -> 2256 bytes 11-check_regression/console.log.xz | Bin 13500 -> 13576 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 57 +- 11-check_regression/mail-body.txt | 217 +- 11-check_regression/results.compare | 99 +- 11-check_regression/results.compare2 | 1229 +++-- 11-check_regression/results.regressions | 107 +- 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 219 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 107 +- sumfiles/gdb.log.xz | Bin 1830168 -> 1781480 bytes sumfiles/gdb.sum | 8217 ++++++++++--------------------- 29 files changed, 3797 insertions(+), 6535 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_sq/gnu-master-aarch64-spec2k6-Os updated (afe66b255d26 -> f11dea2e1ac2)

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_sq/gnu-master-aarch64-spec2k6-Os in repository toolchain/ci/base-artifacts. from afe66b255d26 45: onsuccess: #100: 1: [TCWG CI] No change after glibc: 3 [...] new f11dea2e1ac2 46: onsuccess: #105: 1: [TCWG CI] No change after binutils [...] 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 1832 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32408 -> 32384 bytes 04-build_abe-stage1/console.log.xz | Bin 73536 -> 73680 bytes 06-build_abe-linux/console.log.xz | Bin 8824 -> 8820 bytes 07-build_abe-glibc/console.log.xz | Bin 245624 -> 246120 bytes 08-build_abe-stage2/console.log.xz | Bin 183264 -> 182088 bytes 09-benchmark/benchmark-build.log | 92 +- 09-benchmark/benchmark.log | 90 +- 09-benchmark/console.log.xz | Bin 3868 -> 3888 bytes 10-check_regression/console.log.xz | Bin 13132 -> 12084 bytes .../csv-results-vs-first-1/md5sum.csv | 2478 +- .../csv-results-vs-first-1/perf.csv | 3404 +- .../csv-results-vs-first-1/results.csv | 69855 +-- .../csv-results-vs-first-1/size.csv | 498826 ++++++++---------- .../csv-results-vs-first-1/vect.csv | 23 +- .../csv-results-vs-prev-0/md5sum.csv | 1865 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 3760 +- .../csv-results-vs-prev-0/results.csv | 5191 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 1160 +- .../csv-results-vs-prev-1/md5sum.csv | 2478 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 3404 +- .../csv-results-vs-prev-1/results.csv | 69855 +-- 10-check_regression/csv-results-vs-prev-1/size.csv | 498826 ++++++++---------- 10-check_regression/csv-results-vs-prev-1/vect.csv | 23 +- 10-check_regression/results-vs-first-brief.csv | 62 +- 10-check_regression/results-vs-first-full.csv | 3391 +- 10-check_regression/results-vs-first-internal.csv | 223 +- 10-check_regression/results-vs-first.csv | 223 +- 10-check_regression/results-vs-first.log | 1283 +- 10-check_regression/results-vs-prev-brief.csv | 62 +- 10-check_regression/results-vs-prev-compare.csv | 31 +- 10-check_regression/results-vs-prev-full.csv | 3535 +- 10-check_regression/results-vs-prev-internal.csv | 223 +- 10-check_regression/results-vs-prev.csv | 223 +- 10-check_regression/results-vs-prev.log | 1299 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-functional.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metrics.json | 1 + .../410.bwaves/results-metadata.json | 10 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-functional.json | 4 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/416.gamess/results-metrics.json | 1 - .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 10 +- .../435.gromacs/results-metadata.json | 10 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-functional.json | 4 +- .../436.cactusADM/results-metadata.json | 10 +- .../436.cactusADM/results-metrics.json | 2 - .../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 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 10 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 10 +- .../454.calculix/results-metadata.json | 10 +- .../454.calculix/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-functional.json | 4 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../459.GemsFDTD/results-metrics.json | 2 - .../462.libquantum/results-metadata.json | 10 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 10 +- .../465.tonto/results-functional.json | 4 +- .../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 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../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 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 10 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- mail/jira-body.txt | 14 +- mail/mail-body.txt | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results_id | 2 +- 103 files changed, 452785 insertions(+), 719642 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-release-arm_eabi-coremark-O3 updated (ec61298a28b9 -> 25de93ab4755)

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_eabi_stm32/gnu_eabi-release-arm_eabi-coremark-O3 in repository toolchain/ci/base-artifacts. from ec61298a28b9 16: onsuccess: #156: 1: [TCWG CI] No change after binutils [...] new 25de93ab4755 17: onsuccess: #157: 1: [TCWG CI] No change after binutils [...] 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 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 29996 -> 30292 bytes 04-build_abe-stage1/console.log.xz | Bin 85224 -> 85716 bytes 06-build_abe-newlib/console.log.xz | Bin 16616 -> 16740 bytes 07-build_abe-stage2/console.log.xz | Bin 159012 -> 160344 bytes 08-benchmark/benchmark-build.log | 84 +++++++++++---------- 08-benchmark/benchmark.log | 82 ++++++++++---------- 08-benchmark/console.log.xz | Bin 3748 -> 3836 bytes 09-check_regression/console.log.xz | Bin 4856 -> 4740 bytes 09-check_regression/results-vs-first.log | 2 +- 09-check_regression/results-vs-prev.log | 4 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +-- .../squad-vs-first/coremark/results-metadata.json | 12 +-- dashboard/squad-vs-first/dashboard-push-squad.sh | 10 +-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 34 ++++----- mail/mail-body.txt | 34 ++++----- mail/mail-subject.txt | 2 +- manifest.sh | 28 +++---- results_id | 2 +- 24 files changed, 159 insertions(+), 155 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (db22616f61c8 -> a6822dc7cd57)

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 db22616f61c8 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new a6822dc7cd57 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits 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 1732 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 40012 -> 39560 bytes 04-build_abe-gcc/console.log.xz | Bin 214288 -> 214584 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8684 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 245908 -> 245136 bytes 08-build_abe-gdb/console.log.xz | Bin 40576 -> 39460 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3844 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3128 -> 2572 bytes 11-check_regression/console.log.xz | Bin 5820 -> 5336 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- sumfiles/gdb.log.xz | Bin 14628 -> 14616 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 24 files changed, 52 insertions(+), 43 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-allmodconfig updated (249c2c8376a2 -> 7247dc03acb1)

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/gnu-master-arm-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from 249c2c8376a2 36: onsuccess: #586: 33: Success after binutils/gcc/linux/ [...] new 7247dc03acb1 37: onsuccess: #587: 33: Success after binutils/gcc/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 1972 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31760 -> 31892 bytes 04-build_abe-stage1/console.log.xz | Bin 91496 -> 91252 bytes 05-build_abe-qemu/console.log.xz | Bin 31448 -> 30652 bytes 06-build_linux/console.log.xz | Bin 4896 -> 4904 bytes 08-check_regression/console.log.xz | Bin 4392 -> 4380 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 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 | 30 +++++++++++++++--------------- 16 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (0a17a169b12c -> a161de826133)

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 0a17a169b12c 145: onsuccess: #561: 6: Success after binutils/gcc/linux/ [...] discards 5fbed5a24070 144: onsuccess: #560: 6: Success after binutils/gcc/linux/ [...] discards d4ffe4b2f621 143: onsuccess: #559: 6: Success after binutils/gcc/linux/ [...] discards e1826e017d3a 142: onsuccess: #558: 6: Success after binutils/gcc/linux/ [...] discards 483b0035cdac 141: onsuccess: #557: 6: Success after binutils/gcc/linux/ [...] discards 787ead4d42ce 140: onsuccess: #556: 6: Success after binutils/gcc/linux/ [...] discards 4de83da3ee56 139: onsuccess: #555: 6: Success after binutils/gcc/linux/ [...] discards e78dd197e297 138: onsuccess: #554: 6: Success after binutils/gcc/linux/ [...] discards ecc1f5e9d288 137: onsuccess: #553: 6: Success after binutils/gcc/linux/ [...] discards 16cf49f45576 136: onsuccess: #551: 6: Success after binutils/gcc/linux/ [...] discards 944f10f1a715 135: onsuccess: #550: 6: Success after binutils/gcc/linux/ [...] discards 8e084ad7341f 134: onsuccess: #544: 6: Success after binutils: 18 commits discards 728df8533075 133: onsuccess: #542: 6: Success after binutils/gcc/linux/ [...] discards c612f8bdacc6 132: onsuccess: #541: 6: Success after binutils/gcc/linux/ [...] discards 0381c2a984d4 131: onsuccess: #540: 6: Success after binutils/gcc/linux/ [...] discards 410915732427 130: onsuccess: #539: 6: Success after binutils/gcc/linux/ [...] discards d3a1a569ffff 129: onsuccess: #538: 6: Success after binutils/gcc/linux/ [...] discards 7473b9efc536 128: onsuccess: #537: 6: Success after binutils/gcc/linux/ [...] discards 4a706ab4fe19 127: onsuccess: #536: 6: Success after binutils/gcc/linux/ [...] discards e7c0ad820154 126: onsuccess: #535: 6: Success after binutils/gcc/linux/ [...] discards b8b2e48202d2 125: onsuccess: #534: 6: Success after binutils/gcc/linux/ [...] discards 5c3fd9f2d6ec 124: onsuccess: #533: 6: Success after binutils/gcc/linux/ [...] discards 982fbaa6f4ea 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 6 [...] discards 73914825ea16 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 5 [...] discards 0cd6905a9b5f 121: onsuccess: #530: 6: Success after binutils/gcc/linux/ [...] discards 73525e8e0734 120: onsuccess: #529: 6: Success after binutils/gcc/linux/ [...] discards e4d01d76af3e 119: onsuccess: #528: 6: Success after binutils/gcc/linux/ [...] discards a31b78d64aba 118: onsuccess: #527: 6: Success after binutils/gcc/linux/ [...] discards af65b14ede3f 117: onsuccess: #526: 6: Success after binutils/gcc/linux/ [...] discards bb36870126f0 116: onsuccess: #525: 6: Success after binutils/gcc/linux/ [...] discards da5c31559368 115: onsuccess: #524: 6: Success after binutils/gcc/linux/ [...] discards b14ba9745b7b 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits discards c6071838d305 113: onsuccess: #522: 1: Success after gcc: 12 commits discards 556468896845 112: force: #521: 1: Failure after basepoints/gcc-13-3918- [...] discards 9cb250f11852 111: force: #520: 6: Success after gcc: 9 commits discards 91f803e1fad6 110: onsuccess: #518: 6: Success after binutils: 5 commits discards 6ac1fc4c97f6 109: onsuccess: #516: 6: Success after binutils/gcc/linux/ [...] discards 1eae776812c8 108: onsuccess: #514: 6: Success after binutils/gcc/linux/ [...] discards 58fc84a39b9e 107: onsuccess: #513: 6: Success after binutils/gcc/linux/ [...] discards e2173539036f 106: onsuccess: #512: 6: Success after binutils/gcc/linux/ [...] discards 5d8c1ae0bc03 105: onsuccess: #511: 6: Success after binutils/gcc/linux/ [...] discards 238407b598ec 104: onsuccess: #510: 6: Success after binutils/gcc/linux/ [...] discards 7af6b5602101 103: onsuccess: #509: 6: Success after binutils/gcc/linux/ [...] discards c9c15b4468aa 102: onsuccess: #508: 6: Success after binutils/gcc/linux/ [...] discards 3d3d722e542e 101: onsuccess: #507: 4: Success after binutils/gcc/linux/ [...] discards e07315692e31 100: onsuccess: #506: 4: Success after baseline build: no [...] discards 3e9aa7a771f5 99: force: #505: 4: Failure after basepoints/gcc-13-3596-g [...] discards 8a624e2b1bf6 98: force: #504: 6: Success after gcc: 18 commits discards 3698b9678837 97: onsuccess: #503: 6: Success after linux: 11 commits discards 329763fa6282 96: onsuccess: #502: 6: Success after glibc: 10 commits discards 600fe22e2aa2 95: onsuccess: #500: 6: Success after binutils: 8 commits discards 0c3616c9d4c3 94: onsuccess: #498: 6: Success after binutils/gcc/linux/g [...] discards 04f5e46d79e7 93: onsuccess: #497: 6: Success after binutils/gcc/linux/g [...] discards 7ab8d20ca3e5 92: onsuccess: #496: 6: Success after binutils/gcc/linux/g [...] discards e96bb733515d 91: onsuccess: #495: 6: Success after binutils/gcc/linux/g [...] discards f289d4a5cd1d 90: onsuccess: #494: 6: Success after binutils/gcc/linux/g [...] discards 63fc15ecb584 89: onsuccess: #492: 6: Success after binutils/gcc/linux/g [...] discards bfa77050ba8c 88: onsuccess: #491: 6: Success after binutils/gcc/linux/g [...] discards 70acd621967d 87: onsuccess: #490: 6: Success after binutils/gcc/linux/g [...] discards 57f86c334a62 86: onsuccess: #489: 6: Success after binutils/gcc/linux/g [...] discards 36fe2f6d0d57 85: onsuccess: #488: 6: Success after binutils/gcc/linux/g [...] discards 2aa136a94984 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/g [...] discards 7bd4ff1c25ab 83: onsuccess: #486: 6: Success after binutils/gcc/linux/g [...] discards 18d6fad5f603 82: onsuccess: #485: 6: Success after binutils/gcc/linux/g [...] discards bd200b5230bd 81: onsuccess: #484: 6: Success after binutils/gcc/linux/g [...] discards 0717096b090e 80: onsuccess: #483: 6: Success after binutils/gcc/linux/g [...] discards 13e345316ee2 79: onsuccess: #482: 6: Success after binutils/gcc/linux/g [...] discards e4e5c37ce107 78: onsuccess: #481: 6: Success after binutils/gcc/linux/g [...] discards e2c80b0721d6 77: onsuccess: #480: 6: Success after binutils/gcc/linux/g [...] discards 0859720704b5 76: onsuccess: #479: 6: Success after binutils/gcc/linux/g [...] discards 3b03a832e203 75: onsuccess: #478: 6: Success after binutils/gcc/linux/g [...] discards 3cbf85f75f7e 74: onsuccess: #477: 6: Success after binutils/gcc/linux/g [...] discards 74c346219e9b 73: onsuccess: #476: 6: Success after binutils/gcc/linux/g [...] discards cbf07f323f34 72: onsuccess: #475: 6: Success after binutils/gcc/linux/g [...] discards 1be5c4a9bef8 71: onsuccess: #474: 6: Success after binutils/gcc/linux/g [...] discards ef72eeb9e66c 70: onsuccess: #473: 6: Success after binutils/gcc/linux/g [...] discards 6c43630aff07 69: onsuccess: #472: 6: Success after binutils/gcc/linux/g [...] discards ff95b85e2578 68: onsuccess: #471: 6: Success after binutils/gcc/linux/g [...] discards 7fed488ef7d3 67: onsuccess: #470: 6: Success after binutils/gcc/linux/g [...] discards de4cc9896d7a 66: onsuccess: #469: 6: Success after binutils/gcc/linux/g [...] discards 23180c9495ca 65: onsuccess: #468: 6: Success after binutils/gcc/linux/g [...] discards ed69a959f3f1 64: onsuccess: #467: 6: Success after binutils/gcc/linux/g [...] discards facd3671b7b8 63: onsuccess: #466: 6: Success after binutils/gcc/linux/g [...] discards 967fb6e9071e 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits discards 8bcb9477f7ad 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits discards 5b6398efc1ae 60: onsuccess: #463: 1: Success after gcc: 10 commits discards 7554ea417ecd 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g [...] discards 5a49d11cbd3d 58: force: #461: 6: Success after gcc: 29 commits discards 8b99e8c98011 57: onsuccess: #459: 6: Success after binutils: 8 commits discards 01fb19bcb55a 56: onsuccess: #457: 6: Success after binutils/gcc/linux/g [...] discards b08b1681172b 55: onsuccess: #456: 6: Success after binutils/gcc/linux/g [...] discards 0041091313b7 54: onsuccess: #455: 6: Success after binutils/gcc/linux/g [...] discards 5fbe1fa98c24 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/g [...] discards 56dc982d6bcd 52: onsuccess: #453: 6: Success after binutils/gcc/linux/g [...] discards 27bc46dacddf 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/g [...] discards 73894253a3a3 50: onsuccess: #451: 6: Success after binutils/gcc/linux/g [...] discards 44cf48a50bc6 49: onsuccess: #450: 6: Success after binutils/gcc/linux/g [...] discards 8987f07ad780 48: onsuccess: #449: 6: Success after binutils/gcc/linux/g [...] discards e47914a18e79 47: onsuccess: #448: 4: Success after binutils/gcc/linux/g [...] discards 6cdc61f1fea5 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits discards be3501b113c1 45: onsuccess: #446: 4: Success after gcc: 13 commits new 4d3e26645389 45: onsuccess: #446: 4: Success after gcc: 13 commits new b96f5f16435c 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits new 0b45e8e219c2 47: onsuccess: #448: 4: Success after binutils/gcc/linux/g [...] new 3edd9858cfa4 48: onsuccess: #449: 6: Success after binutils/gcc/linux/g [...] new 771d17bd64dc 49: onsuccess: #450: 6: Success after binutils/gcc/linux/g [...] new 4af00684b1c6 50: onsuccess: #451: 6: Success after binutils/gcc/linux/g [...] new 1b6bff161845 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/g [...] new 5f5427db81e6 52: onsuccess: #453: 6: Success after binutils/gcc/linux/g [...] new 801591385424 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/g [...] new e21b62621ac8 54: onsuccess: #455: 6: Success after binutils/gcc/linux/g [...] new 5d9ffd34804a 55: onsuccess: #456: 6: Success after binutils/gcc/linux/g [...] new 1eb567360751 56: onsuccess: #457: 6: Success after binutils/gcc/linux/g [...] new 68bfedde658e 57: onsuccess: #459: 6: Success after binutils: 8 commits new e98b20579165 58: force: #461: 6: Success after gcc: 29 commits new cfd1300034d6 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g [...] new 696fff4d01d4 60: onsuccess: #463: 1: Success after gcc: 10 commits new 37557c785b34 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits new ca9fc794b5c9 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits new c77cde854834 63: onsuccess: #466: 6: Success after binutils/gcc/linux/g [...] new d94f89af688a 64: onsuccess: #467: 6: Success after binutils/gcc/linux/g [...] new 03b8f834a45d 65: onsuccess: #468: 6: Success after binutils/gcc/linux/g [...] new 5520be962ed9 66: onsuccess: #469: 6: Success after binutils/gcc/linux/g [...] new e0b6c46189e2 67: onsuccess: #470: 6: Success after binutils/gcc/linux/g [...] new 1096afb59761 68: onsuccess: #471: 6: Success after binutils/gcc/linux/g [...] new 7d347084e50a 69: onsuccess: #472: 6: Success after binutils/gcc/linux/g [...] new 85d2000b2669 70: onsuccess: #473: 6: Success after binutils/gcc/linux/g [...] new 28c6d90dc98b 71: onsuccess: #474: 6: Success after binutils/gcc/linux/g [...] new d4f85ef700cb 72: onsuccess: #475: 6: Success after binutils/gcc/linux/g [...] new c1af70472d17 73: onsuccess: #476: 6: Success after binutils/gcc/linux/g [...] new 20f5375f65c4 74: onsuccess: #477: 6: Success after binutils/gcc/linux/g [...] new cfce0b9cfb68 75: onsuccess: #478: 6: Success after binutils/gcc/linux/g [...] new dd62a41e9d51 76: onsuccess: #479: 6: Success after binutils/gcc/linux/g [...] new 7f4a72984920 77: onsuccess: #480: 6: Success after binutils/gcc/linux/g [...] new 89bb337949fa 78: onsuccess: #481: 6: Success after binutils/gcc/linux/g [...] new 8fb3f8f3c1b5 79: onsuccess: #482: 6: Success after binutils/gcc/linux/g [...] new 3bd179cac502 80: onsuccess: #483: 6: Success after binutils/gcc/linux/g [...] new a5c5b15b88ae 81: onsuccess: #484: 6: Success after binutils/gcc/linux/g [...] new f81ab2b84c48 82: onsuccess: #485: 6: Success after binutils/gcc/linux/g [...] new 5dd30271b3df 83: onsuccess: #486: 6: Success after binutils/gcc/linux/g [...] new 9e6e6d64fca7 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/g [...] new 4b272b35ac51 85: onsuccess: #488: 6: Success after binutils/gcc/linux/g [...] new 4e3aee2e72fa 86: onsuccess: #489: 6: Success after binutils/gcc/linux/g [...] new 95b077709174 87: onsuccess: #490: 6: Success after binutils/gcc/linux/g [...] new 44e5c67d22d3 88: onsuccess: #491: 6: Success after binutils/gcc/linux/g [...] new be0bde0fdd08 89: onsuccess: #492: 6: Success after binutils/gcc/linux/g [...] new 9e5e3dc9f333 90: onsuccess: #494: 6: Success after binutils/gcc/linux/g [...] new f423aff38efb 91: onsuccess: #495: 6: Success after binutils/gcc/linux/g [...] new 07c739405219 92: onsuccess: #496: 6: Success after binutils/gcc/linux/g [...] new 79e52f64ee2c 93: onsuccess: #497: 6: Success after binutils/gcc/linux/g [...] new 26a4e7706a76 94: onsuccess: #498: 6: Success after binutils/gcc/linux/g [...] new 51da898e225a 95: onsuccess: #500: 6: Success after binutils: 8 commits new 10a1effddedd 96: onsuccess: #502: 6: Success after glibc: 10 commits new 27878db20ea7 97: onsuccess: #503: 6: Success after linux: 11 commits new df0a80abc18b 98: force: #504: 6: Success after gcc: 18 commits new 933339027077 99: force: #505: 4: Failure after basepoints/gcc-13-3596-g [...] new 61ed04040678 100: onsuccess: #506: 4: Success after baseline build: no [...] new 2d978271f0cb 101: onsuccess: #507: 4: Success after binutils/gcc/linux/ [...] new fa54cfeaa2f5 102: onsuccess: #508: 6: Success after binutils/gcc/linux/ [...] new c11fbcdcca9b 103: onsuccess: #509: 6: Success after binutils/gcc/linux/ [...] new 9492b6b50013 104: onsuccess: #510: 6: Success after binutils/gcc/linux/ [...] new 7f60f9f32fe4 105: onsuccess: #511: 6: Success after binutils/gcc/linux/ [...] new ad20b627e173 106: onsuccess: #512: 6: Success after binutils/gcc/linux/ [...] new de63159dc909 107: onsuccess: #513: 6: Success after binutils/gcc/linux/ [...] new 6c588512c31c 108: onsuccess: #514: 6: Success after binutils/gcc/linux/ [...] new 9d56386b0393 109: onsuccess: #516: 6: Success after binutils/gcc/linux/ [...] new d8ece500a936 110: onsuccess: #518: 6: Success after binutils: 5 commits new 590033cb4c5d 111: force: #520: 6: Success after gcc: 9 commits new 73c31ba2d07b 112: force: #521: 1: Failure after basepoints/gcc-13-3918- [...] new 8b3066fa661e 113: onsuccess: #522: 1: Success after gcc: 12 commits new 8899787b0d9e 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits new 1861770b731e 115: onsuccess: #524: 6: Success after binutils/gcc/linux/ [...] new 7c2f87dfb922 116: onsuccess: #525: 6: Success after binutils/gcc/linux/ [...] new b9b936b9f1ef 117: onsuccess: #526: 6: Success after binutils/gcc/linux/ [...] new 10f7993ecf71 118: onsuccess: #527: 6: Success after binutils/gcc/linux/ [...] new 07fb78f461ce 119: onsuccess: #528: 6: Success after binutils/gcc/linux/ [...] new 42e85d8eb045 120: onsuccess: #529: 6: Success after binutils/gcc/linux/ [...] new f13c3e52dd22 121: onsuccess: #530: 6: Success after binutils/gcc/linux/ [...] new a45a5d3a9c18 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 5 [...] new 952b78695ee4 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 6 [...] new 1a8c3be7cefb 124: onsuccess: #533: 6: Success after binutils/gcc/linux/ [...] new 5f75ac6bbdf3 125: onsuccess: #534: 6: Success after binutils/gcc/linux/ [...] new c72b055ec41b 126: onsuccess: #535: 6: Success after binutils/gcc/linux/ [...] new ffd3905869b7 127: onsuccess: #536: 6: Success after binutils/gcc/linux/ [...] new 9d849e2699b6 128: onsuccess: #537: 6: Success after binutils/gcc/linux/ [...] new 9695085e264d 129: onsuccess: #538: 6: Success after binutils/gcc/linux/ [...] new 5c494f510cad 130: onsuccess: #539: 6: Success after binutils/gcc/linux/ [...] new d595206005ef 131: onsuccess: #540: 6: Success after binutils/gcc/linux/ [...] new 570b36795feb 132: onsuccess: #541: 6: Success after binutils/gcc/linux/ [...] new fd4b2722ed82 133: onsuccess: #542: 6: Success after binutils/gcc/linux/ [...] new 2d598a1365fe 134: onsuccess: #544: 6: Success after binutils: 18 commits new 6ec17b505b8b 135: onsuccess: #550: 6: Success after binutils/gcc/linux/ [...] new aa2dadf833e4 136: onsuccess: #551: 6: Success after binutils/gcc/linux/ [...] new 2328812e7915 137: onsuccess: #553: 6: Success after binutils/gcc/linux/ [...] new 4b89cd481567 138: onsuccess: #554: 6: Success after binutils/gcc/linux/ [...] new e2ae72762ca5 139: onsuccess: #555: 6: Success after binutils/gcc/linux/ [...] new dbfca8d2480c 140: onsuccess: #556: 6: Success after binutils/gcc/linux/ [...] new d293b5f4e327 141: onsuccess: #557: 6: Success after binutils/gcc/linux/ [...] new b5afe415d99b 142: onsuccess: #558: 6: Success after binutils/gcc/linux/ [...] new 35815cf7ef50 143: onsuccess: #559: 6: Success after binutils/gcc/linux/ [...] new 2760ac1af50e 144: onsuccess: #560: 6: Success after binutils/gcc/linux/ [...] new b5c492b506c3 145: onsuccess: #561: 6: Success after binutils/gcc/linux/ [...] new a161de826133 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 1 [...] 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 (0a17a169b12c) \ 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 1736 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 54744 -> 52684 bytes 05-build_abe-gcc/console.log.xz | Bin 237132 -> 233924 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8756 -> 8600 bytes 08-build_abe-glibc/console.log.xz | Bin 237268 -> 234784 bytes 09-build_abe-gdb/console.log.xz | Bin 52344 -> 51760 bytes 10-check_regression/console.log.xz | Bin 4096 -> 3600 bytes 11-update_baseline/console.log | 40 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++------------ 18 files changed, 41 insertions(+), 41 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-aarch64-check_bootstrap_lto updated (41e66cb672aa -> 513978925f5b)

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_gcc_check_bootstrap/master-aarch64-check_bootstrap_lto in repository toolchain/ci/base-artifacts. discards 41e66cb672aa 125: onsuccess: #690: 1: Success after binutils/gcc: 27 commits discards 180cb845e63f 124: onsuccess: #689: 1: Success after binutils/gcc: 84 commits discards 43f68f5d686a 123: onsuccess: #688: 1: Success after gcc: 18 commits discards aca2ce49c7eb 122: onsuccess: #685: 1: Success after gcc: 25 commits discards f3f41ee795f1 121: onsuccess: #682: 1: Success after gcc: 63 commits discards ccb13de7dd62 120: onsuccess: #679: 1: Success after binutils/gcc: 39 commits discards c61b3a53748e 119: onsuccess: #678: 1: Success after binutils/gcc: 8 commits discards 3c0ec0698282 118: onsuccess: #677: 1: Success after binutils/gcc: 19 commits discards e3119fd65340 117: onsuccess: #676: 1: Success after binutils/gcc: 61 commits discards b8be9ad30e71 116: onsuccess: #674: 1: Success after binutils/gcc: 30 commits discards 1c894e0011e2 115: onsuccess: #673: 1: Success after binutils/gcc: 42 commits discards 749565d37496 114: onsuccess: #672: 1: Success after binutils/gcc: 29 commits discards 0d9870dad5b0 113: onsuccess: #671: 1: Success after binutils/gcc: 10 commits discards 035ff8ea5a4f 112: onsuccess: #670: 1: Success after binutils/gcc: 14 commits discards 88e352aa3f26 111: onsuccess: #669: 1: Success after binutils/gcc: 39 commits discards 31888c5eff3a 110: onsuccess: #668: 1: Success after binutils/gcc: 87 commits discards eb874172a116 109: onsuccess: #666: 1: Success after binutils/gcc: 60 commits discards d0c73ef7d604 108: onsuccess: #665: 1: Success after binutils/gcc: 83 commits discards f7c126fef2de 107: onsuccess: #663: 1: Success after gcc: 7 commits discards a31058eb835d 106: onsuccess: #660: 1: Success after binutils/gcc: 17 commits discards a452707145d9 105: onsuccess: #659: 1: Success after binutils/gcc: 50 commits discards f907df4f641e 104: onsuccess: #658: 1: Success after binutils/gcc: 48 commits discards 45140fb0d0e1 103: onsuccess: #657: 1: Success after binutils/gcc: 44 commits discards 5d7bb8e65f0e 102: onsuccess: #656: 1: Success after gcc: 30 commits discards 263403a016c3 101: onsuccess: #655: 1: Success after binutils: 5 commits discards 3f1ba94c1631 100: onsuccess: #653: 1: Success after binutils/gcc: 11 commits discards c6b7218aa980 99: onsuccess: #652: 1: Success after binutils/gcc: 35 commits discards cfb2bf898622 98: onsuccess: #651: 1: Success after binutils/gcc: 34 commits discards 5d5328166d19 97: onsuccess: #650: 1: Success after binutils/gcc: 43 commits discards f6ce7571d52f 96: onsuccess: #649: 1: Success after binutils/gcc: 25 commits discards e1947921d24a 95: onsuccess: #648: 1: Success after binutils/gcc: 220 commits discards 376885712302 94: onsuccess: #645: 1: Success after binutils: 3 commits discards 95420a37fee7 93: onsuccess: #642: 1: Success after binutils: 5 commits discards f04ebc09830e 92: onsuccess: #640: 1: Success after binutils/gcc: 71 commits discards 4204ad60a48c 91: onsuccess: #639: 1: Success after binutils/gcc: 46 commits discards 245e90c8fc3d 90: onsuccess: #638: 1: Success after binutils/gcc: 59 commits discards 9bf7940283c8 89: onsuccess: #637: 1: Success after binutils/gcc: 70 commits discards 3d2dcbaf4560 88: onsuccess: #636: 1: Success after binutils/gcc: 56 commits discards 46184da99b74 87: onsuccess: #635: 1: Success after binutils/gcc: 12 commits discards df47cafc8134 86: onsuccess: #634: 1: Success after binutils/gcc: 28 commits discards 4c1d6f5ad038 85: onsuccess: #633: 1: Success after binutils/gcc: 86 commits discards 114e3a72642f 84: onsuccess: #632: 1: Success after binutils/gcc: 31 commits discards fba61665fb58 83: onsuccess: #631: 1: Success after binutils/gcc: 26 commits discards 4df3de10f2f9 82: onsuccess: #630: 1: Success after binutils/gcc: 34 commits discards eaccb9c74e06 81: onsuccess: #629: 1: Success after binutils/gcc: 26 commits discards 8d1cc63e688e 80: onsuccess: #628: 1: Success after binutils/gcc: 3 commits discards 798c3f1be564 79: onsuccess: #627: 1: Success after binutils/gcc: 32 commits discards 947c3e18f154 78: onsuccess: #626: 1: Success after binutils/gcc: 35 commits discards d6bdfe1e9b6d 77: onsuccess: #625: 1: Success after binutils/gcc: 29 commits discards cdafce2cbcb5 76: onsuccess: #624: 1: Success after binutils/gcc: 35 commits discards 4863d3f9b552 75: onsuccess: #623: 1: Success after binutils/gcc: 45 commits discards 444913cd79c9 74: onsuccess: #622: 1: Success after binutils/gcc: 25 commits discards 4721eb7f2978 73: onsuccess: #621: 1: Success after binutils/gcc: 4 commits discards 927e215af919 72: onsuccess: #620: 1: Success after binutils/gcc: 15 commits discards 1e1c803828e2 71: onsuccess: #619: 1: Success after binutils/gcc: 45 commits discards 4a110d010ba2 70: onsuccess: #618: 1: Success after binutils/gcc: 43 commits discards 0267c25d9868 69: onsuccess: #617: 1: Success after binutils/gcc: 40 commits discards c86b521690a3 68: onsuccess: #616: 1: Success after binutils/gcc: 58 commits discards cbe981f917d7 67: onsuccess: #615: 1: Success after binutils/gcc: 29 commits discards 813c6e53bb48 66: onsuccess: #614: 1: Success after binutils/gcc: 9 commits discards 2662b4eec539 65: onsuccess: #613: 1: Success after binutils/gcc: 15 commits discards 7b0b6398a1da 64: onsuccess: #612: 1: Success after binutils/gcc: 52 commits discards 2186938bba21 63: onsuccess: #611: 1: Success after binutils/gcc: 28 commits discards 5fb6fc61330b 62: onsuccess: #610: 1: Success after binutils/gcc: 40 commits discards 1c959645ef6b 61: onsuccess: #609: 1: Success after binutils/gcc: 100 commits discards f8ade966281f 60: onsuccess: #607: 1: Success after binutils: 16 commits discards 95fe3940f0fe 59: onsuccess: #604: 1: Success after gdb-12-branchpoint-2 [...] discards 802000e36c32 58: onsuccess: #601: 1: Success after binutils: 5 commits discards 606fdd1e782f 57: onsuccess: #599: 1: Success after binutils/gcc: 37 commits discards 9ae042ea7b68 56: onsuccess: #598: 1: Success after binutils/gcc: 56 commits discards 7a316ad69283 55: onsuccess: #597: 1: Success after binutils/gcc: 37 commits discards f230dbba369f 54: onsuccess: #596: 1: Success after binutils/gcc: 38 commits discards 7af1bdfc54e1 53: onsuccess: #595: 1: Success after binutils/gcc: 48 commits discards 8228bc9fcf7a 52: onsuccess: #594: 1: Success after binutils/gcc: 15 commits discards d770a02e604b 51: onsuccess: #593: 1: Success after binutils/gcc: 27 commits discards 59e978b5394a 50: onsuccess: #592: 1: Success after binutils/gcc: 54 commits discards 3d23b93fc48a 49: onsuccess: #591: 1: Success after binutils/gcc: 87 commits discards 1424c325f8e8 48: onsuccess: #589: 1: Success after binutils: 11 commits discards 343ebfae4bf4 47: onsuccess: #586: 1: Success after binutils: 8 commits discards 983a744c3986 46: onsuccess: #584: 1: Success after binutils/gcc: 43 commits discards baffe4245f8e 45: onsuccess: #583: 1: Success after binutils/gcc: 12 commits discards 11606e5af192 44: onsuccess: #582: 1: Success after binutils/gcc: 19 commits discards 399e07820e60 43: onsuccess: #581: 1: Success after binutils/gcc: 55 commits discards 2b2732b54673 42: onsuccess: #580: 1: Success after binutils/gcc: 40 commits discards fe64fa98b265 41: onsuccess: #579: 1: Success after binutils/gcc: 47 commits discards 97cbd4c49d8a 40: onsuccess: #578: 1: Success after binutils/gcc: 26 commits discards 9fd87de0ca78 39: onsuccess: #577: 1: Success after binutils/gcc: 8 commits discards a36f74379102 38: onsuccess: #576: 1: Success after binutils/gcc: 6 commits discards 2a306690df4d 37: onsuccess: #575: 1: Success after binutils/gcc: 14 commits discards 26dfaf8b4d21 36: onsuccess: #574: 1: Success after binutils/gcc: 25 commits discards c93bbad8791c 35: onsuccess: #573: 1: Success after binutils/gcc: 16 commits discards c5acbd5a4d36 34: onsuccess: #572: 1: Success after binutils/gcc: 34 commits discards 1eb70b1ed13b 33: onsuccess: #571: 1: Success after binutils/gcc: 34 commits discards 216a43f5a9e9 32: onsuccess: #570: 1: Success after binutils/gcc: 59 commits discards 75af9b4b19ae 31: onsuccess: #569: 1: Success after binutils/gcc: 5 commits discards 23f69e80ed9f 30: onsuccess: #568: 1: Success after binutils/gcc: 17 commits discards b8b758e7f936 29: onsuccess: #567: 1: Success after binutils/gcc: 24 commits discards 710b9b4a029a 28: onsuccess: #566: 1: Success after binutils/gcc: 25 commits discards ccc7ad500419 27: onsuccess: #565: 1: Success after binutils/gcc: 149 commits discards e25f0f87bc13 26: onsuccess: #563: 1: Success after binutils/gcc: 5 commits discards 84dc0f3b14b0 25: onsuccess: #562: 1: Success after binutils/gcc: 14 commits new 9be2a89809e9 25: onsuccess: #562: 1: Success after binutils/gcc: 14 commits new 252afad9ebca 26: onsuccess: #563: 1: Success after binutils/gcc: 5 commits new a5065353f932 27: onsuccess: #565: 1: Success after binutils/gcc: 149 commits new 8a1b5211f0bb 28: onsuccess: #566: 1: Success after binutils/gcc: 25 commits new 667f9c67aaf3 29: onsuccess: #567: 1: Success after binutils/gcc: 24 commits new f1471b2b8fc9 30: onsuccess: #568: 1: Success after binutils/gcc: 17 commits new 456ecbd1830a 31: onsuccess: #569: 1: Success after binutils/gcc: 5 commits new 5d601ed4c323 32: onsuccess: #570: 1: Success after binutils/gcc: 59 commits new 2e582f89a7af 33: onsuccess: #571: 1: Success after binutils/gcc: 34 commits new 1a838d010853 34: onsuccess: #572: 1: Success after binutils/gcc: 34 commits new dd5f3bb855f4 35: onsuccess: #573: 1: Success after binutils/gcc: 16 commits new 8e78fecd8b26 36: onsuccess: #574: 1: Success after binutils/gcc: 25 commits new 1a21e2997450 37: onsuccess: #575: 1: Success after binutils/gcc: 14 commits new e47b37d59134 38: onsuccess: #576: 1: Success after binutils/gcc: 6 commits new 343bddf9c75a 39: onsuccess: #577: 1: Success after binutils/gcc: 8 commits new a76ee1257a03 40: onsuccess: #578: 1: Success after binutils/gcc: 26 commits new f490162f6a87 41: onsuccess: #579: 1: Success after binutils/gcc: 47 commits new 7c9e5de146b7 42: onsuccess: #580: 1: Success after binutils/gcc: 40 commits new 87a32c866b71 43: onsuccess: #581: 1: Success after binutils/gcc: 55 commits new cdece46c402a 44: onsuccess: #582: 1: Success after binutils/gcc: 19 commits new bbe5a5a9f842 45: onsuccess: #583: 1: Success after binutils/gcc: 12 commits new 5c8bf4dfd0ab 46: onsuccess: #584: 1: Success after binutils/gcc: 43 commits new 8a794fab19b0 47: onsuccess: #586: 1: Success after binutils: 8 commits new fa1781d01c4b 48: onsuccess: #589: 1: Success after binutils: 11 commits new b50f323ed18d 49: onsuccess: #591: 1: Success after binutils/gcc: 87 commits new 0b4f77fdc502 50: onsuccess: #592: 1: Success after binutils/gcc: 54 commits new 7f4837a1b7c9 51: onsuccess: #593: 1: Success after binutils/gcc: 27 commits new 7558de1f9f15 52: onsuccess: #594: 1: Success after binutils/gcc: 15 commits new 3e797bc8d454 53: onsuccess: #595: 1: Success after binutils/gcc: 48 commits new 3d887b6270c7 54: onsuccess: #596: 1: Success after binutils/gcc: 38 commits new 4c64915b6195 55: onsuccess: #597: 1: Success after binutils/gcc: 37 commits new dec64d9e8fa2 56: onsuccess: #598: 1: Success after binutils/gcc: 56 commits new 29d57beb4eec 57: onsuccess: #599: 1: Success after binutils/gcc: 37 commits new 74c96910911a 58: onsuccess: #601: 1: Success after binutils: 5 commits new 6866f61ee8c2 59: onsuccess: #604: 1: Success after gdb-12-branchpoint-2 [...] new 3e8fa866917b 60: onsuccess: #607: 1: Success after binutils: 16 commits new fbc573644694 61: onsuccess: #609: 1: Success after binutils/gcc: 100 commits new a57c68f42f13 62: onsuccess: #610: 1: Success after binutils/gcc: 40 commits new cde6082fb075 63: onsuccess: #611: 1: Success after binutils/gcc: 28 commits new 287794c200bf 64: onsuccess: #612: 1: Success after binutils/gcc: 52 commits new bc3a6da95986 65: onsuccess: #613: 1: Success after binutils/gcc: 15 commits new 869ded04d3ac 66: onsuccess: #614: 1: Success after binutils/gcc: 9 commits new 3d7dd21d15a8 67: onsuccess: #615: 1: Success after binutils/gcc: 29 commits new 0d03721fe0cc 68: onsuccess: #616: 1: Success after binutils/gcc: 58 commits new 2bc7e12f6e17 69: onsuccess: #617: 1: Success after binutils/gcc: 40 commits new d16aa6dad8aa 70: onsuccess: #618: 1: Success after binutils/gcc: 43 commits new 9e7740114a55 71: onsuccess: #619: 1: Success after binutils/gcc: 45 commits new b48b1bdec413 72: onsuccess: #620: 1: Success after binutils/gcc: 15 commits new c6eb8e2c59d6 73: onsuccess: #621: 1: Success after binutils/gcc: 4 commits new 6b47905fd45b 74: onsuccess: #622: 1: Success after binutils/gcc: 25 commits new fcee0a3879db 75: onsuccess: #623: 1: Success after binutils/gcc: 45 commits new 9aadc237d755 76: onsuccess: #624: 1: Success after binutils/gcc: 35 commits new 4ab93b2f23d2 77: onsuccess: #625: 1: Success after binutils/gcc: 29 commits new 4f9d335ee76a 78: onsuccess: #626: 1: Success after binutils/gcc: 35 commits new 38351b88dfc1 79: onsuccess: #627: 1: Success after binutils/gcc: 32 commits new fa0da5f87c0a 80: onsuccess: #628: 1: Success after binutils/gcc: 3 commits new 639390ca50cd 81: onsuccess: #629: 1: Success after binutils/gcc: 26 commits new 92a62f769e0d 82: onsuccess: #630: 1: Success after binutils/gcc: 34 commits new d78b787a7de0 83: onsuccess: #631: 1: Success after binutils/gcc: 26 commits new 7f78b49e1190 84: onsuccess: #632: 1: Success after binutils/gcc: 31 commits new f07dc4c41e8d 85: onsuccess: #633: 1: Success after binutils/gcc: 86 commits new 5a78fc56e7e0 86: onsuccess: #634: 1: Success after binutils/gcc: 28 commits new d8d653b58a68 87: onsuccess: #635: 1: Success after binutils/gcc: 12 commits new 022b05dd5279 88: onsuccess: #636: 1: Success after binutils/gcc: 56 commits new 13f7e22e256b 89: onsuccess: #637: 1: Success after binutils/gcc: 70 commits new b1b030f2fd8c 90: onsuccess: #638: 1: Success after binutils/gcc: 59 commits new f1ac607563f7 91: onsuccess: #639: 1: Success after binutils/gcc: 46 commits new 02976b741a7e 92: onsuccess: #640: 1: Success after binutils/gcc: 71 commits new 40fcc3202438 93: onsuccess: #642: 1: Success after binutils: 5 commits new 93908bcedd54 94: onsuccess: #645: 1: Success after binutils: 3 commits new 17676202f33d 95: onsuccess: #648: 1: Success after binutils/gcc: 220 commits new fc6a5e7e789e 96: onsuccess: #649: 1: Success after binutils/gcc: 25 commits new 8f23b4deb83d 97: onsuccess: #650: 1: Success after binutils/gcc: 43 commits new 5d2b79a0cd78 98: onsuccess: #651: 1: Success after binutils/gcc: 34 commits new 565fbb2d2e3b 99: onsuccess: #652: 1: Success after binutils/gcc: 35 commits new d17330442164 100: onsuccess: #653: 1: Success after binutils/gcc: 11 commits new 5afc79994c23 101: onsuccess: #655: 1: Success after binutils: 5 commits new 346720b9cee3 102: onsuccess: #656: 1: Success after gcc: 30 commits new 4a0aff52d976 103: onsuccess: #657: 1: Success after binutils/gcc: 44 commits new c7fa21d6e47d 104: onsuccess: #658: 1: Success after binutils/gcc: 48 commits new 40dc8cb7f511 105: onsuccess: #659: 1: Success after binutils/gcc: 50 commits new 4d881a89897e 106: onsuccess: #660: 1: Success after binutils/gcc: 17 commits new df7b9e703936 107: onsuccess: #663: 1: Success after gcc: 7 commits new e5f21186f543 108: onsuccess: #665: 1: Success after binutils/gcc: 83 commits new 08414334ae59 109: onsuccess: #666: 1: Success after binutils/gcc: 60 commits new e69b88502acf 110: onsuccess: #668: 1: Success after binutils/gcc: 87 commits new 6c8dd1249daa 111: onsuccess: #669: 1: Success after binutils/gcc: 39 commits new e1bc509ddbb9 112: onsuccess: #670: 1: Success after binutils/gcc: 14 commits new afd54b46f13c 113: onsuccess: #671: 1: Success after binutils/gcc: 10 commits new 6f1e61b8b703 114: onsuccess: #672: 1: Success after binutils/gcc: 29 commits new 0c0309471821 115: onsuccess: #673: 1: Success after binutils/gcc: 42 commits new 0d9e009c0557 116: onsuccess: #674: 1: Success after binutils/gcc: 30 commits new 3d2ecae5a46b 117: onsuccess: #676: 1: Success after binutils/gcc: 61 commits new 8edf100b5e6f 118: onsuccess: #677: 1: Success after binutils/gcc: 19 commits new 7394df46874a 119: onsuccess: #678: 1: Success after binutils/gcc: 8 commits new 0116afceb692 120: onsuccess: #679: 1: Success after binutils/gcc: 39 commits new 8230bafac0e6 121: onsuccess: #682: 1: Success after gcc: 63 commits new ccead9aa7af7 122: onsuccess: #685: 1: Success after gcc: 25 commits new bb25de4615aa 123: onsuccess: #688: 1: Success after gcc: 18 commits new 166da978e88d 124: onsuccess: #689: 1: Success after binutils/gcc: 84 commits new 4908fa5f6553 125: onsuccess: #690: 1: Success after binutils/gcc: 27 commits new 513978925f5b 126: onsuccess: #691: 1: Success after binutils/gcc: 10 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 (41e66cb672aa) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check_bootstrap/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1756 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 40324 -> 39540 bytes 04-build_abe-bootstrap_lto/console.log.xz | Bin 281164 -> 276348 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3888 bytes 06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2676 -> 2576 bytes 07-check_regression/console.log.xz | Bin 5460 -> 5444 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 27 + 07-check_regression/results.compare | 26 +- 07-check_regression/results.compare2 | 137 +- 07-check_regression/results.regressions | 27 + 08-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 27 + sumfiles/g++.log.xz | Bin 3664452 -> 3690088 bytes sumfiles/g++.sum | 139 +- sumfiles/gcc.log.xz | Bin 3283748 -> 3269128 bytes sumfiles/gcc.sum | 5060 +++++++++++------------ sumfiles/gfortran.log.xz | Bin 1094984 -> 1090996 bytes sumfiles/gfortran.sum | 96 +- sumfiles/libatomic.log.xz | Bin 2352 -> 2356 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 225752 -> 226164 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 467876 -> 473708 bytes sumfiles/libstdc++.sum | 12 +- 36 files changed, 2891 insertions(+), 2811 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022