Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (47ac239e312 -> c353f4a1ae0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64 in repository toolchain/ci/base-artifacts. discards 47ac239e312 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits discards d802877406a 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits discards b7db3710c16 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits discards 03dc0935b8e 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits discards d98e8d4b026 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits discards ea27a6a7126 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits discards 012de16df77 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits discards f06aaa5edfd 381: onsuccess: #2343: 1: Success after gcc: 2 commits discards a616276a5c8 380: onsuccess: #2342: 1: Success after gcc: 3 commits discards 7b38b392b42 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] discards d4eb865ba35 378: onsuccess: #2340: 1: Success after binutils: 2 commits discards 617fe38bb65 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits discards 9969ba2aae4 376: onsuccess: #2338: 1: Success after gcc: 2 commits discards bfb767cf79d 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits discards 153b7b7e5d9 374: onsuccess: #2336: 1: Success after gcc: 4 commits discards e22ad1bcf6a 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits discards 6a30b7d5c22 372: onsuccess: #2334: 1: Success after gcc: 5 commits discards 9d34a58220f 371: onsuccess: #2333: 1: Success after binutils: 5 commits discards bdb8a2d3ca8 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits discards 1773e20944b 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards 483a1a53d13 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards 39dafca763a 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards b2f0ea9c44a 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards f5ea1f68047 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards 90352498e3c 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards 4afed4776bf 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards f7c61ff66b9 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards b75f4034d11 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards 8ae463f3528 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards e7086beffe1 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] discards 37f4ba27ccd 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards f8bfbdd9c86 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards 2ee2e9b4c67 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards f229f590042 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards a4bc381e383 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards b58ecec1564 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards 85bfd720ed8 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards d6d3fd553a5 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards 2c1cea623dc 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards d2d4b62afbd 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards 6eefbf8aa66 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards ea983d95e3d 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards a2feba1b643 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards a7a5033a56d 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards 4edf59a49bd 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards 0479d040533 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards 4e7b3233df9 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards 5e177d182c6 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards d0ce92b89a6 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards 4a83f7afe73 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards 26cfb2084bc 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards 7cfeef6e628 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards a74099fc2a7 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards c62584154b8 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards 804179a852d 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards f2ac1f7e4c1 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] discards 3fdb14af134 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards 04e7a4bfb1c 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] discards fc935c07191 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards b1ee1b41065 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards 4b9dbdbf04b 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] discards 9787aeaa29b 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards e350e46dc68 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards ea0e20796c5 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards d6cf84bfc7e 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards a533247b31b 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards 1269dd92e44 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards 65bc5127a69 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits discards 971d4db0a02 320: onsuccess: #2274: 1: Success after gcc: 5 commits discards 5e834be9aaa 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits discards 0ffd7ce5456 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits discards 4acbd8fc9a9 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits discards 884210185e2 316: onsuccess: #2270: 1: Success after gcc: 2 commits discards 79a6e436e98 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits discards 5e91e41eaf8 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits discards d9890cd2d07 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits discards acc74dc64a9 312: onsuccess: #2265: 1: Success after binutils: 2 commits discards 9ac8ecc863b 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] discards 0b527c26848 310: onsuccess: #2259: 1: Success after binutils: 2 commits discards bc7dce4521f 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] discards 327caee16b4 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] discards 7cca86090c6 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] discards 96cd383aa40 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] discards e3382f91b05 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits discards 53adbda14bc 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits discards d286c7aaa73 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits discards ee7d42bd113 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits discards 6c081c48bbd 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits discards 22154cec17d 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits discards 4abf88ec7ef 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits discards cfa6b09ad76 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits discards 0c0de96f91b 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits discards a6362e9ead6 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits discards 20d4bd12445 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits discards 879146e9f4c 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits discards 001f7e0cd55 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits discards b63c6443c43 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits discards 266a31d6372 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits discards 18146cd7c4c 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits discards 51b9ca05123 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits discards 1ca447e378f 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits new 603f66a80f3 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits new 6c28131c130 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits new c28644547b2 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits new c57f2364291 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits new 3707f6be6fc 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits new f89f8c2f228 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits new dfc92727ba2 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits new a1516af871e 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits new ba6360f42cd 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits new e03bfe5f2d9 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits new 5c663f7d5ea 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits new 068b08e6612 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits new 356405554f4 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits new 4f070ba1d4d 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits new 44f6c6b28b7 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits new cd8dca05836 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits new 615e1b54a8f 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits new 6c89d6b36b3 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits new 3846a50f9d5 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint- [...] new 3582401141f 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint- [...] new 2da3b6c4806 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint- [...] new f7d28ad5945 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint- [...] new 4857dd4825f 310: onsuccess: #2259: 1: Success after binutils: 2 commits new 08c39fe6b52 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint- [...] new db27f576af2 312: onsuccess: #2265: 1: Success after binutils: 2 commits new 334e673814e 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits new d295f391819 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits new a5d7f5e1d1c 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits new 50a48c0d90f 316: onsuccess: #2270: 1: Success after gcc: 2 commits new 77c1d10d14c 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new 1b445743aa2 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits new c43b6378710 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits new 1623f6c4e37 320: onsuccess: #2274: 1: Success after gcc: 5 commits new 44bcfe7d608 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new f3b454def78 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new d80b95984f5 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new d1efbe14f8b 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new 06bb6a6f33a 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new 115549e3480 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new ee3301e08a1 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new 0d772e9c289 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint- [...] new a1cfbb30474 329: onsuccess: #2285: 1: Success after gcc: 8 commits new 66940b9ec15 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new 2604e97312c 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint- [...] new 6bf5887158f 332: onsuccess: #2288: 1: Success after gcc: 2 commits new 71da4c5d71f 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-4 [...] new 789bbf1ef9b 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new cd30450565d 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new 572bdfa9e2e 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new 30932bd0994 337: onsuccess: #2293: 1: Success after gcc: 21 commits new 836a2dab41b 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new b1526ffdc45 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new 3a90cfc2664 340: onsuccess: #2296: 1: Success after gcc: 3 commits new 68e8c992f22 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new 37319be5d64 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new 81296330953 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new 463c8c61aec 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new 83238414d04 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new fcb42ab0eb3 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new b8359c709b2 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new 5e042be0904 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new fd1c276acf9 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new 1e525ed5499 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new 20df94e3fcb 351: onsuccess: #2307: 1: Success after binutils: 2 commits new 58f5184a321 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new d57976d8804 353: onsuccess: #2309: 1: Success after gcc: 7 commits new 4ae446a5f51 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new 71c6c3ed922 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new 8d4a0cf4eb0 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new 948abab7ea5 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new 70642136014 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new 810a75ee816 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint- [...] new bbb46b178fe 360: onsuccess: #2317: 1: Success after binutils: 4 commits new af035d487a9 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new b4f11138452 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new 9bb9324d17b 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new 9ad20cc9e30 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new 190f9d84631 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new dd3cdba4939 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new bb209911c63 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new 4cb215aacc4 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new e3e601ee066 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new fc9d7b557ef 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits new 45c9de042bb 371: onsuccess: #2333: 1: Success after binutils: 5 commits new 6e911c24bfb 372: onsuccess: #2334: 1: Success after gcc: 5 commits new 3e7869ca5ec 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits new 8b5b65f23c6 374: onsuccess: #2336: 1: Success after gcc: 4 commits new 5b2d1f867d3 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new 0a6baf3d321 376: onsuccess: #2338: 1: Success after gcc: 2 commits new c23c810ceaf 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits new 8f7600eec88 378: onsuccess: #2340: 1: Success after binutils: 2 commits new 75167d58a95 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-4 [...] new 6275d8cc504 380: onsuccess: #2342: 1: Success after gcc: 3 commits new 8cc296564ee 381: onsuccess: #2343: 1: Success after gcc: 2 commits new 3d706c04130 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits new 003a4892cdb 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits new 04510e630d4 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits new e7c76e818db 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits new a4a53ab7b08 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits new 38103d00c94 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits new 60fb176500a 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits new c353f4a1ae0 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (47ac239e312) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] 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 1720 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 39244 -> 39748 bytes 04-build_abe-gcc/console.log.xz | Bin 214380 -> 217092 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3836 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2652 -> 3532 bytes 07-check_regression/console.log.xz | Bin 5456 -> 5460 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 6 - 07-check_regression/mail-body.txt | 22 +- 07-check_regression/results.compare | 9 +- 07-check_regression/results.compare2 | 97 +- 07-check_regression/results.regressions | 26 - 08-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 26 - sumfiles/g++.log.xz | Bin 3616244 -> 3605480 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 3143832 -> 3139956 bytes sumfiles/gcc.sum | 4600 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1049200 -> 1052764 bytes sumfiles/gfortran.sum | 70 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2184 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 219224 -> 219248 bytes sumfiles/libgomp.sum | 12 +- sumfiles/libitm.log.xz | Bin 2548 -> 2548 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 454784 -> 451784 bytes sumfiles/libstdc++.sum | 4 +- 36 files changed, 2502 insertions(+), 2507 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-defconfig updated (ae90437473f -> f32ee848542)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-defconfig in repository toolchain/ci/base-artifacts. from ae90437473f 28: onsuccess: #482: boot: Success after binutils/llvm/qemu [...] new f32ee848542 29: onsuccess: #483: boot: Success after binutils/llvm/linu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1912 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31676 -> 32396 bytes 04-build_kernel_llvm/console.log.xz | Bin 66800 -> 67080 bytes 05-build_abe-qemu/console.log.xz | Bin 30616 -> 31320 bytes 06-build_linux/console.log.xz | Bin 3424 -> 3480 bytes 07-boot_linux/console.log.xz | Bin 6256 -> 6288 bytes 08-check_regression/console.log.xz | Bin 4096 -> 4640 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (4a8808bce18 -> 24939d7399b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 4a8808bce18 125: onsuccess: #614: 1: Success after linux: 12 commits discards d52cc55bb73 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 968554d495c 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards d004a5cd6a9 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 4c6ae5d6d41 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards a4d940b3ff7 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 4cb73e22e2a 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards d76d72061e2 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 5e16a76f4c9 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 7eb9425b699 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards fdb733e315d 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 36f974c28dc 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 7531a6d41eb 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 7949d031843 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards a60d3ae75ba 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards 011a9a25642 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 309cd895354 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 53d55a676fa 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards c7d14db8b36 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 8a92b63e82e 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards f74d6720f37 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards dc77d5f99d5 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 16d9d51bccc 103: onsuccess: #589: 1: Success after binutils: 3 commits discards e0208476aba 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 41cee873394 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] discards e2ca08777e5 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards 374d908b37b 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] discards 65966eebde7 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards f6efb959981 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] discards 4506a33dd24 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] discards a65a5370dad 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards 2fc55782427 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards ff01992a8b6 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards aa04de37396 92: onsuccess: #575: 1: Success after linux: 34 commits discards 12dbaef96e4 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 401b8e059bf 90: onsuccess: #572: 1: Success after binutils: 15 commits discards ccbf82e216f 89: onsuccess: #570: 1: Success after linux: 11 commits discards 5807430967f 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 17f6726f6c8 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 961e1eb9792 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards b846f980606 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 2bb9dfd03e6 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards b0ef4834e55 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] discards 93808f76ff3 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] discards afd76a9f5ae 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 3f49d1504a5 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] discards dd8af79d6dc 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards ef2a6a1def3 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] discards 8ead05ae371 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards c785d09fc7a 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] discards bcd00a4eb74 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] discards 932bd3f93b2 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards d527cf64b1e 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 88d759b0395 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards de4669f6331 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards 5bc4f9892c7 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 99925f26d59 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] discards 85781f7c154 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards 8dde38699a4 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards cf5f2a46576 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards c83554ab411 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards db2a1f04db3 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 9228e455879 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards beadd2571bd 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 1e27158d661 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 4b12ca63369 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] discards f2d56a991ab 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards a2561b4905b 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 6cc72f5d43e 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] discards 9d80e881716 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 3ac90ac0383 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 64799058999 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] discards 666b6bb0ef0 53: onsuccess: #531: 1: Success after binutils: 12 commits discards cc20cfdde05 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 6c0614e6ecc 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 271b1a344c6 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] discards 4ad13bf6b82 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] discards 0d51dcce84e 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] discards 7c7e78c4681 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] discards aa341085d48 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards e48564c53a5 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] discards 1a971606010 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards 96d61ae540c 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards d5e94ad30a2 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] discards b14235f67a5 41: onsuccess: #514: 1: Success after linux: 64 commits discards b7a950ceace 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] discards 633c31228c3 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 48fda4e452a 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 331244f9059 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards 1df6b4eb0ea 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 4a58391b892 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 0efa43ea142 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards b80042f50db 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] discards b0db3bba3d5 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards 0207f3295da 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards 437f476ccf6 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 64463e7ff29 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards 55e581a493a 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] discards d72115389ae 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards 46c4070cf3d 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] discards be5e20a70ba 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new f89c8a0e628 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gd [...] new e689639b43b 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] new 4c38f04728d 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new f8cdcf50688 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] new 4a255702ff0 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 81091679873 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new c3e222cfe43 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new 96e662a15b6 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 259fe58e164 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] new cde3d054a6a 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new b70e9cd17e4 35: onsuccess: #503: 1: Success after binutils: 11 commits new 9add084f946 36: onsuccess: #505: 1: Success after glibc: 3 commits new e721a661479 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] new 1be76f92b5e 38: onsuccess: #508: 1: Success after binutils: 3 commits new c3a95370d6e 39: onsuccess: #511: 1: Success after binutils: 8 commits new f0152e5e7ed 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] new 95bfd86a77e 41: onsuccess: #514: 1: Success after linux: 64 commits new 0d7d10aa60d 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] new e28810a6b20 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new 54de9aded57 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new 221bd1ca9d9 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] new 1345198dd40 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new d7d03a4743f 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] new 6c09cebdc64 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] new 1524a01b3cc 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] new f4e41a77dde 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] new 87a351b4724 51: onsuccess: #525: 1: Success after binutils: 8 commits new 047d394264f 52: onsuccess: #528: 1: Success after binutils: 8 commits new 1f2e857b3da 53: onsuccess: #531: 1: Success after binutils: 12 commits new 9d577255e2c 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] new c647fbaf669 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 820dd996ba4 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 9d271c8eb3b 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] new 2147becc140 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new e556f53d73b 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 9be9296b692 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] new b2df72d257f 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 78e8c8d09cc 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new d866b14e41f 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 32a957dfae0 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 0a7b8b026a2 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new 431c70b3e1c 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new c0c1e158a99 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new b0950c6e782 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new 032f92b951b 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] new fb45b239dc1 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 6003971da44 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new 9e5d7f9070c 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 4fd107a46d8 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new dc9596acf14 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new b1f1a68d13c 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] new d94b4a20240 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] new b501ae6b249 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new 2b9a7fc100c 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] new 0e1840b3c62 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 74cb63641fd 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] new 7f1bab49804 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new d099f32a3f7 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] new f6094551b2a 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] new f385af29c52 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new ddc92c2bc26 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new bb8f387ac41 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new a3c4ac0108a 87: onsuccess: #567: 1: Success after binutils: 8 commits new 51e21bf4c68 88: onsuccess: #569: 1: Success after glibc: 10 commits new 466ed49950e 89: onsuccess: #570: 1: Success after linux: 11 commits new c5daad35675 90: onsuccess: #572: 1: Success after binutils: 15 commits new b3df343b232 91: onsuccess: #574: 1: Success after glibc: 3 commits new 8cc0ad2aceb 92: onsuccess: #575: 1: Success after linux: 34 commits new 6dac530f13e 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 241c426474b 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 3e2fca1d912 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new cbc7a5ba071 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] new 7413673e59a 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] new f40568ba851 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 0b5cff3b834 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] new d09e5ea4114 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 353dcbdfa30 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] new e228da7664e 102: onsuccess: #586: 1: Success after binutils: 5 commits new 6b342b8e43a 103: onsuccess: #589: 1: Success after binutils: 3 commits new f9c0e9c8605 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 74543d7030d 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new daf8b5028c6 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 361933ca91c 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 88e4ef157f6 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new f4c56dc46ed 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 3c827c3719a 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new a78ca4b2bfd 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 40302044d3b 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 4a0768078b4 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new c2aa79d3c44 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new dd228c55477 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new dbeaf6ee6e8 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 8fcaa7d67c3 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new c78829e023e 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 4013e6d9c47 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 3774bc07ad0 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 128e180e757 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 1f2ce773c2b 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 0d8fd60c6af 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new f783b53cacf 124: onsuccess: #612: 1: Success after binutils: 18 commits new dcb4611e441 125: onsuccess: #614: 1: Success after linux: 12 commits new 24939d7399b 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (4a8808bce18) \ 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 1668 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 52308 -> 53520 bytes 04-build_abe-gcc/console.log.xz | Bin 235332 -> 237224 bytes 06-build_abe-linux/console.log.xz | Bin 8440 -> 8772 bytes 07-build_abe-glibc/console.log.xz | Bin 237844 -> 236768 bytes 08-build_abe-gdb/console.log.xz | Bin 51976 -> 51768 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3956 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2148 -> 2196 bytes 11-check_regression/console.log.xz | Bin 16428 -> 13244 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 56 +- 11-check_regression/mail-body.txt | 215 +- 11-check_regression/results.compare | 115 +- 11-check_regression/results.compare2 | 4248 +++++++------------------------ 11-check_regression/results.regressions | 112 +- 12-update_baseline/console.log | 48 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 217 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 112 +- sumfiles/gdb.log.xz | Bin 1771916 -> 1747888 bytes sumfiles/gdb.sum | 2663 ++----------------- 30 files changed, 1695 insertions(+), 6145 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-release-arm_eabi-coremark-O3 updated (1fab01612a2 -> 00eb47f7de7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-release-arm_eabi-coremark-O3 in repository toolchain/ci/base-artifacts. from 1fab01612a2 14: onsuccess: #154: 1: [TCWG CI] No change after binutils/ [...] new 00eb47f7de7 15: onsuccess: #155: 1: [TCWG CI] No change after binutils/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 30248 -> 30368 bytes 04-build_abe-stage1/console.log.xz | Bin 85464 -> 86152 bytes 06-build_abe-newlib/console.log.xz | Bin 16664 -> 16780 bytes 07-build_abe-stage2/console.log.xz | Bin 159640 -> 159296 bytes 08-benchmark/benchmark-build.log | 104 ++++++++++----------- 08-benchmark/benchmark.log | 102 ++++++++++---------- 08-benchmark/console.log.xz | Bin 3804 -> 3832 bytes 09-check_regression/console.log.xz | Bin 4780 -> 4924 bytes 09-check_regression/results-vs-first.log | 2 +- 09-check_regression/results-vs-prev.log | 4 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +-- .../squad-vs-first/coremark/results-metadata.json | 12 +-- dashboard/squad-vs-first/dashboard-push-squad.sh | 10 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 33 ++++--- mail/mail-body.txt | 33 ++++--- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++--- results_id | 2 +- 24 files changed, 180 insertions(+), 174 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (601859b8fe1 -> 02242900b21)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 601859b8fe1 118: onsuccess: #863: 1: Success after linux: 12 commits discards 73440ebe65c 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 5b10528008a 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 929df00bddd 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards b62acf004b9 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards fe0eb75b840 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 1c02474b882 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 2d076fe955b 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards ddc0fdb09fc 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 0e8b39713b5 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 0a16ed0b39a 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 81baec4ddaa 107: onsuccess: #849: 1: Success after binutils: 5 commits discards a59bf233c0d 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 96515d78867 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards a11df02b07f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 4faa3732557 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 5b781d39610 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 4b59229d0b6 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 823db54164e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards aebdb5653e9 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 7b1998b8ef1 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 8c5cf587ae1 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 848d8f79d16 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 1f4fc65f880 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 7ca4540a5bf 94: onsuccess: #832: 1: Success after binutils: 5 commits discards b95bbd73241 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 4b6fbd169c1 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards ab8af324e19 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 472a5aa8cae 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards e99eafef1fc 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 8482fd7e200 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 04ca838db54 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 8e0fa1a7489 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 162214917b8 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 4466911cd13 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 48cf7eecd30 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards b2e829280d0 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards f023dc51bb8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards a9713876b8e 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 91105fb6f37 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 00d2a3c29d7 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards e758b3f2407 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards d6eaf91671e 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 6ebb744f0ec 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 7e632a3c52d 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards bade4d706c6 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 54c75968771 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards b3b869b1b2c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards fd9b270f1d5 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 619ed660fd4 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards ba6d0449dea 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 19299c9c7b3 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 0bff4a80ecb 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 97958fc73db 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 6286c575bb1 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards d91c2edbb37 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 2c4d08189da 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards fd4fac26864 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards dfaf14f2aca 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 2df6ec4a1cf 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards c2860607043 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 798e1afcd0f 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 75bc94cb0ac 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 258e5355482 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards a7a0940d59d 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards f524d7c2764 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 93ce1aff0df 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards cafc737a7e3 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards d0db2a79ae0 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 6a76d502ea6 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 144b6a067fb 48: onsuccess: #782: 1: Success after binutils: 8 commits discards e3498d1b557 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards b3a2f443ea3 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 1b1ef2ad7f6 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards c4c363d007b 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards b88e3276290 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 907b0e39a3e 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 19b2a764b71 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards b145a445108 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards c366c133213 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards d9d9e2b41f9 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 56c6b21c3eb 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 18ca0f37aac 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 683f844cb96 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards f2f0a22cc94 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 83571d06832 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 63a5c26b4ae 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards b2bdf09918d 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards f9f490c9a3a 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 9025e11e1a0 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards d78532bbce7 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 674a6a6a023 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards a7dc747a127 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards b4d4f6c0f2f 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards f9c7e006ea0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards e7791425a92 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 33d906cc98e 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards b1b440ba800 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards c489667a5ac 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 92ca07ea68c 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards ed006a80da5 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c5a28d4ea47 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new f6f8f305708 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 4ef9ec60a4d 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 3ed461d62b6 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 446f13bf7f0 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 7259133c5f5 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 8c1f1fb663e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 7e381ba923d 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 8d51a056b4e 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new d2751d7d192 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new c006d6f1b25 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 16add68e636 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 8603051a518 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 1019783728c 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new d982b64a0bd 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new ec25f0a3873 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 55191be855f 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 31b1fe20af8 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 3037ee1a1fd 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 6c8b88cb630 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 2f5c082901f 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new b0b31ffe630 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 2ba57f88c48 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new ce4b843b9cb 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 3f5880575a6 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 2cee81ebfc0 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new e864fddf3c3 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 514278d8003 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new cdca9bb9a4b 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new d9c2a4b4cd4 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 5677b8ce820 48: onsuccess: #782: 1: Success after binutils: 8 commits new a7a7bfcd3bd 49: onsuccess: #785: 1: Success after binutils: 12 commits new 1180de743ef 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new 8cc2d21fb04 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 3c93246650b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 0721fdf2806 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 7d47ede03f4 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new c4f714b4d96 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 06ed784bf21 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 3bbae48b8e1 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new a3b9bee1bc4 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 216853a2c6a 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 377b3b2ad01 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 9a01ac7ffba 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 98c54dfa3e1 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 8c4f4749fa8 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new a027cf1c05a 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new f8e2f369ad4 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 91b2a06a7db 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 2f9899382bf 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new ad88ad10e50 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 8f71ecf8aa6 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 8b9a9061098 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 741a5638b8f 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new d2d4ac33727 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 02bee66e19b 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new ca5bf6bb0ee 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 7a9ccb581e9 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 0a58c04d374 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 19fdd08a8bc 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 3df4adc6f57 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 766eea3c69c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 98052c87702 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 16bf080dd17 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 202855a893b 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 2524e2d6904 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 6f5fe57f3dd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 68993034a45 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 6a2d47efe7f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 5b4893af8ea 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new c9cbf6242a9 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 92285ee85d1 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new bcf50657a29 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 7a6337877ac 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new d496184ab94 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 571962a7515 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new d48cb20d829 94: onsuccess: #832: 1: Success after binutils: 5 commits new 167653fcaf2 95: onsuccess: #835: 1: Success after binutils: 3 commits new 378b49a7017 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 89e99c15a7e 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 6e3d0120d41 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 7a10b0f2c73 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 2cee15b6296 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 856cfcd204b 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 3400c94806c 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 4e8bb120d18 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 9199d1307a2 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 089082c18c7 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 4ae737b71ec 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 9778ad0a4bb 107: onsuccess: #849: 1: Success after binutils: 5 commits new 6a8ae9da110 108: onsuccess: #850: 1: Success after gcc: 2 commits new 461eb5fc5fb 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 6020e9134f2 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 38504873f98 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new da21edc01a0 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 0482a060710 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new b60c74b7af5 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new cf3920505e4 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 9d2f4532b02 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 918f85e2a69 117: onsuccess: #861: 1: Success after binutils: 18 commits new ba8b652fee6 118: onsuccess: #863: 1: Success after linux: 12 commits new 02242900b21 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (601859b8fe1) \ 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 1788 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 39332 -> 39576 bytes 04-build_abe-gcc/console.log.xz | Bin 214516 -> 215288 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8428 -> 8728 bytes 07-build_abe-glibc/console.log.xz | Bin 246076 -> 243404 bytes 08-build_abe-gdb/console.log.xz | Bin 38932 -> 39148 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3844 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2772 -> 3576 bytes 11-check_regression/console.log.xz | Bin 4908 -> 7832 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 232 +- 12-update_baseline/console.log | 46 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 3739028 -> 3747500 bytes sumfiles/g++.sum | 224 +- sumfiles/gcc.log.xz | Bin 3318432 -> 3330456 bytes sumfiles/gcc.sum | 5089 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1080964 -> 1081840 bytes sumfiles/gfortran.sum | 114 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231200 -> 232148 bytes sumfiles/libgomp.sum | 26 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 453080 -> 456840 bytes sumfiles/libstdc++.sum | 16 +- 38 files changed, 3078 insertions(+), 2749 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[linux] branch master updated (bce9332220bd -> 8ed710da2873)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository linux. from bce9332220bd proc: proc_skip_spaces() shouldn't think it is working on [...] new ad7f402ae4f4 xen/netback: Ensure protocol headers don't fall in the non [...] new 74e7e1efdad4 xen/netback: don't call kfree_skb() with interrupts disabled new b71101d6ae7b Merge tag 'for-linus-xsa-6.1-rc9-tag' of git://git.kernel. [...] new 0dd4cdccdab3 KVM: s390: vsie: Fix the initialization of the epoch exten [...] new 7e3bba93f42e Merge tag 'kvm-s390-master-6.1-2' of https://git.kernel.or [...] new e542baf30b48 KVM: x86: fix uninitialized variable use on KVM_REQ_TRIPLE_FAULT new b8b43a4c2e9f KVM: Move halt-polling documentation into common directory new 34e30ebbe48c KVM: Document the interaction between KVM_CAP_HALT_POLL an [...] new 5b3e0cd872b0 Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt [...] new b7d9aae40484 Revert "arm64: dma: Drop cache invalidation from arch_dma_ [...] new 8ed710da2873 Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/li [...] The 11 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: Documentation/virt/kvm/api.rst | 15 +- Documentation/virt/kvm/{x86 => }/halt-polling.rst | 13 ++ Documentation/virt/kvm/index.rst | 1 + Documentation/virt/kvm/x86/index.rst | 1 - arch/arm64/mm/dma-mapping.c | 17 +- arch/s390/kvm/vsie.c | 4 +- arch/x86/kvm/x86.c | 2 +- drivers/net/xen-netback/common.h | 2 +- drivers/net/xen-netback/interface.c | 6 +- drivers/net/xen-netback/netback.c | 223 ++++++++++++---------- drivers/net/xen-netback/rx.c | 8 +- 11 files changed, 174 insertions(+), 118 deletions(-) rename Documentation/virt/kvm/{x86 => }/halt-polling.rst (92%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_tx1/gnu-release-aarch64-spec2k6-O3_LTO updated (7d401633de4 -> 601ca08cbf5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_tx1/gnu-release-aarch64-spec2k6-O3_LTO in repository toolchain/ci/base-artifacts. from 7d401633de4 20: onsuccess: #291: 1: [TCWG CI] No change after glibc: 2 commits new 601ca08cbf5 21: onsuccess: #292: 1: [TCWG CI] No change after v6.0.10-4 [...] 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 1828 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30752 -> 30300 bytes 04-build_abe-stage1/console.log.xz | Bin 69300 -> 68312 bytes 06-build_abe-linux/console.log.xz | Bin 8820 -> 8784 bytes 07-build_abe-glibc/console.log.xz | Bin 236252 -> 236696 bytes 08-build_abe-stage2/console.log.xz | Bin 172780 -> 173012 bytes 09-benchmark/benchmark-build.log | 110 +- 09-benchmark/benchmark.log | 108 +- 09-benchmark/console.log.xz | Bin 3852 -> 3900 bytes 10-check_regression/console.log.xz | Bin 6200 -> 6180 bytes .../csv-results-vs-first-1/perf.csv | 168 +- .../csv-results-vs-first-1/results.csv | 10055 +- .../csv-results-vs-first-1/size.csv | 338094 +++++++------ .../csv-results-vs-first-1/vect.csv | 20 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 173 +- .../csv-results-vs-prev-0/results.csv | 18635 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 474292 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/vect.csv | 36 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 168 +- .../csv-results-vs-prev-1/results.csv | 10055 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 338094 +++++++------ 10-check_regression/csv-results-vs-prev-1/vect.csv | 20 +- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 166 +- 10-check_regression/results-vs-first-internal.csv | 82 +- 10-check_regression/results-vs-first.csv | 82 +- 10-check_regression/results-vs-first.log | 1080 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-full.csv | 182 +- 10-check_regression/results-vs-prev-internal.csv | 82 +- 10-check_regression/results-vs-prev.csv | 82 +- 10-check_regression/results-vs-prev.log | 1384 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 10 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../434.zeusmp/results-metadata.json | 10 +- .../435.gromacs/results-metadata.json | 10 +- .../436.cactusADM/results-metadata.json | 10 +- .../437.leslie3d/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../447.dealII/results-metadata.json | 10 +- .../450.soplex/results-metadata.json | 10 +- .../453.povray/results-metadata.json | 10 +- .../454.calculix/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 10 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 10 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 10 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/linux_rev | 2 +- mail/jira-body.txt | 8 +- mail/mail-body.txt | 8 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results_id | 2 +- 84 files changed, 592189 insertions(+), 601605 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_apm/gnu-master-arm-spec2k6-Os_LTO updated (57f6154632b -> 4688dcb6435)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_apm/gnu-master-arm-spec2k6-Os_LTO in repository toolchain/ci/base-artifacts. from 57f6154632b 27: onsuccess: #188: 1: [TCWG CI] No change after glibc: 48 [...] new 4688dcb6435 28: onsuccess: #189: 1: [TCWG CI] No change after linux: 94 [...] 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 1820 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32052 -> 31976 bytes 04-build_abe-stage1/console.log.xz | Bin 92700 -> 92524 bytes 06-build_abe-linux/console.log.xz | Bin 8808 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 238244 -> 238416 bytes 08-build_abe-stage2/console.log.xz | Bin 213684 -> 216404 bytes 09-benchmark/benchmark-build.log | 90 +- 09-benchmark/benchmark.log | 88 +- 09-benchmark/console.log.xz | Bin 3768 -> 3820 bytes 10-check_regression/console.log.xz | Bin 6136 -> 6072 bytes .../csv-results-vs-first-1/perf.csv | 249 ++-- .../csv-results-vs-first-1/results.csv | 266 ++--- 10-check_regression/csv-results-vs-prev-0/perf.csv | 235 ++-- .../csv-results-vs-prev-0/results.csv | 769 +++++++------ 10-check_regression/csv-results-vs-prev-0/size.csv | 580 +++++----- 10-check_regression/csv-results-vs-prev-1/perf.csv | 249 ++-- .../csv-results-vs-prev-1/results.csv | 266 ++--- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 259 ++--- 10-check_regression/results-vs-first-internal.csv | 80 +- 10-check_regression/results-vs-first.csv | 80 +- 10-check_regression/results-vs-first.log | 1084 +++++++++--------- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-full.csv | 279 ++--- 10-check_regression/results-vs-prev-internal.csv | 80 +- 10-check_regression/results-vs-prev.csv | 80 +- 10-check_regression/results-vs-prev.log | 1188 ++++++++++---------- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../410.bwaves/results-metadata.json | 10 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../434.zeusmp/results-metadata.json | 10 +- .../435.gromacs/results-metadata.json | 10 +- .../436.cactusADM/results-metadata.json | 10 +- .../437.leslie3d/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 10 +- .../450.soplex/results-metadata.json | 10 +- .../453.povray/results-metadata.json | 10 +- .../454.calculix/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../471.omnetpp/results-metadata.json | 10 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metadata.json | 10 +- .../482.sphinx3/results-metadata.json | 10 +- .../483.xalancbmk/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/linux_rev | 2 +- mail/jira-body.txt | 14 +- mail/mail-body.txt | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results_id | 2 +- 70 files changed, 3288 insertions(+), 3252 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch devel/modula-2 updated (5405813b8aa -> 98b201a33be)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/modula-2 in repository gcc. from 5405813b8aa gm2-lang.cc further tidyup of code. new 98b201a33be Bugfix gm2_type_for_size. Patchset suggestion missed. 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: gcc/m2/gm2-lang.cc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allnoconfig in repository toolchain/ci/base-artifacts. from af5a17c3499 26: onsuccess: #417: all: Success after binutils/llvm/linux [...] new b2eb2969831 27: onsuccess: #418: all: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31376 -> 31532 bytes 04-build_kernel_llvm/console.log.xz | Bin 65268 -> 65532 bytes 05-build_abe-qemu/console.log.xz | Bin 30904 -> 30412 bytes 06-build_linux/console.log.xz | Bin 3064 -> 3128 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4384 -> 4464 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 26 insertions(+), 26 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022