Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (2605d39c94 -> b75b7dfd0a)

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-arm in repository toolchain/ci/base-artifacts. discards 2605d39c94 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 7594e0004b 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 4daa9abe1a 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 1a76a35a3b 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 74386651cf 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 0fbff96c2f 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards c308569257 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards b5439b0795 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] discards 6a4fdc36ac 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] discards 43e9e12e25 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] discards a738cff5f0 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] discards 9f48033a9f 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] discards 62274e0923 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards f97c6c04fc 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 386e58e5d5 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 49ead470ff 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 9069a23261 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 37cd7a8c53 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 4c175062d0 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 4427fa3f06 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards 3013c30a04 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards 71594ce1f9 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards fa866b5a32 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 802ec217ae 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] discards 3b46780456 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards afd2a9c87d 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 48fb80bac4 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 15532791f1 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards fd17400660 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 5186b68a4e 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards be6d85d272 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards c2cba0b5b3 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards ea368c33b4 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 5125e185c0 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 74e55c85c1 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 272639a13d 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 57ad2cb335 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 1209e8e0d6 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] discards 5aaa1073c0 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards b5a17bf4e3 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards d15fd1ff66 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 9492159d0f 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 8de3efdbb9 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 923357fa72 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards cecc2e2369 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] discards dd685ebe85 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] discards bec3e664d6 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 5cb3baf9a0 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] discards 3893656b83 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 8f854fb705 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 12a7a7c721 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 2054e40bed 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] discards f7065c93db 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 737f022d64 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] discards c5274c8716 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] discards 9a809c60c0 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 9fb6dbbfa7 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 7a5fdb9c39 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards b45619b948 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] discards 621e8643c7 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] discards e4665391bf 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] discards 0c3d67b67a 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] discards 7aac845e85 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits discards e4172db9ff 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] discards 53538160af 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] discards 741635cf69 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] discards d7d76045b6 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards e1b952cb6a 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards c3d4304d9f 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] discards 7aff9df491 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 808cb28975 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 885d6e4704 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] discards 231bb4ad22 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] discards 39f46d03fb 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 2fdd945a6e 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] discards 6a2024c2c9 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 1cfea40523 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 0acc152903 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] discards f600ed0d03 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 8638722cc3 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 12b656c168 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 968b1ae123 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] discards 8389786ad1 162: onsuccess: #624: 1: Success after linux: 10 commits discards b9a56d23cd 161: onsuccess: #623: 1: Success after glibc: 9 commits discards fa6bb04c53 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 4e07d794b2 159: onsuccess: #620: 1: Success after binutils: 12 commits discards b40d05255e 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] discards 52eee8fa5a 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] discards 014e4310d6 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 554c8d5d0f 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards 3314bea0ad 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits discards c98c191548 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 commits discards fcdccf65ab 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits discards 2e0eb3d901 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] discards ba1757b20b 150: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 3d92b7d9d5 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] discards 3657e87ffa 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards ce7c72fb32 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards fe16739d71 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards dedec8b40b 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards bf2068695d 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits new e3f669ed1c 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits new 840f9bceb6 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 7760c5c242 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 80c129c09e 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 47f7bf58b6 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new ba931d533b 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] new 3abe31daeb 150: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new ba7f48bd96 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] new befc755997 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits new ae0797023b 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 commits new 4bff69f00f 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits new 368a65bee5 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 5a8b196893 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 78067fa1c6 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] new cdf4c39e0a 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] new d8ae63dd07 159: onsuccess: #620: 1: Success after binutils: 12 commits new c656c97fd7 160: onsuccess: #621: 1: Success after gcc: 11 commits new 2308f2cff1 161: onsuccess: #623: 1: Success after glibc: 9 commits new 67c7d084a8 162: onsuccess: #624: 1: Success after linux: 10 commits new 5385ba6599 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] new 7ffb07a26e 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 0e6e8d7221 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 598d5316ba 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 362cac3240 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] new ec0677e6d8 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new fd00b171a3 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 6b928c4829 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] new 831e1ed84c 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new ca44ae8a4d 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] new b55ea4d98a 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] new 1743dcca90 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 7b413e7373 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 02e8bdad83 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] new 0109bfe69d 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 685a7613b6 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new d0eb8b5591 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] new a29b1d3a5f 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] new 6dd53303a0 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] new e00bef7323 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits new e7bd837f73 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] new 1bdfc26ee1 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] new f7b48c0810 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] new 89e7d9daff 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] new 59751d41aa 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new b9d24f558d 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 0d742272a6 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 8f809de829 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] new 644ee2ed6d 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] new 6236d86129 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 918a14ae4a 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] new 12a9716fb4 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 5961d09aaf 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 5643b2eb65 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new da89515914 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] new 22649d54f3 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 23ae45cd65 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] new 3d6bb2543a 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] new 8bfa404cf4 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new ff00716107 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 6406fc15a9 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 3d8c573432 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 1f867cbc83 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 62eee5b577 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 72739a9e39 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] new 25d6588f93 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 24e69386d6 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 1105d178ba 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 2d35f679fb 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 691772f391 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new da65419574 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new f3eba8d849 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 6e3965758e 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new f3d7e16237 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new cc6def0774 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 50568de5bf 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 043eb4d442 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 798c6b0773 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new da4bcbdd10 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] new 1041cda58f 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new ccb57ce0ae 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 8d597edac1 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new c7b7cb4be3 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new cb145ae02e 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 23a8d0e9d8 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new ccdc603d48 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new a869a4d6c4 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 02b1eeb21d 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 16bb98f017 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 1807bf0218 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new fbd911a925 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] new 19d89edb0a 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] new 64ecf0e039 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] new f3d490a399 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] new c54f13a2bc 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] new 8fa865bcbb 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 5a4b3ba551 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new b1d35bdac9 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new c88a18939c 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 6a06d67d79 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new abdd7d2cb5 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 3ce65718c0 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new b75b7dfd0a 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] 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 (2605d39c94) \ 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 2048 -> 2240 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 49000 -> 49288 bytes 04-build_abe-gcc/console.log.xz | Bin 235784 -> 235256 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8516 -> 8824 bytes 07-build_abe-glibc/console.log.xz | Bin 231976 -> 232892 bytes 08-build_abe-gdb/console.log.xz | Bin 46292 -> 46628 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3800 bytes 10-build_abe-check_gcc/console.log.xz | Bin 11164 -> 11292 bytes 11-check_regression/console.log.xz | Bin 5308 -> 2584 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 6 - 11-check_regression/results.compare | 36 +- 11-check_regression/results.compare2 | 43 +- 11-check_regression/results.regressions | 43 - 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 3 + mail/changes-list-long.txt | 17 - mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 34 - mail/short-diag.txt | 1 - manifest.sh | 40 +- results | 43 - sumfiles/g++.log.sep.xz | Bin 37968 -> 44800 bytes sumfiles/g++.log.xz | Bin 2920044 -> 2884724 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 4977 +++++++++++----------- sumfiles/gcc.log.sep.xz | Bin 70188 -> 79080 bytes sumfiles/gcc.log.xz | Bin 2486228 -> 2520628 bytes sumfiles/gcc.sum | 5 +- sumfiles/gcc.sum.sep | 6954 ++++++++++++++++++++----------- sumfiles/gfortran.log.sep.xz | Bin 36888 -> 16892 bytes sumfiles/gfortran.log.xz | Bin 963148 -> 957952 bytes sumfiles/gfortran.sum | 8 +- sumfiles/gfortran.sum.sep | 1449 ++++--- sumfiles/libatomic.log.xz | Bin 2280 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 230904 -> 230836 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 9612 -> 7512 bytes sumfiles/libstdc++.log.xz | Bin 483336 -> 483472 bytes sumfiles/libstdc++.sum.sep | 217 +- 52 files changed, 8298 insertions(+), 5639 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (20d4b69c5e -> a77d7c69f9)

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-arm in repository toolchain/ci/base-artifacts. discards 20d4b69c5e 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 8e02c958b1 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards f0a295e8b9 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 042bb35002 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 018c309789 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 6d4b5bb47d 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 0389990237 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards ab22886e00 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 07d5892f36 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 0506f3745a 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards cd76407f27 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 6d936fc38c 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards a3e706e887 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 3528cb2f25 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards be0d4d5a3b 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 06be7f4a91 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards fa2d7e6893 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 6ac69f5389 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards afb3ffb736 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards aad47931d7 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 13d6aace49 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards b2b95c0f6f 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 85485d1005 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 2392c5ba9b 121: force: #26: : Failure after baseline build: no new commits discards 35169faa0d 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 9ba9406773 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 18c129f421 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards fdbf8098bf 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 7bffe08078 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards dd996e577f 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards b869fb8219 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 7694571bb6 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 0c8176c88f 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards db2d078698 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 0a14f3d44d 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 21ffd9f7ea 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 9c9dbeba3f 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 2b3044fcf2 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 9d469b5ec5 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 6605a70799 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 9539cd74d7 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 06967233a9 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards b2b9316046 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 478065abe6 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards 8b52052270 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards b2abf8f646 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 3081736093 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 0b944c17b9 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards 2125f1093c 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 5e6bd4ae4e 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards 0cd9ba9e2c 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards df76e059ed 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards c707105290 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards f57003d0f1 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 7e2d7b0947 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards 9ad29b84ba 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 90bf5ac659 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 5705200b58 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 5d92b099de 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards 5cf6fa0bb7 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards ceb1e287f5 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards f723f70552 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 9c7fb0c667 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards d345c01919 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards d36b3d73e5 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards f0dcb1b651 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards df2f59f987 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 3cf1fd068b 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 34920df5f1 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards c3ca5f2096 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards ff748b4d1e 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 560429150b 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards a308161402 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 8dbce22cd2 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards ef8a740f68 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 4a1b1177e2 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards d3a287a576 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 77bf6cb7d4 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards e64de65870 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards f8e4890c9e 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards 61cf87e566 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 80a97e2865 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards c322bb58ce 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards d4219a98be 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 0f0881c181 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards a9d1d335ee 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 4350aecdd9 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards 8a577f44bd 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards a4c45efc6b 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 091d87915a 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 63364b9035 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 92773d9a36 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 2c6f49860d 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards c46e314622 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards e54622e12f 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards 31c0c7fc37 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] discards 828ff7ef83 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards 7595199ad2 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] discards d8e2515b36 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] discards 0f5f8ddbc4 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] discards 04a2bc4066 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new d0e4d42b6c 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 4094f99e70 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] new fa831c42ce 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] new 0b491ad90d 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new 579063c8b8 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new ba3c4d3030 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new b68c4835d9 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new f0e531ada4 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 89a9528f28 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 885b9318e7 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 5a2b2aa2dd 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new f8536980cc 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 15b299fae4 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new f382ee62f3 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 933752abfa 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new 5ba5769fbd 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 59a1db9b2f 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new e0e288f5fa 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new f799342cb9 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 5e69e3addb 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new c86494d49f 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new eec5c1965f 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new 41ec7bcb4e 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 6138552efd 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new b6343f401c 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 0775af1573 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new a30b0bc787 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 8c75577e03 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 58d91fc5a0 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new fa1f23ee48 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 782c8310ac 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new f9b46c2368 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new 5b64ca2acf 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new d01e3117a8 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 4f37f98e3c 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new eb439ea7e5 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 61bad9450f 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 6591cf2a95 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 5224c85fcc 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new c7a70d318d 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new eb16f302e8 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new bd278e0985 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new a78ebc4163 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 9d3974cd68 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 68b3b93729 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 0849a0f674 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 8b3cd4c8ea 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new d6c18e5d9b 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 926713a5a1 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new bee5e7050c 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new a5d054decc 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 3ec2aaa01e 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new 1b2c34d714 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 99262727f7 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 74c3ee6d4e 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 9a1cbf8f4a 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new ffd3e648b1 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new dbf954f420 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new b60c875e14 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new b911874d88 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 3f9d951e8e 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new f6bf584414 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 8c3da5c70e 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 06774d6e8c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 9f8d0137f6 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 9cb5601c16 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 33e85bcc5b 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 3f424abbbd 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 047744e671 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 829ada5f77 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 0e5caf063d 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 6e6c9c8ca2 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 81aa265e92 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 5f1b5ceedb 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 8b192da825 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new f74e24d409 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 145ea7dea5 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 3e2e81d03a 121: force: #26: : Failure after baseline build: no new commits new 7c263088bd 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 7ca60e4874 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 36d69733d9 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 081a803de6 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 7b0bfdd0c4 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 4512ab46e5 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 6ddfea20be 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 739754ad5a 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 21a153f8a7 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new abfe1c014b 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 708f1100fc 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 170261da21 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new c199459d51 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new c2acb84074 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 70e7458260 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 865f9e836c 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new fe5410d039 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 121f368260 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 98ab5f3f8e 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 5da4029893 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 2969832a8e 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 3481278831 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new ef831c5161 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new a77d7c69f9 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] 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 (20d4b69c5e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] 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 2032 -> 2292 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 49208 -> 49116 bytes 04-build_abe-gcc/console.log.xz | Bin 234896 -> 235872 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8256 -> 8852 bytes 07-build_abe-glibc/console.log.xz | Bin 232212 -> 232568 bytes 08-build_abe-gdb/console.log.xz | Bin 46844 -> 47028 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3812 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3132 -> 3024 bytes 11-check_regression/console.log.xz | Bin 4116 -> 1944 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 6 +-- 12-update_baseline/console.log | 68 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 3 ++ mail/changes-list-long.txt | 13 ------- mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 34 ----------------- mail/short-diag.txt | 1 - manifest.sh | 40 ++++++++++---------- sumfiles/gdb.log.xz | Bin 14248 -> 14244 bytes sumfiles/gdb.sum | 4 +- 29 files changed, 72 insertions(+), 115 deletions(-) create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-arm-master-O2_LTO updated (a5e046478f -> 64a017778e)

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-code_speed-spec2k6/gnu-arm-master-O2_LTO in repository toolchain/ci/base-artifacts. from a5e046478f 0: init: #19: 1: [TCWG CI] Success after baseline build: no [...] new 64a017778e 1: onsuccess: #20: 1: [TCWG CI] https://ci.linaro.org/job/tc [...] 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 2304 -> 2072 bytes 01-reset_artifacts/patch-env.sh | 2 - 02-prepare_abe/console.log.xz | Bin 2516 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 26764 -> 26924 bytes 04-build_abe-stage1/console.log.xz | Bin 89416 -> 89676 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 8344 -> 8344 bytes 07-build_abe-glibc/console.log.xz | Bin 233084 -> 232940 bytes 08-build_abe-stage2/console.log.xz | Bin 211048 -> 211704 bytes 09-benchmark/benchmark-build.log | 146 +- 09-benchmark/benchmark.log | 144 +- 09-benchmark/console.log.xz | Bin 4280 -> 4360 bytes 10-check_regression/bmk-specific-variability.csv | 22 + 10-check_regression/console.log.xz | Bin 7388 -> 6596 bytes 10-check_regression/mail-body.txt | 13 - 10-check_regression/mail-subject.txt | 1 - 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 3 + mail/changes-list-long.txt | 2 - mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/short-diag.txt | 1 - manifest.sh | 38 +- results-vs-first/compare-results-internal.csv | 80 +- results-vs-first/csv-results-1/md5sum.csv | 32 +- results-vs-first/csv-results-1/perf.csv | 193 +- results-vs-first/csv-results-1/results.csv | 25932 +- results-vs-first/csv-results-1/size.csv | 605568 ++++++++++---------- results-vs-first/csv-results-1/sve.csv | 17940 +- results-vs-first/csv-results-1/vect.csv | 46 +- results-vs-first/interesting-symbols.csv | 44 +- results-vs-first/results-brief.csv | 68 +- results-vs-first/results-full.csv | 201 +- results-vs-first/results-internal.csv | 80 +- results-vs-first/results.csv | 80 +- results-vs-first/tcwg-benchmark-results.log | 3146 +- results-vs-prev/compare-results-internal.csv | 80 +- results-vs-prev/csv-results-1/md5sum.csv | 32 +- results-vs-prev/csv-results-1/perf.csv | 193 +- results-vs-prev/csv-results-1/results.csv | 25932 +- results-vs-prev/csv-results-1/size.csv | 605568 ++++++++++---------- results-vs-prev/csv-results-1/sve.csv | 17940 +- results-vs-prev/csv-results-1/vect.csv | 46 +- results-vs-prev/interesting-symbols.csv | 44 +- results-vs-prev/results-brief.csv | 68 +- results-vs-prev/results-full.csv | 201 +- results-vs-prev/results-internal.csv | 80 +- results-vs-prev/results.csv | 80 +- results-vs-prev/tcwg-benchmark-results.log | 3140 +- results_id | 2 +- 55 files changed, 637957 insertions(+), 669245 deletions(-) delete mode 100644 01-reset_artifacts/patch-env.sh create mode 100644 10-check_regression/bmk-specific-variability.csv delete mode 100644 10-check_regression/mail-body.txt delete mode 100644 10-check_regression/mail-subject.txt create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-arm-master-O2 updated (99c868a92b -> f148fc7f14)

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-code_size-spec2k6/gnu-arm-master-O2 in repository toolchain/ci/base-artifacts. from 99c868a92b 3: onsuccess: #5: 1: [TCWG CI] Success after binutils/gcc/gl [...] new f148fc7f14 4: onsuccess: #6: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] 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 2088 -> 2076 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 27372 -> 27208 bytes 04-build_abe-stage1/console.log.xz | Bin 89676 -> 89460 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 7588 -> 8356 bytes 07-build_abe-glibc/console.log.xz | Bin 234064 -> 233096 bytes 08-build_abe-stage2/console.log.xz | Bin 210976 -> 210040 bytes 09-benchmark/benchmark-build.log | 106 +- 09-benchmark/benchmark.log | 104 +- 09-benchmark/console.log.xz | Bin 4208 -> 4228 bytes 10-check_regression/bmk-specific-variability.csv | 138 +- 10-check_regression/console.log.xz | Bin 17340 -> 15428 bytes 10-check_regression/mail-body.txt | 13 - 10-check_regression/mail-subject.txt | 1 - .../output-bmk-results/exe.improvement | 1 - .../output-bmk-results/exe.improvement.diff | 1 - .../output-bmk-results/exe.regression | 2 + .../output-bmk-results/exe.regression.diff | 1 + .../output-bmk-results/symbol.improvement | 10 +- .../output-bmk-results/symbol.improvement.diff | 2 +- .../output-bmk-results/symbol.regression | 15 +- .../output-bmk-results/symbol.regression.diff | 2 +- 11-update_baseline/console.log | 9 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 3 + mail/changes-list-long.txt | 20 - mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 34 - mail/short-diag.txt | 1 - manifest.sh | 38 +- results-vs-first/compare-results-internal.csv | 213 +- results-vs-first/csv-results-0/md5sum.csv | 1936 +- results-vs-first/csv-results-0/results.csv | 1013086 ++++++++-------- results-vs-first/csv-results-0/size.csv | 1016530 ++++++++--------- results-vs-first/csv-results-0/sve.csv | 28912 +- results-vs-first/csv-results-0/vect.csv | 76 +- results-vs-first/csv-results-1/md5sum.csv | 2135 +- results-vs-first/csv-results-1/perf.csv | 2686 +- results-vs-first/csv-results-1/results.csv | 998222 ++++++++-------- results-vs-first/csv-results-1/size.csv | 1001444 ++++++++-------- results-vs-first/csv-results-1/sve.csv | 28465 +- results-vs-first/csv-results-1/vect.csv | 60 +- results-vs-first/interesting-symbols.csv | 123 +- results-vs-first/results-brief.csv | 65 +- results-vs-first/results-full.csv | 2530 +- results-vs-first/results-internal.csv | 223 +- results-vs-first/results.csv | 223 +- results-vs-first/tcwg-benchmark-results.log | 3294 +- results-vs-prev/compare-results-internal.csv | 228 +- results-vs-prev/compare-results.csv | 25 +- results-vs-prev/csv-results-0/md5sum.csv | 2485 +- results-vs-prev/csv-results-0/perf.csv | 2478 +- results-vs-prev/csv-results-0/results.csv | 998177 ++++++++-------- results-vs-prev/csv-results-0/size.csv | 1001387 ++++++++-------- results-vs-prev/csv-results-0/sve.csv | 28855 +- results-vs-prev/csv-results-0/vect.csv | 76 +- results-vs-prev/csv-results-1/md5sum.csv | 2133 +- results-vs-prev/csv-results-1/perf.csv | 2686 +- results-vs-prev/csv-results-1/results.csv | 998222 ++++++++-------- results-vs-prev/csv-results-1/size.csv | 1001444 ++++++++-------- results-vs-prev/csv-results-1/sve.csv | 28465 +- results-vs-prev/csv-results-1/vect.csv | 60 +- results-vs-prev/interesting-symbols.csv | 123 +- results-vs-prev/results-brief.csv | 67 +- results-vs-prev/results-full.csv | 2786 +- results-vs-prev/results-internal.csv | 241 +- results-vs-prev/results.csv | 241 +- results-vs-prev/tcwg-benchmark-results.log | 3430 +- results_id | 2 +- 75 files changed, 4103424 insertions(+), 4070923 deletions(-) delete mode 100644 10-check_regression/mail-body.txt delete mode 100644 10-check_regression/mail-subject.txt delete mode 100644 10-check_regression/output-bmk-results/exe.improvement delete mode 100644 10-check_regression/output-bmk-results/exe.improvement.diff create mode 100644 10-check_regression/output-bmk-results/exe.regression create mode 100644 10-check_regression/output-bmk-results/exe.regression.diff create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto updated (f7ed90c3c2 -> 0b3555c806)

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_bootstrap/master-arm-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. discards f7ed90c3c2 212: onsuccess: #55: 2: [TCWG CI] Success after binutils/gcc [...] discards e67613965f 211: onsuccess: #54: 2: [TCWG CI] Success after binutils/gcc [...] discards 7396d73771 210: onsuccess: #53: 2: [TCWG CI] Success after binutils/gcc [...] discards a5b0d8ffd7 209: onsuccess: #52: 2: [TCWG CI] Success after binutils/gcc [...] discards 97bd3fa4ca 208: onsuccess: #51: 2: [TCWG CI] Success after binutils/gcc [...] discards 9a2a9da426 207: onsuccess: #50: 2: [TCWG CI] Success after binutils/gcc [...] discards e2115fb345 206: onsuccess: #49: 2: [TCWG CI] Success after binutils/gcc [...] discards 7cb7bc0b21 205: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] discards f881561c81 204: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] discards 820b708a8e 203: onsuccess: #46: 2: [TCWG CI] Success after binutils/gcc [...] discards 3250334d41 202: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] discards ed42b622a4 201: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] discards 22893ee62e 200: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] discards 6e439fc33b 199: onsuccess: #42: 1: [TCWG CI] Success after gcc: 2 commits discards bab7a9787a 198: force: #41: 1: [TCWG CI] Failure after basepoints/gcc-1 [...] discards 6a04d0d99f 197: force: #40: 2: [TCWG CI] Success after gcc: 40 commits discards 14e1112be8 196: onsuccess: #38: 2: [TCWG CI] Success after binutils: 59 [...] discards d02a4fca51 195: onsuccess: #35: 2: Success after binutils/gcc: 5 commits discards b3f78bd2e5 194: onsuccess: #34: 2: Success after binutils/gcc: 45 commits discards 7ce3cb0dd1 193: onsuccess: #32: 2: Success after binutils/gcc: 42 commits discards 83522d89a3 192: onsuccess: #31: 2: Success after binutils/gcc: 25 commits discards 69896fd72d 191: onsuccess: #30: 2: Success after binutils/gcc: 42 commits discards 4277ae6e65 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits discards 92a58c3bae 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits discards 434f8c7f2a 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits discards fbc7b01148 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits discards 99e30ce1e7 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits discards ea2cdd964b 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits discards 35c2dc2f67 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits discards 9502b8f614 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits discards da0b4d502d 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits discards 1adde1e59c 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits discards 955de34bb8 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits discards cfa02f36ab 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits discards 2642b0cedd 178: onsuccess: #16: 0: Success after binutils: 15 commits discards 6454b4e915 177: force: #15: 0: Failure after gdb-13-branchpoint-1318-g4 [...] discards 519ea477c9 176: force: #14: 2: Success after binutils: 18 commits discards b5b5085023 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits discards b055574764 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits discards c8643e6d6a 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits discards 4720234c15 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards 89704e42af 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits discards 1b94295c1b 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits discards c173630edf 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits discards 3edb1e6bcd 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits discards 24fab38563 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards ad7f198d67 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits discards 2228159d38 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits discards 61dec778c9 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits discards 4b8ed6ea6d 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits discards f822bc3273 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits discards 20fecea004 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits discards c2d5c8bf18 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits discards 4c4a1cc0c4 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits discards 5b17619809 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits discards bc8060c7bf 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits discards 7a6d09c2be 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits discards d9283d504e 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits discards 9a8e3e676e 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits discards 2c42e0ebbd 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits discards 612d0e5900 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits discards bceb64ec04 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits discards d321e2cd68 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits discards ade714457d 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits discards 8bf9f89a90 148: onsuccess: #571: 2: Success after gcc: 4 commits discards 4535ce6773 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits discards 2f9d48f116 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits discards 484aa7ec26 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits discards 15e9e6ab7a 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits discards 26ef91bdd3 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits discards 090bc3d2eb 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits discards 52adbfd690 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits discards 86eacd41e0 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits discards e9b18d144c 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits discards 046b627f82 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits discards 5109fd0892 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits discards 297736e4fd 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits discards 4aface975c 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits discards c23087abae 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits discards 9166779836 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits discards 819b7d818d 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits discards 7ce93566d7 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits discards 8a44d12f30 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits discards 98af6a9028 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits discards 7b77de1409 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits discards 6fbec70dbc 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits discards 040cbc8c71 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits discards 0c4060cbb4 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits discards 6f13b3e08a 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits discards 2090b7d1ac 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits discards ece22a43b0 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits discards 6ffa56f9d5 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits discards 2ed2c1a89f 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits discards 7988b01c86 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits discards 1dde8a3a7f 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits discards b8c5d67c01 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits discards cad27075dd 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits discards 5529a27ab1 115: onsuccess: #530: 2: Success after binutils/gcc: 9 commits discards 39898f892f 114: onsuccess: #529: 2: Success after binutils/gcc: 4 commits discards 0474a6cf4b 113: onsuccess: #528: 2: Success after binutils/gcc: 187 commits discards 1c5915b356 112: onsuccess: #527: 1: Success after binutils: 10 commits new d2affdc636 112: onsuccess: #527: 1: Success after binutils: 10 commits new f32bfd2c3d 113: onsuccess: #528: 2: Success after binutils/gcc: 187 commits new 84ba01abd0 114: onsuccess: #529: 2: Success after binutils/gcc: 4 commits new 4f9646a309 115: onsuccess: #530: 2: Success after binutils/gcc: 9 commits new be62b67953 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits new 66ae0095de 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits new 4801bfd70c 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits new a64f5ae78a 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits new 2db29c3915 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits new d86ab662bc 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits new 760e03b063 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits new 2136923b23 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits new 863e834de7 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits new d25d4be220 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits new 20695f9cea 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits new 36c6516c2d 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits new d764d18638 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits new de89f89a96 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits new e197890536 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits new a978a852da 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits new 1bc869c3fa 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits new 709c1986fc 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits new 5b23bcaea0 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits new e539682e0c 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits new 871ca1344a 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits new f1275ed1cb 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits new cb6123aa8b 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits new 1780f3518a 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits new 733f2b4e3e 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits new a73f7bde06 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits new 501409999a 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits new 9e209d8a4e 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits new ebf184dea3 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits new 74e9ac19b8 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits new c73ec94e03 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits new 936e956cb4 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits new 02b7f939ce 148: onsuccess: #571: 2: Success after gcc: 4 commits new 7c6b2448d7 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits new 36ec5701c1 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits new f59e0cb385 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits new 3b1dfcdbf9 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits new aa9579ade4 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits new b7364c672d 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits new d442f2ecc3 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits new c28f26cbf3 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits new a37054e407 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits new c1bc2e2d2a 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits new eca8b0e57f 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits new d8317fc0a2 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits new e9d6b83af3 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits new 9c1e48c346 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits new 670e5ca4c8 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits new 27f554239e 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits new a131def7d2 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits new 7cb985a0ec 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits new 7e7a58f355 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new 3d7b09fd9f 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits new e20c23e3e1 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits new 989a06aabe 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits new e5d45df7a1 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits new 7bbe1e9737 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 7e211e9e8b 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits new 9c19b0a6e2 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits new 8c417f7769 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits new 2fad8fac35 176: force: #14: 2: Success after binutils: 18 commits new 7db24dd968 177: force: #15: 0: Failure after gdb-13-branchpoint-1318-g4 [...] new 9331d97417 178: onsuccess: #16: 0: Success after binutils: 15 commits new fb8d07a714 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits new ff509c17a5 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits new 03b5fa1611 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits new 2d7bf5d4e2 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits new 746d27f789 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits new d724836a7c 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits new 2bedbdec2d 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits new 0957f9041b 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits new 455ce1d77b 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits new 98c9330706 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits new 1d7ed8fd0d 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits new 0f02fd8e0e 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits new e9c01166eb 191: onsuccess: #30: 2: Success after binutils/gcc: 42 commits new ffc3df201f 192: onsuccess: #31: 2: Success after binutils/gcc: 25 commits new 7ae70a32f4 193: onsuccess: #32: 2: Success after binutils/gcc: 42 commits new 03b7ef4da0 194: onsuccess: #34: 2: Success after binutils/gcc: 45 commits new ea628a4b15 195: onsuccess: #35: 2: Success after binutils/gcc: 5 commits new f0959c7215 196: onsuccess: #38: 2: [TCWG CI] Success after binutils: 59 [...] new 7318b0cdca 197: force: #40: 2: [TCWG CI] Success after gcc: 40 commits new 36564e7ba2 198: force: #41: 1: [TCWG CI] Failure after basepoints/gcc-1 [...] new 97e5ef8ee3 199: onsuccess: #42: 1: [TCWG CI] Success after gcc: 2 commits new f3f26255eb 200: onsuccess: #43: 2: [TCWG CI] Success after binutils/gcc [...] new 3aa22e48ca 201: onsuccess: #44: 2: [TCWG CI] Success after binutils/gcc [...] new bf1be4dbcd 202: onsuccess: #45: 2: [TCWG CI] Success after binutils/gcc [...] new df86cb9451 203: onsuccess: #46: 2: [TCWG CI] Success after binutils/gcc [...] new c76f9bf83e 204: onsuccess: #47: 2: [TCWG CI] Success after binutils/gcc [...] new 0b7a867af8 205: onsuccess: #48: 2: [TCWG CI] Success after binutils/gcc [...] new a4c55265e1 206: onsuccess: #49: 2: [TCWG CI] Success after binutils/gcc [...] new 33201b9a2f 207: onsuccess: #50: 2: [TCWG CI] Success after binutils/gcc [...] new 908303cda0 208: onsuccess: #51: 2: [TCWG CI] Success after binutils/gcc [...] new 9cfa900c23 209: onsuccess: #52: 2: [TCWG CI] Success after binutils/gcc [...] new d161b4d5f8 210: onsuccess: #53: 2: [TCWG CI] Success after binutils/gcc [...] new 0e847d59ff 211: onsuccess: #54: 2: [TCWG CI] Success after binutils/gcc [...] new c237ee30d7 212: onsuccess: #55: 2: [TCWG CI] Success after binutils/gcc [...] new 0b3555c806 213: onsuccess: #56: 2: [TCWG CI] https://ci.linaro.org/job/ [...] 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 (f7ed90c3c2) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 1948 -> 1964 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2532 bytes 04-build_abe-binutils/console.log.xz | Bin 49328 -> 48800 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 606088 -> 612756 bytes 06-check_regression/console.log.xz | Bin 2704 -> 1152 bytes 07-update_baseline/console.log | 42 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- jenkins/notify.sh | 3 ++ mail/changes-list-long.txt | 9 ----- mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 22 ----------- mail/short-diag.txt | 1 - manifest.sh | 22 ++++++----- 16 files changed, 40 insertions(+), 67 deletions(-) create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (ea965abcd8 -> 905ae4246a)

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-aarch64 in repository toolchain/ci/base-artifacts. discards ea965abcd8 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] discards 9cbd40898e 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits discards c5d9d57e39 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] discards 2de925a9f8 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] discards 093e39b41f 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits discards 2f7c428c1b 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] discards 39eccc32d4 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] discards 1ff28223e1 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits discards 891e73f402 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] discards 0102b21c0c 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] discards 397701c790 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 9c1a12fca8 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 776c43ed5d 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits discards a1237cbb55 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 409f592fe2 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] discards 7dd5694828 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] discards d0d669cfe6 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] discards b62e66932a 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 6af8ef6ba1 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] discards b8056ccd81 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards be0d03d28d 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 1b11780972 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 5e745c425c 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 306cdc2afe 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] discards c44bfc6fd0 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards c804d5d343 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards cf2b667869 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 0aec0451a4 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] discards bbfff59a8d 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] discards f9db332900 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] discards c608cb50e1 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] discards ccf2104dfe 214: onsuccess: #47: 1: Success after gdb: 21 commits discards a63209264a 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] discards 06642a428f 212: force: #45: 1: Success after gdb: 22 commits discards 462d05a055 211: onsuccess: #44: 1: Success after linux: 26 commits discards e914517d4c 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] discards efa71bc302 209: force: #37: 1: Success after baseline build: no new commits discards 8ee88383c5 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards df50cce495 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 365c122362 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards eb4001cbcf 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards c45b091d33 204: force: #26: : Failure after baseline build: no new commits discards 5da67d9411 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards ef531a8d00 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 1ecaec4e80 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards f39e4e33fb 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards d5e2e494f9 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 651063195a 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 3618e18ecf 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 5a3381d692 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 9e66c0f377 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 70d98f4edd 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards bfede98a20 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards f05889dd64 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 631ab5574a 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 4c65c13aa0 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards f15ee841ab 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 31df5b1b45 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 4239580d5a 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 260f023993 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards bc2eab12d8 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards b626968507 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] discards 6a5f851cbe 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] discards eb63d8f823 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] discards 3287b22e1c 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] discards 555a22256d 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] discards 5ffb17ff69 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] discards e063a805c9 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] discards 03cb6dbbfb 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] discards 1e0e3ba4f3 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] discards fadda48599 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] discards 0700424bd5 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] discards c5de6ab572 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] discards 7e4fadfeae 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] discards 08649a5376 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] discards e70178da8e 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards c90b80325f 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 9fc13b06ce 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 8a20614ffd 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 86c823be2e 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards 0c1a17aae7 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards 028dcff40c 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 9b760ff4b6 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 970beab388 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards 244ea8937b 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards 303be71b97 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards 0ccbe84cee 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 636faae866 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 246f0cfa6a 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 9388649441 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 8dfaba13c7 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards b361fa10ca 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 447b2951ae 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards 36252e9796 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 44f4e44037 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards de681d9743 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 58f801b4dd 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 5299c3832f 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 04e813e57d 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards 8b25317e5a 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards eeff592f2b 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 4cf0ee8de0 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new f94ac1da83 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 560c436913 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new ea81f7e16e 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 6592157e73 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 2e65186da3 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 031f894e67 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 3e9996d5f9 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 59968ac5e4 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 6aae0be70f 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 355f32be22 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new d12a0e46cb 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new 0756e2e400 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new fa74c010c8 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 23b16d4613 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new 96ff5b259d 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new d1b61b69dc 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 4fbe56cefe 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new bd5995549b 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new 8df9761b5f 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new 47f481f209 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new b2a9482e61 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new f67afc4e16 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new 061402460f 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new d39829fea6 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 6d5e1e8759 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new 5cfdbf334b 171: onsuccess: #964: 1: Success after binutils/gcc/linux/gl [...] new 35ccecbea7 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/gd [...] new 8d07842166 173: onsuccess: #966: 1: Success after binutils/gcc/linux/gl [...] new b0dad22231 174: onsuccess: #967: 1: Success after binutils/gcc/linux/gd [...] new fd1cc9871a 175: onsuccess: #968: 1: Success after binutils/gcc/linux/gl [...] new d9092ffdd3 176: onsuccess: #969: 1: Success after binutils/gcc/linux/gl [...] new 3f19ffb4af 177: onsuccess: #970: 1: Success after binutils/gcc/linux/gl [...] new 5afae13c65 178: onsuccess: #971: 1: Success after binutils/gcc/linux/gl [...] new efa0871e5d 179: onsuccess: #972: 1: Success after binutils/gcc/linux/gl [...] new 770a105874 180: onsuccess: #973: 1: Success after binutils/gcc/linux/gd [...] new f035f0aaba 181: onsuccess: #974: 1: Success after binutils/gcc/linux/gl [...] new 47bbf224aa 182: onsuccess: #975: 1: Success after binutils/gcc/linux/gl [...] new 6af729e48c 183: onsuccess: #976: 1: Success after binutils/gcc/linux/gl [...] new cec8944cbd 184: onsuccess: #977: 1: Success after binutils/gcc/linux/gl [...] new bd27d76cea 185: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 156e664459 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 3fc4546941 187: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new d0f595c52f 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new f6a1e31a3d 189: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 1847233e3e 190: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new bd12eff3ff 191: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new b8998e3f71 192: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 373778287b 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new d69b5dabb2 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new e7a42fabec 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 4315481bd4 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 8a0d327ef1 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 296f5a1e25 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new c64dcb898d 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 9d43365333 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new e0ad26074d 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 1f61991179 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new d3f533f8d0 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 2562ec7183 204: force: #26: : Failure after baseline build: no new commits new 4584cccea8 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 75d7a07d3c 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 9dd9e2e24c 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 57ea8969bb 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new db40e0a6db 209: force: #37: 1: Success after baseline build: no new commits new 054a52cc8e 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-gd [...] new cc2bc34277 211: onsuccess: #44: 1: Success after linux: 26 commits new 18300479d7 212: force: #45: 1: Success after gdb: 22 commits new 2f2cefbcab 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g9 [...] new fa69c77802 214: onsuccess: #47: 1: Success after gdb: 21 commits new 4b4bc63c1e 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gdb [...] new 6ef14f7538 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gdb [...] new fcc9d9082c 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gdb [...] new 937ebee9a5 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gcc [...] new 6864db3da2 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 305837ecb0 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 56a84187ea 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new fe4c51f2b4 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/gcc [...] new 20f6ccd210 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 191cce1f3f 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 49755b98f3 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 92e2ceefc5 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new e95d9e310f 227: force: #81: 1: [TCWG CI] Failure after baseline build: [...] new 108d698a1b 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 8678b0569a 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.9000- [...] new 84a96764d8 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37.9 [...] new 53b8e524d0 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/gcc [...] new 3f7abf6f0b 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new ab0b488fa8 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: 2 commits new 281dfef30d 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 5b5b76890c 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new ca2d4b2a24 236: onsuccess: #96: 1: [TCWG CI] Success after binutils/gcc [...] new a592ecc632 237: onsuccess: #97: 1: [TCWG CI] Success after binutils/gcc [...] new cf59be03fa 238: onsuccess: #100: 1: [TCWG CI] Success after gdb: 8 commits new 4aded4a280 239: onsuccess: #105: 1: [TCWG CI] Success after binutils/gc [...] new b7d92261db 240: onsuccess: #106: 1: [TCWG CI] Success after binutils/gc [...] new 639e72943c 241: onsuccess: #111: 1: [TCWG CI] Success after gcc: 6 commits new 8a376d5845 242: force: #114: 1: [TCWG CI] Failure after baseline build: [...] new 536bd4fd8a 243: onsuccess: #116: 1: [TCWG CI] Success after binutils/gc [...] new e5db4ada98 244: onsuccess: #117: 1: [TCWG CI] Success after gdb: 7 commits new 46c70158b6 245: onsuccess: #119: 1: [TCWG CI] Success after binutils/gc [...] new 905ae4246a 246: force: #121: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] 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 (ea965abcd8) \ 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 2060 -> 2192 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 35360 -> 35520 bytes 04-build_abe-gcc/console.log.xz | Bin 203868 -> 203728 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8800 -> 8864 bytes 07-build_abe-glibc/console.log.xz | Bin 240720 -> 241556 bytes 08-build_abe-gdb/console.log.xz | Bin 34892 -> 34848 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3848 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2752 -> 2840 bytes 11-check_regression/console.log.xz | Bin 5172 -> 1588 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 91 +- 12-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- jenkins/notify.sh | 3 + mail/changes-list-long.txt | 22 - mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 30 - mail/short-diag.txt | 1 - manifest.sh | 28 +- sumfiles/gdb.log.0.xz | Bin 2007704 -> 1946612 bytes sumfiles/gdb.log.1.xz | Bin 15132 -> 20324 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 5388 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 5428 bytes sumfiles/gdb.sum | 1688 +++++++++++++++++++-------------- sumfiles/gdb.sum.0 | 1688 +++++++++++++++++++-------------- sumfiles/gdb.sum.1 | 251 ++++- sumfiles/gdb.sum.2 | 182 ++++ sumfiles/gdb.sum.3 | 182 ++++ 31 files changed, 2651 insertions(+), 1593 deletions(-) create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt create mode 100644 sumfiles/gdb.log.2.xz create mode 100644 sumfiles/gdb.log.3.xz create mode 100644 sumfiles/gdb.sum.2 create mode 100644 sumfiles/gdb.sum.3 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[binutils-gdb] branch master updated (7bb9e56c6a6 -> d8ca1d2fc58)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 7bb9e56c6a6 Replace an assertion in the dwarf code with a warning message. new d8ca1d2fc58 gdb, doc: correct argument description for info connections [...] 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: gdb/doc/gdb.texinfo | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/gnu-aarch64-master-O2 updated (e4c50858b0 -> f9714378de)

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-code_speed-cpu2017rate/gnu-aarch64-master-O2 in repository toolchain/ci/base-artifacts. from e4c50858b0 17: onsuccess: #20: 1: [TCWG CI] Success after binutils/gcc/ [...] new f9714378de 18: onsuccess: #21: 1: [TCWG CI] Success after binutils/gcc/ [...] 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 2056 -> 2404 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2556 bytes 03-build_abe-binutils/console.log.xz | Bin 27196 -> 27256 bytes 04-build_abe-stage1/console.log.xz | Bin 71528 -> 71048 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 7588 -> 8352 bytes 07-build_abe-glibc/console.log.xz | Bin 242876 -> 241740 bytes 08-build_abe-stage2/console.log.xz | Bin 176820 -> 176164 bytes 09-benchmark/benchmark-build.log | 138 +- 09-benchmark/benchmark.log | 136 +- 09-benchmark/console.log.xz | Bin 4236 -> 4240 bytes 10-check_regression/bmk-specific-variability.csv | 116 +- 10-check_regression/console.log.xz | Bin 16536 -> 17768 bytes .../output-bmk-results/symbol.improvement | 6 +- .../output-bmk-results/symbol.improvement.diff | 2 +- .../output-bmk-results/symbol.regression | 5 +- .../output-bmk-results/symbol.regression.diff | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 44 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +- manifest.sh | 36 +- results-vs-first/compare-results-internal.csv | 173 +- results-vs-first/csv-results-0/md5sum.csv | 2552 +- results-vs-first/csv-results-0/results.csv | 773090 ++++++++--------- results-vs-first/csv-results-0/size.csv | 777890 +++++++++--------- results-vs-first/csv-results-0/sve.csv | 24318 +- results-vs-first/csv-results-0/vect.csv | 738 +- results-vs-first/csv-results-1/md5sum.csv | 2417 +- results-vs-first/csv-results-1/perf.csv | 2808 +- results-vs-first/csv-results-1/results.csv | 738867 ++++++++--------- results-vs-first/csv-results-1/size.csv | 743461 ++++++++--------- results-vs-first/csv-results-1/sve.csv | 24206 +- results-vs-first/csv-results-1/vect.csv | 642 +- results-vs-first/interesting-symbols.csv | 115 +- results-vs-first/results-brief.csv | 56 +- results-vs-first/results-full.csv | 2655 +- results-vs-first/results-internal.csv | 183 +- results-vs-first/results.csv | 183 +- results-vs-first/tcwg-benchmark-results.log | 2660 +- results-vs-prev/compare-results-internal.csv | 177 +- results-vs-prev/compare-results.csv | 3 +- results-vs-prev/csv-results-0/md5sum.csv | 2239 +- results-vs-prev/csv-results-0/perf.csv | 2819 +- results-vs-prev/csv-results-0/results.csv | 733677 +++++++++-------- results-vs-prev/csv-results-0/size.csv | 727424 ++++++++-------- results-vs-prev/csv-results-0/sve.csv | 24336 +- results-vs-prev/csv-results-0/vect.csv | 696 +- results-vs-prev/csv-results-1/md5sum.csv | 2413 +- results-vs-prev/csv-results-1/perf.csv | 2808 +- results-vs-prev/csv-results-1/results.csv | 738867 ++++++++--------- results-vs-prev/csv-results-1/size.csv | 743461 ++++++++--------- results-vs-prev/csv-results-1/sve.csv | 24206 +- results-vs-prev/csv-results-1/vect.csv | 642 +- results-vs-prev/interesting-symbols.csv | 115 +- results-vs-prev/results-brief.csv | 56 +- results-vs-prev/results-full.csv | 2861 +- results-vs-prev/results-internal.csv | 187 +- results-vs-prev/results.csv | 187 +- results-vs-prev/tcwg-benchmark-results.log | 3440 +- results_id | 2 +- save-temps/500.perlbench_r.tar.xz | Bin 5106636 -> 5157932 bytes save-temps/502.gcc_r.tar.xz | Bin 23301204 -> 23241820 bytes save-temps/503.bwaves_r.tar.xz | Bin 134676 -> 134864 bytes save-temps/505.mcf_r.tar.xz | Bin 100752 -> 101016 bytes save-temps/507.cactuBSSN_r.tar.xz | Bin 8432084 -> 8169792 bytes save-temps/508.namd_r.tar.xz | Bin 2299988 -> 2255392 bytes save-temps/510.parest_r.tar.xz | Bin 43590248 -> 44512440 bytes save-temps/511.povray_r.tar.xz | Bin 2936452 -> 2948492 bytes save-temps/519.lbm_r.tar.xz | Bin 107276 -> 107464 bytes save-temps/520.omnetpp_r.tar.xz | Bin 8079864 -> 8078748 bytes save-temps/521.wrf_r.tar.xz | Bin 43999480 -> 44038452 bytes save-temps/523.xalancbmk_r.tar.xz | Bin 26015372 -> 26226724 bytes save-temps/525.x264_r.tar.xz | Bin 3666652 -> 3673320 bytes save-temps/526.blender_r.tar.xz | Bin 35853152 -> 35639196 bytes save-temps/527.cam4_r.tar.xz | Bin 14814100 -> 14828124 bytes save-temps/531.deepsjeng_r.tar.xz | Bin 301024 -> 301340 bytes save-temps/538.imagick_r.tar.xz | Bin 4658240 -> 4726488 bytes save-temps/541.leela_r.tar.xz | Bin 1078124 -> 1129480 bytes save-temps/544.nab_r.tar.xz | Bin 505600 -> 505288 bytes save-temps/548.exchange2_r.tar.xz | Bin 479536 -> 479204 bytes save-temps/549.fotonik3d_r.tar.xz | Bin 883536 -> 883508 bytes save-temps/554.roms_r.tar.xz | Bin 1903820 -> 1900104 bytes save-temps/557.xz_r.tar.xz | Bin 796552 -> 796588 bytes 88 files changed, 3042302 insertions(+), 3065857 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

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

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 a1bfdaadf7 241: onsuccess: #50: 6: [TCWG CI] Success after binutils/gcc [...] discards e844928327 240: onsuccess: #49: 6: [TCWG CI] Success after binutils/gcc [...] discards 1092611f88 239: onsuccess: #48: 6: [TCWG CI] Success after binutils/gcc [...] discards ba1fe48128 238: onsuccess: #47: 6: [TCWG CI] Success after binutils/gcc [...] discards 7a129c37da 237: onsuccess: #46: 6: [TCWG CI] Success after binutils/gcc [...] discards b528796bfc 236: onsuccess: #45: 6: [TCWG CI] Success after binutils/gcc [...] discards a7c5fe96e5 235: onsuccess: #44: 6: [TCWG CI] Success after binutils/gcc [...] discards c4dd5fa0ba 234: onsuccess: #43: 6: [TCWG CI] Success after binutils/gcc [...] discards 420ac470fa 233: onsuccess: #42: 6: [TCWG CI] Success after binutils/gcc [...] discards 2b6102597f 232: onsuccess: #41: 6: [TCWG CI] Success after binutils/gcc [...] discards 7954a277ec 231: onsuccess: #39: 6: [TCWG CI] Success after binutils/gcc [...] discards 6b84bfacae 230: onsuccess: #38: 6: [TCWG CI] Success after binutils/gcc [...] discards 8c2f27b667 229: onsuccess: #37: 6: [TCWG CI] Success after binutils/gcc [...] discards 0673deeea0 228: onsuccess: #35: 6: Success after binutils/gcc/linux/gli [...] discards e394dfdfea 227: onsuccess: #34: 6: Success after binutils/gcc/linux/gdb [...] discards 12708845c1 226: onsuccess: #32: 6: Success after binutils/gcc/linux/gdb [...] discards 37c7cec580 225: onsuccess: #31: 6: Success after binutils/gcc/linux/gli [...] discards dfec3400e6 224: onsuccess: #30: 6: Success after binutils/gcc/linux/gdb [...] discards b001bc1719 223: onsuccess: #29: 6: Success after binutils/gcc/linux/gdb [...] discards 9f16e60cc8 222: onsuccess: #28: 6: Success after binutils/gcc/linux/gdb [...] discards 739953ad02 221: onsuccess: #26: 6: Success after binutils/gcc/linux/gdb [...] discards 1db13a336f 220: onsuccess: #25: 6: Success after binutils/gcc/linux/gdb [...] discards a86a48deda 219: onsuccess: #24: 6: Success after binutils/gcc/linux/gli [...] discards 11dcbb4e66 218: onsuccess: #23: 6: Success after binutils/gcc/linux/gdb [...] discards d717d34084 217: onsuccess: #22: 6: Success after binutils/gcc/linux/gli [...] discards 3340dbe71d 216: onsuccess: #21: 6: Success after binutils/gcc/linux/gdb [...] discards 33e724f9c0 215: onsuccess: #20: 6: Success after binutils/gcc/linux/gli [...] discards 64e799576f 214: onsuccess: #19: 6: Success after binutils/gcc/linux/gdb [...] discards 5e20295374 213: onsuccess: #18: 6: Success after binutils/gcc/linux/gli [...] discards dc0c507fc4 212: onsuccess: #17: 6: Success after binutils/gcc/linux/gli [...] discards 76935c2729 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gli [...] discards 480cf0297e 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gdb [...] discards cba812570d 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gdb [...] discards 2203c7b59e 208: onsuccess: #9: 6: Success after binutils/gcc/linux/glib [...] discards a0d7479960 207: onsuccess: #8: 6: Success after binutils/gcc/linux/glib [...] discards ce31e06c57 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb: [...] discards ab1edc61dc 205: onsuccess: #6: 6: Success after binutils/gcc/linux/glib [...] discards c1e56aa9e5 204: onsuccess: #5: 6: Success after binutils/gcc/linux/glib [...] discards 4f71e78082 203: onsuccess: #4: 6: Success after binutils/gcc/linux/glib [...] discards 070e91e2b4 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb: [...] discards 706b09e2fc 201: onsuccess: #2: 6: Success after binutils/gcc/linux/glib [...] discards 8a734db34e 200: onsuccess: #1: 6: Success after binutils/gcc/linux/glib [...] discards a887de3c45 199: onsuccess: #630: 6: Success after binutils/gcc/linux/gl [...] discards 78a5bd9733 198: onsuccess: #629: 6: Success after binutils/gcc/linux/gl [...] discards ddd2222d3c 197: onsuccess: #628: 6: Success after binutils/gcc/linux/gl [...] discards cabd34439c 196: onsuccess: #621: 6: Success after binutils/gcc/linux/gl [...] discards 814d80da88 195: onsuccess: #620: 6: Success after binutils/gcc/linux/gl [...] discards cbbee29fe9 194: onsuccess: #619: 6: Success after binutils/gcc/linux/gd [...] discards 3187631d30 193: onsuccess: #618: 6: Success after binutils/gcc/linux/gl [...] discards 27ae0c810e 192: onsuccess: #617: 6: Success after binutils/gcc/linux/gl [...] discards b15bad2280 191: onsuccess: #615: 6: Success after binutils/gcc/linux/gl [...] discards 9f9f333ff1 190: onsuccess: #614: 6: Success after binutils/gcc/linux/gl [...] discards a7dc2d00b6 189: onsuccess: #613: 6: Success after binutils/gcc/linux/gl [...] discards a3b779981e 188: onsuccess: #612: 6: Success after binutils/gcc/linux/gd [...] discards 73e8b6541c 187: onsuccess: #611: 6: Success after binutils/gcc/linux/gl [...] discards 1cd8d9f795 186: onsuccess: #610: 6: Success after binutils/gcc/linux/gl [...] discards b9ffa195cb 185: onsuccess: #609: 6: Success after binutils/gcc/linux/gl [...] discards c57f4ce852 184: onsuccess: #608: 6: Success after binutils/gcc/linux/gl [...] discards 55b66dffe1 183: onsuccess: #607: 6: Success after binutils/gcc/linux/gd [...] discards c67c12fe0c 182: onsuccess: #606: 6: Success after binutils/gcc/linux/gl [...] discards 7552ec4318 181: onsuccess: #605: 6: Success after binutils/gcc/linux/gd [...] discards 5842368e81 180: onsuccess: #604: 6: Success after binutils/gcc/linux/gl [...] discards b8040cb5a7 179: onsuccess: #603: 6: Success after binutils/gcc/linux/gl [...] discards 09723bab83 178: onsuccess: #602: 6: Success after binutils/gcc/linux/gd [...] discards 8d293606be 177: onsuccess: #601: 6: Success after binutils/gcc/linux/gd [...] discards 6ed4f42f6b 176: onsuccess: #600: 6: Success after binutils/gcc/linux/gd [...] discards b821c9f8ab 175: onsuccess: #599: 6: Success after binutils/gcc/linux/gd [...] discards 12f61c73d8 174: onsuccess: #598: 6: Success after binutils/gcc/linux/gl [...] discards 8f1fcfa0f9 173: onsuccess: #597: 6: Success after binutils/gcc/linux/gl [...] discards e4103bfcfc 172: onsuccess: #596: 6: Success after binutils/gcc/linux/gl [...] discards 29304ba4a5 171: onsuccess: #595: 6: Success after binutils/gcc/linux/gl [...] discards 275a1d3367 170: onsuccess: #594: 6: Success after binutils/gcc/linux/gl [...] discards e143aaef72 169: onsuccess: #593: 6: Success after binutils/gcc/linux/gl [...] discards 150324dd6e 168: onsuccess: #591: 6: Success after binutils/gcc/linux/gd [...] discards 8f29278e6e 167: onsuccess: #590: 6: Success after binutils/gcc/linux/gl [...] discards af8054565d 166: onsuccess: #589: 6: Success after binutils/gcc/linux/gl [...] discards fe5998ecc8 165: onsuccess: #588: 6: Success after binutils/gcc/linux/gl [...] discards de4ae59481 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/gd [...] discards 70c0d2e5c7 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] discards d5713a9d1a 162: onsuccess: #579: 6: Success after gcc: 11 commits discards 421519b5cf 161: onsuccess: #578: 6: Success after binutils: 15 commits discards a8abbe2a46 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] discards 65aafed973 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] discards 2461570b5b 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] discards 818b87002b 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits discards 886b601b17 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits discards 53e362b212 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits discards 54f84fa10a 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] discards c730a021ef 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits discards 5ce01bdc89 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] discards 29a3ba4265 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] discards a110dffb76 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] discards e1bdecfb54 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] discards 3af765e5c9 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] discards f94d7a8646 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] discards fffeb57d2a 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits discards e55f2fe00c 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] discards 25329c65b9 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] discards 7fb7140c17 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] discards dd32ecaac6 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] discards 1ce1ee7c2e 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] new 06806a706f 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] new c2ac03dee1 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] new df00d5ddeb 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] new 59c1f002d0 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] new b6a2a29c7d 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] new e4413304c6 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits new 9b2debb896 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] new b37de889aa 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] new 4c6b291555 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] new b91782e8b4 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] new 5db96fa693 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] new 7f70714de7 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] new b7b2e0e94d 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits new 2555527d39 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] new 268bed018c 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits new c0f05a1d73 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits new 0e710009d3 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits new e414f89395 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] new 7d923bd19a 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] new a4210fda09 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] new 4d2de65101 161: onsuccess: #578: 6: Success after binutils: 15 commits new a01cf2e9b4 162: onsuccess: #579: 6: Success after gcc: 11 commits new 299735e74d 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] new b68f6d838c 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/gd [...] new dbbe89bb65 165: onsuccess: #588: 6: Success after binutils/gcc/linux/gl [...] new e580c26412 166: onsuccess: #589: 6: Success after binutils/gcc/linux/gl [...] new 44efdee791 167: onsuccess: #590: 6: Success after binutils/gcc/linux/gl [...] new 499bc6ab75 168: onsuccess: #591: 6: Success after binutils/gcc/linux/gd [...] new 8caa38fa02 169: onsuccess: #593: 6: Success after binutils/gcc/linux/gl [...] new 362e4b4278 170: onsuccess: #594: 6: Success after binutils/gcc/linux/gl [...] new b2009f7903 171: onsuccess: #595: 6: Success after binutils/gcc/linux/gl [...] new ef87e4c2e8 172: onsuccess: #596: 6: Success after binutils/gcc/linux/gl [...] new 2cf03a89f0 173: onsuccess: #597: 6: Success after binutils/gcc/linux/gl [...] new a095f34614 174: onsuccess: #598: 6: Success after binutils/gcc/linux/gl [...] new 36d51a56f5 175: onsuccess: #599: 6: Success after binutils/gcc/linux/gd [...] new 7f86a70be6 176: onsuccess: #600: 6: Success after binutils/gcc/linux/gd [...] new eeb30bb57e 177: onsuccess: #601: 6: Success after binutils/gcc/linux/gd [...] new d25afed234 178: onsuccess: #602: 6: Success after binutils/gcc/linux/gd [...] new e7996114d7 179: onsuccess: #603: 6: Success after binutils/gcc/linux/gl [...] new 2d67fc7337 180: onsuccess: #604: 6: Success after binutils/gcc/linux/gl [...] new 0cde15f4e9 181: onsuccess: #605: 6: Success after binutils/gcc/linux/gd [...] new 90c9f9f36a 182: onsuccess: #606: 6: Success after binutils/gcc/linux/gl [...] new 2967c5429f 183: onsuccess: #607: 6: Success after binutils/gcc/linux/gd [...] new 0585ddefac 184: onsuccess: #608: 6: Success after binutils/gcc/linux/gl [...] new c6335ef7a6 185: onsuccess: #609: 6: Success after binutils/gcc/linux/gl [...] new 5b9c24ba65 186: onsuccess: #610: 6: Success after binutils/gcc/linux/gl [...] new 601eb9fdaf 187: onsuccess: #611: 6: Success after binutils/gcc/linux/gl [...] new f80e50db93 188: onsuccess: #612: 6: Success after binutils/gcc/linux/gd [...] new ea53cf54e4 189: onsuccess: #613: 6: Success after binutils/gcc/linux/gl [...] new 9d834427f7 190: onsuccess: #614: 6: Success after binutils/gcc/linux/gl [...] new a5b4810fda 191: onsuccess: #615: 6: Success after binutils/gcc/linux/gl [...] new b1d5e4ac37 192: onsuccess: #617: 6: Success after binutils/gcc/linux/gl [...] new d3041818fe 193: onsuccess: #618: 6: Success after binutils/gcc/linux/gl [...] new 6c1f29ce84 194: onsuccess: #619: 6: Success after binutils/gcc/linux/gd [...] new 8c0379a9cc 195: onsuccess: #620: 6: Success after binutils/gcc/linux/gl [...] new 6e20708b78 196: onsuccess: #621: 6: Success after binutils/gcc/linux/gl [...] new 51fdebf7ef 197: onsuccess: #628: 6: Success after binutils/gcc/linux/gl [...] new dbc7aa07fe 198: onsuccess: #629: 6: Success after binutils/gcc/linux/gl [...] new f5163d4575 199: onsuccess: #630: 6: Success after binutils/gcc/linux/gl [...] new 689030d05e 200: onsuccess: #1: 6: Success after binutils/gcc/linux/glib [...] new cbd6f0217b 201: onsuccess: #2: 6: Success after binutils/gcc/linux/glib [...] new 6116f773eb 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb: [...] new 2511f25c27 203: onsuccess: #4: 6: Success after binutils/gcc/linux/glib [...] new 0f44632c02 204: onsuccess: #5: 6: Success after binutils/gcc/linux/glib [...] new 866a6fba4b 205: onsuccess: #6: 6: Success after binutils/gcc/linux/glib [...] new 3b65ffa6c1 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb: [...] new bd34f471ac 207: onsuccess: #8: 6: Success after binutils/gcc/linux/glib [...] new f7640bcc81 208: onsuccess: #9: 6: Success after binutils/gcc/linux/glib [...] new db84126d12 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gdb [...] new daf8c20e19 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gdb [...] new 1f080ef8ad 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gli [...] new 342eff3cbb 212: onsuccess: #17: 6: Success after binutils/gcc/linux/gli [...] new 77d6a6c266 213: onsuccess: #18: 6: Success after binutils/gcc/linux/gli [...] new 6bfacb4595 214: onsuccess: #19: 6: Success after binutils/gcc/linux/gdb [...] new 42fe70742a 215: onsuccess: #20: 6: Success after binutils/gcc/linux/gli [...] new e45e450050 216: onsuccess: #21: 6: Success after binutils/gcc/linux/gdb [...] new 73b9e5d3e6 217: onsuccess: #22: 6: Success after binutils/gcc/linux/gli [...] new d514988cb6 218: onsuccess: #23: 6: Success after binutils/gcc/linux/gdb [...] new 794bf283ec 219: onsuccess: #24: 6: Success after binutils/gcc/linux/gli [...] new c0b94f301d 220: onsuccess: #25: 6: Success after binutils/gcc/linux/gdb [...] new 70daae4b39 221: onsuccess: #26: 6: Success after binutils/gcc/linux/gdb [...] new 4872639770 222: onsuccess: #28: 6: Success after binutils/gcc/linux/gdb [...] new a17e5d1d32 223: onsuccess: #29: 6: Success after binutils/gcc/linux/gdb [...] new 339a1739ca 224: onsuccess: #30: 6: Success after binutils/gcc/linux/gdb [...] new 296c77f4f7 225: onsuccess: #31: 6: Success after binutils/gcc/linux/gli [...] new 70f6dc849f 226: onsuccess: #32: 6: Success after binutils/gcc/linux/gdb [...] new 0cb1da821a 227: onsuccess: #34: 6: Success after binutils/gcc/linux/gdb [...] new e5ebe98b35 228: onsuccess: #35: 6: Success after binutils/gcc/linux/gli [...] new 733a2c0299 229: onsuccess: #37: 6: [TCWG CI] Success after binutils/gcc [...] new 4c1a12b39c 230: onsuccess: #38: 6: [TCWG CI] Success after binutils/gcc [...] new 9e3ae9b9bd 231: onsuccess: #39: 6: [TCWG CI] Success after binutils/gcc [...] new eb1ccc12f8 232: onsuccess: #41: 6: [TCWG CI] Success after binutils/gcc [...] new 916c5c339a 233: onsuccess: #42: 6: [TCWG CI] Success after binutils/gcc [...] new 12d4a6e98f 234: onsuccess: #43: 6: [TCWG CI] Success after binutils/gcc [...] new fe68f4dfda 235: onsuccess: #44: 6: [TCWG CI] Success after binutils/gcc [...] new 2b5dc185e1 236: onsuccess: #45: 6: [TCWG CI] Success after binutils/gcc [...] new 183fb7e6eb 237: onsuccess: #46: 6: [TCWG CI] Success after binutils/gcc [...] new eb0182a430 238: onsuccess: #47: 6: [TCWG CI] Success after binutils/gcc [...] new 62a48a324d 239: onsuccess: #48: 6: [TCWG CI] Success after binutils/gcc [...] new cafdf1bc50 240: onsuccess: #49: 6: [TCWG CI] Success after binutils/gcc [...] new 0051a9580c 241: onsuccess: #50: 6: [TCWG CI] Success after binutils/gcc [...] new 0c5b91428d 242: onsuccess: #51: 6: [TCWG CI] https://ci.linaro.org/job/ [...] 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 (a1bfdaadf7) \ 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 2012 -> 2020 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2548 bytes 04-build_abe-binutils/console.log.xz | Bin 49652 -> 49072 bytes 05-build_abe-gcc/console.log.xz | Bin 234448 -> 234680 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8264 -> 8844 bytes 08-build_abe-glibc/console.log.xz | Bin 233032 -> 233288 bytes 09-build_abe-gdb/console.log.xz | Bin 46552 -> 47040 bytes 10-check_regression/console.log.xz | Bin 3788 -> 1260 bytes 11-update_baseline/console.log | 42 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 3 +++ mail/changes-list-long.txt | 18 --------------- mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 34 ---------------------------- mail/short-diag.txt | 1 - manifest.sh | 40 +++++++++++++++++---------------- 23 files changed, 52 insertions(+), 100 deletions(-) create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[binutils-gdb] branch binutils-2_40-branch updated (7a06052ee66 -> ded035f913e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch binutils-2_40-branch in repository binutils-gdb. from 7a06052ee66 Automatic date update in version.in new ded035f913e lto: Don't add indirect symbols for versioned aliases in IR 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: bfd/elflink.c | 9 ++++++++- ld/testsuite/ld-plugin/lto.exp | 9 +++++++++ ld/testsuite/ld-plugin/pr30281.c | 4 ++++ ld/testsuite/{ld-elfvers/vers23a.map => ld-plugin/pr30281.t} | 3 +-- 4 files changed, 22 insertions(+), 3 deletions(-) create mode 100644 ld/testsuite/ld-plugin/pr30281.c copy ld/testsuite/{ld-elfvers/vers23a.map => ld-plugin/pr30281.t} (55%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023