Tcwg-commits November 2022

tcwg-commits@lists.linaro.org

5 participants
4683 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (cfa30f0244 -> 8da8f7c2e7)

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 cfa30f0244 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards a5413e3dd2 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards f4c5c37e36 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards ecf94ab294 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint-2 [...] discards abdd6373cb 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards 992d40592d 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards 6f8dfecfd1 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards 16e8c912ff 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards e01a7fcee2 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards 2ecf1e85d9 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards 505f2a36c3 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards 20cfbda6ac 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards 3263789384 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards daae73ad09 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards d9cf433081 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits discards 5003b3f107 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits discards 64aa966722 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits discards 004150e1bf 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards 0568c557af 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards e6ba99ed34 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards a7b5bbed2d 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards ecdc52e40b 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards 18c0e6bba5 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards 6a8d993719 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards 27bbe8e25b 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards 9be67000ce 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards 02f0426e95 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards 40d5d200b3 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards c8e6c945f4 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards ad0ea4b0cb 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-41 [...] discards c85471ce61 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards 4d7a55022c 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint-2 [...] discards 8d0d42aa8e 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards a0f3dc18b1 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards a7697818e6 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint-2 [...] discards 6310c25bb2 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards 26330cdbc6 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards 8ad0f98ae9 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards 47c56bd468 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards 57891058bb 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards 7996744125 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards bb7a3c3c15 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits discards 65f591f89a 320: onsuccess: #2274: 1: Success after gcc: 5 commits discards 5abd8ea51c 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits discards 418fd5414e 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits discards b9c65eb8fc 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits discards 9ddd16c35f 316: onsuccess: #2270: 1: Success after gcc: 2 commits discards 26efc7474b 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits discards 98bf88e82e 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits discards d0e9af506d 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits discards 1000018c9e 312: onsuccess: #2265: 1: Success after binutils: 2 commits discards 7d08ded030 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint-2 [...] discards 089ab9ad2a 310: onsuccess: #2259: 1: Success after binutils: 2 commits discards 49eebc3225 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint-2 [...] discards 3243608be2 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint-2 [...] discards 1f5a57e348 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint-2 [...] discards ef40be565f 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint-2 [...] discards 2fa4172c46 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits discards 78efd89540 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits discards d87b0f37b3 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits discards 79edafa365 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits discards 5f3af3c86b 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits discards 2221aae5c3 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits discards b02fc1b5e3 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits discards 10384251ac 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits discards c07917e668 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits discards 72d7ba9ff7 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits discards b1319b676e 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits discards 8ade8f346a 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits discards 7c9a20512d 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits discards bf89061905 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits discards ed91d09acf 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits discards 8ae2414ad6 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits discards 32462fe709 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits discards 72a346d96c 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits discards f1f5092bef 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits discards 41a66d99d2 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits discards 26a4be95ee 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits discards e4a9cc52e6 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits discards 7c51ffea95 283: onsuccess: #2222: 1: Success after gcc: 4 commits discards 31f893e50c 282: onsuccess: #2221: 1: Success after gcc: 2 commits discards 6c0ab427f8 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits discards 746958998f 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits discards 1cb1a47ff5 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-36 [...] discards 170e8792d6 278: onsuccess: #2217: 1: Success after binutils: 7 commits discards 572116e56e 277: onsuccess: #2216: 1: Success after binutils: 2 commits discards 149e95fc74 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits discards 2f3f5f4d89 275: onsuccess: #2214: 1: Success after binutils/gcc: 14 commits discards ffa7ed62fa 274: onsuccess: #2213: 1: Success after binutils/gcc: 12 commits discards ee472019f2 273: onsuccess: #2212: 1: Success after binutils/gcc: 13 commits discards 44e856193f 272: onsuccess: #2211: 1: Success after binutils/gcc: 19 commits discards fadbe4e8f5 271: onsuccess: #2210: 1: Success after binutils/gcc: 8 commits discards 1f8074b552 270: onsuccess: #2209: 1: Success after gcc: 2 commits discards 496c87a5f6 269: onsuccess: #2208: 1: Success after binutils/gcc: 8 commits discards ee7beb6e93 268: onsuccess: #2207: 1: Success after binutils/gcc: 12 commits discards 93ff145b17 267: onsuccess: #2206: 1: Success after binutils/gcc: 5 commits discards c92afbbbaf 266: onsuccess: #2205: 1: Success after binutils/gcc: 8 commits discards a532ae4c24 265: onsuccess: #2204: 1: Success after binutils/gcc: 5 commits discards 36807211ed 264: onsuccess: #2203: 1: Success after gcc: 9 commits discards 99fba6f22b 263: onsuccess: #2202: 1: Success after binutils/gcc: 5 commits discards 4ab91c04f1 262: onsuccess: #2201: 1: Success after gcc: 6 commits new 48ab6221a3 262: onsuccess: #2201: 1: Success after gcc: 6 commits new 4a8a64e36f 263: onsuccess: #2202: 1: Success after binutils/gcc: 5 commits new 2f94f7367b 264: onsuccess: #2203: 1: Success after gcc: 9 commits new 8d891982e1 265: onsuccess: #2204: 1: Success after binutils/gcc: 5 commits new 7c68c203d5 266: onsuccess: #2205: 1: Success after binutils/gcc: 8 commits new b43db0906a 267: onsuccess: #2206: 1: Success after binutils/gcc: 5 commits new aa2ce84384 268: onsuccess: #2207: 1: Success after binutils/gcc: 12 commits new c15c0e1e6b 269: onsuccess: #2208: 1: Success after binutils/gcc: 8 commits new 0857336e11 270: onsuccess: #2209: 1: Success after gcc: 2 commits new 131f353f47 271: onsuccess: #2210: 1: Success after binutils/gcc: 8 commits new d624c2ac6e 272: onsuccess: #2211: 1: Success after binutils/gcc: 19 commits new a53c27544a 273: onsuccess: #2212: 1: Success after binutils/gcc: 13 commits new aa20676a7a 274: onsuccess: #2213: 1: Success after binutils/gcc: 12 commits new 8db6b737fb 275: onsuccess: #2214: 1: Success after binutils/gcc: 14 commits new 7ca756c0d3 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits new a606311d34 277: onsuccess: #2216: 1: Success after binutils: 2 commits new 36a4025836 278: onsuccess: #2217: 1: Success after binutils: 7 commits new 786b418b79 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-36 [...] new d5625f667e 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits new 673af050d9 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits new 67c322ea39 282: onsuccess: #2221: 1: Success after gcc: 2 commits new 17bdbcdc6d 283: onsuccess: #2222: 1: Success after gcc: 4 commits new a061e47965 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits new b74aa01de6 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits new 40d6ba2b2b 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits new 30acfb6a44 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits new c7d6a5d2cb 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits new 8b82b351e9 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits new d9027548c1 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits new f2746ed61d 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits new 16b6cc708a 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits new 3f0b1732da 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits new ad90533cf4 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits new efd0335d3f 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits new f4f953a596 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits new 41b7eaf1ea 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits new e3c8b3fcd1 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits new f712c27898 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits new 5ae2c9a43b 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits new ec92c9ccde 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits new c8c4e71767 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits new 24b4852ec4 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits new d89fbd42dd 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits new 3b4f9d2da2 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits new 130f8cbf96 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint-2 [...] new ee2405320f 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint-2 [...] new 9a9ae5e509 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint-2 [...] new d95d39e061 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint-2 [...] new 217311c4ea 310: onsuccess: #2259: 1: Success after binutils: 2 commits new 89222443d8 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint-2 [...] new 62d7e4cfe7 312: onsuccess: #2265: 1: Success after binutils: 2 commits new 1d723aaa1b 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits new 19b2cf6b67 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits new 82dfe357f5 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits new 359bb6bc7c 316: onsuccess: #2270: 1: Success after gcc: 2 commits new 2695c1c2a2 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new 9d211773bf 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits new 3e5d271ffb 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits new d5ee3832af 320: onsuccess: #2274: 1: Success after gcc: 5 commits new 45333375a8 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new 7c5e00f380 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new 388b9099e1 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new 3b1f2b25a7 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new 039fcf81bc 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new accbc6a2f6 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new 2cc5eb2b25 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new 737009df77 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint-2 [...] new 5730375839 329: onsuccess: #2285: 1: Success after gcc: 8 commits new 1fd066e93e 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new cc39c6ace8 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint-2 [...] new e716f17a86 332: onsuccess: #2288: 1: Success after gcc: 2 commits new 51982db5d4 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-41 [...] new 1771044383 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new 8053bc6ddf 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new eef83ac51e 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new 0ce9373306 337: onsuccess: #2293: 1: Success after gcc: 21 commits new 86d440fd82 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new b82bb432f1 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new f5c74b9b6b 340: onsuccess: #2296: 1: Success after gcc: 3 commits new 7dc8a1fa0b 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new 1bd6e324eb 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new 97bb3118d5 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new db932e585f 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new dbcfb1dbb4 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new 776e569d57 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits new 50ddbf1056 347: onsuccess: #2303: 1: Success after binutils/gcc: 3 commits new 52ef033fda 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new 645d49c3c5 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new c2d7661088 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new ced51b4f8a 351: onsuccess: #2307: 1: Success after binutils: 2 commits new 6c17d8ca87 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new aa856e1a19 353: onsuccess: #2309: 1: Success after gcc: 7 commits new a60565b332 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new 9fadf62466 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new 2fda3d2f90 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new 5988bc462f 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new d516ea87c4 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new 8b334bc160 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint-2 [...] new 408bc151ba 360: onsuccess: #2317: 1: Success after binutils: 4 commits new 5e0293f841 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new ae736e553c 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new 8da8f7c2e7 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 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 (cfa30f0244) \ 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 1684 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 40260 -> 40744 bytes 04-build_abe-gcc/console.log.xz | Bin 215008 -> 215480 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3844 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2644 -> 2424 bytes 07-check_regression/console.log.xz | Bin 6696 -> 5480 bytes 07-check_regression/extra-bisect-params | 2 +- 07-check_regression/fails.sum | 9 +- 07-check_regression/mail-body.txt | 49 +- 07-check_regression/results.compare | 25 +- 07-check_regression/results.compare2 | 323 +- 07-check_regression/results.regressions | 25 +- 08-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 51 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 25 +- sumfiles/g++.log.xz | Bin 3603176 -> 3603972 bytes sumfiles/g++.sum | 136 +- sumfiles/gcc.log.xz | Bin 3152496 -> 3126564 bytes sumfiles/gcc.sum | 5205 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1050136 -> 1052408 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 219108 -> 218800 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2540 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 453364 -> 457408 bytes sumfiles/libstdc++.sum | 14 +- 36 files changed, 2905 insertions(+), 3113 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[binutils-gdb] branch master updated (79d40365426 -> 5975a5caceb)

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 79d40365426 gdb: relax requirement for the map_failed stap probe to be present new aa563d160d5 Remove reset_ecs and execution_control_state::reset new 65639fcc542 gdb/python: avoid throwing an exception over libopcodes code new 8eb7d135e32 gdb/disasm: mark functions passed to the disassembler noexcept new 5975a5caceb gdb: mark disassembler function callback types as noexcept The 4 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/disasm-selftests.c | 5 +- gdb/disasm.c | 25 +++++----- gdb/disasm.h | 48 +++++++++++++------ gdb/guile/scm-disasm.c | 2 +- gdb/infrun.c | 123 ++++++++++++++++++------------------------------- gdb/python/py-disasm.c | 91 +++++++++++++++++++++++++++--------- 6 files changed, 165 insertions(+), 129 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (227a0de0ff -> 9076de4ae4)

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 227a0de0ff 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 2e3f899564 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards d4f1d47fac 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards af85b7ad48 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 9f0253e854 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards c0c2b39551 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 1cd53e1f6b 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards a4d4473fb8 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 6489f9a317 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards d3cbe9c0a2 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 8d5f5cd033 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 99ea3df386 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards c245fdff22 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards a390dd2467 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 4fd4668f52 102: onsuccess: #586: 1: Success after binutils: 5 commits discards cfbdd76ac7 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards c47275c6c2 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards af51a98d67 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 95263a238b 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 256f683fb9 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards b9ddae7763 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 1a66c4b150 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards be4cb89510 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 74024dac4a 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 9d083dd271 92: onsuccess: #575: 1: Success after linux: 34 commits discards eca958fbe7 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 590d89e09a 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 716b2dc41b 89: onsuccess: #570: 1: Success after linux: 11 commits discards 717d5f0313 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 6d5ba66400 87: onsuccess: #567: 1: Success after binutils: 8 commits discards bdfacb417f 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards cfb196ffd2 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 95302a5dcc 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards c65157d37f 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 50ad57a73e 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 1249c2fc9d 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards bd69037ec8 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards f160eefc08 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 4b13fd7328 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 5ce0e2a0cd 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards c2ef864973 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 553bb216aa 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 5df89c1ef8 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards ac2c7eeb82 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 01a3b92008 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 79ff9e3886 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards f02152e08e 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 021c711bda 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 816204fae5 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 516f4daa71 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards a50417f029 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 68f94a550f 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 591998ecb8 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 8fcb993490 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 1282df4b5c 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 1864a6128f 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 03c4d9c8f0 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards b8ac8011b1 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards f65add4a69 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 9332af56df 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 7151ee2292 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards a7fb12633b 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 2416a1967c 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 792653ac55 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 4981cafb45 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 68971c4e7d 51: onsuccess: #525: 1: Success after binutils: 8 commits discards d33e7f9833 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards d1ba9168df 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards bad3f89833 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards f7fd86f82c 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 8f23bc7900 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 5e5411ff85 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards dde1adcf50 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 70fa13687a 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 1af1de9ca3 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 4f95b46c22 41: onsuccess: #514: 1: Success after linux: 64 commits discards a83f1e4404 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 70d01109a0 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 7ffb16ce63 38: onsuccess: #508: 1: Success after binutils: 3 commits discards bda86bdf6c 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 406cb39176 36: onsuccess: #505: 1: Success after glibc: 3 commits discards bfa28c1573 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 6f7f6c7c0e 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 510bc52314 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards 4b89b06acb 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards da70abd5c9 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 6f7024242f 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 817238d0e8 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 721a385d6f 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards 0c0ab04606 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 22d445d329 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards 5685c0d55b 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 35ecf2102a 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 4c70d88261 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 595ca362c7 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 7c75f2040a 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c8046266e8 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a4f8ae7750 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 13d167a4a5 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e763308ea8 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fd3f19218c 16: onsuccess: 1: Successful build after binutils: 4 commits new 1fc086fef3 16: onsuccess: 1: Successful build after binutils: 4 commits new 4d3b8807e8 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 25db2b0c9b 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 36117130c3 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 353d013d91 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d1c9b9d8e8 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 30e30bcfc5 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 303a50605f 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new ba403ae980 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 75280e9ebd 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new e11592b31c 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new e528f804e1 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 6fab127512 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new e0c59ac040 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 4c6f6341b6 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new a60c2dc8b3 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 5ce981579b 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 9fa407f818 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new 8b76cfdf28 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new cab7d42a27 35: onsuccess: #503: 1: Success after binutils: 11 commits new 3cbf98e722 36: onsuccess: #505: 1: Success after glibc: 3 commits new 6cb324e851 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new ce4184052a 38: onsuccess: #508: 1: Success after binutils: 3 commits new 74c30b1193 39: onsuccess: #511: 1: Success after binutils: 8 commits new ee88ddda3b 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 3df2d010a1 41: onsuccess: #514: 1: Success after linux: 64 commits new ddb2252277 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 1b697cb169 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new fedda3d282 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new eb8877b234 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 0a2b343d99 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new ed26a87a9c 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new f14f6f1c63 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 785f2ca731 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 65752525ee 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new c1d723e9eb 51: onsuccess: #525: 1: Success after binutils: 8 commits new a1e0fd9d7b 52: onsuccess: #528: 1: Success after binutils: 8 commits new cd39a21eee 53: onsuccess: #531: 1: Success after binutils: 12 commits new 8bae8d1ec9 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 502cc3abdd 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 9e265bb206 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 59a2a4c81b 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 1f3d5069c2 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 63dc625a85 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new c4195d1414 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new feda8b8b1a 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 56a1138362 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new fa2847f78e 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new cdc0d15598 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 443c0603e1 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 1f7d19090c 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 1c0f129e26 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new eba7c2370a 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new c9c7b87904 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 2848b3e3c6 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new d30573f78b 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new ed7c67e5ac 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new 605af0dda7 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new eb061c7757 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new cb11715c37 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 0a24e49f7a 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 9f5d890e00 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new ade0025d17 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 34d1075b39 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new fad18eeb71 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 1d61aa3d11 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 702752831a 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 76393cf4a0 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 5630109ab1 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 60a684fef5 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new e8382cfac9 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 36eaed93a6 87: onsuccess: #567: 1: Success after binutils: 8 commits new 8a407534e5 88: onsuccess: #569: 1: Success after glibc: 10 commits new 03eccba835 89: onsuccess: #570: 1: Success after linux: 11 commits new 19d6b005d5 90: onsuccess: #572: 1: Success after binutils: 15 commits new 6a3ee0baf7 91: onsuccess: #574: 1: Success after glibc: 3 commits new 7012fe2d39 92: onsuccess: #575: 1: Success after linux: 34 commits new 5735d31864 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new e49e3ce5d5 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new a85a19c8d5 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new f133c5b1ed 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 35e15e675a 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new f73fe835ea 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 4f680dc2d2 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 4c2a1cc65b 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new daa046570e 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 0f9eb0f91d 102: onsuccess: #586: 1: Success after binutils: 5 commits new eb51559d6e 103: onsuccess: #589: 1: Success after binutils: 3 commits new e2964999f2 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new de78ac1c95 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 911e74e4ab 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 6cf1b3deb9 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 549499a632 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 42a0f5f9a7 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 9b07cd35bf 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 85af88d67f 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 5574eba9b2 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 25b6539619 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new a2a32324c0 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 96e2b6ec56 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new ddf55dc87b 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 9076de4ae4 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] 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 (227a0de0ff) \ 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 1688 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 52952 -> 53960 bytes 04-build_abe-gcc/console.log.xz | Bin 233220 -> 235280 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9216 -> 8368 bytes 07-build_abe-glibc/console.log.xz | Bin 236336 -> 235276 bytes 08-build_abe-gdb/console.log.xz | Bin 52020 -> 52708 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2848 -> 3404 bytes 11-check_regression/console.log.xz | Bin 20540 -> 19512 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 56 +- 11-check_regression/mail-body.txt | 221 +- 11-check_regression/results.compare | 117 +- 11-check_regression/results.compare2 | 2554 +++----- 11-check_regression/results.regressions | 116 +- 12-update_baseline/console.log | 62 +- 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 | 223 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 116 +- sumfiles/gdb.log.xz | Bin 1771520 -> 1730344 bytes sumfiles/gdb.sum | 9725 ++++++++++++++++++++++--------- 31 files changed, 8239 insertions(+), 5005 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allmodconfig updated (693b67a485 -> 31153022aa)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 693b67a485 41: onsuccess: #513: 23023: Success after binutils/llvm/qemu [...] new 31153022aa 42: onsuccess: #514: 23023: 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 1700 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 31436 -> 32044 bytes 04-build_kernel_llvm/console.log.xz | Bin 65576 -> 65736 bytes 05-build_abe-qemu/console.log.xz | Bin 31544 -> 30660 bytes 06-build_linux/console.log.xz | Bin 5900 -> 5208 bytes 08-check_regression/console.log.xz | Bin 3928 -> 4320 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 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (9abf1a930f -> c40ffad94e)

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 9abf1a930f 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards bcd6aa9016 108: onsuccess: #850: 1: Success after gcc: 2 commits discards db20638946 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 8bffafecd1 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards eabf4df1a2 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards d61cb3aca2 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 2d8d0c6982 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 9a9565e019 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 5d9dc4e6bd 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards e3e61465cd 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards ee24fa3f6c 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards d23eb078d3 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards b2197af255 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 2c4aa0cf99 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 5027b91cfc 95: onsuccess: #835: 1: Success after binutils: 3 commits discards f92daecb5a 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 2248718406 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards fe29028eff 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 5129a46934 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 64d7ac0ed0 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 75ed4e89e4 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards e3690ed1d4 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 0c18f91019 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 56ac5f1fad 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards a9e9467731 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards eede216609 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards a870be6ae6 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 3b11b0d21e 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 52356fedf2 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 9a42989ceb 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards b9feeaf1a3 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 89282f50b3 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 9822481dd7 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 4aad54a61a 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards fa1e3801d1 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 5a025c43e8 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 86960f2c74 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards f1f7f89f05 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 452abe9979 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 3125db3119 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 1e0d6d41a8 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 10a3aacf15 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 8a37ed77b3 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 28ffaa3340 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards fbec24b720 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 007ec65610 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards b55537740e 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 9ebc974652 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 2ac6f3f6db 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 8522ed451c 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 190dc613a4 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 0cfabf688e 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards f3aa878c8d 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 3d9d71971c 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 080e47f98c 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 34c1548fee 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards f39e4c2405 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 08f4766a55 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 128532cc5c 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 34f50a5183 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards b5a8378208 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 1e33d7214d 48: onsuccess: #782: 1: Success after binutils: 8 commits discards dba6ada688 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 7d750e9e21 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards c02992dbef 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 89cfd9f790 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards e486d6bea1 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards ffcea228cb 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards e012d4f10b 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 1c4384b4bf 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards 97c5c1cf15 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 383986abf6 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards f242f82f0b 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 86a29fcbbf 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 4c5bb5c220 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards ed7cb1324c 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards a2300543c3 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards 5265dd40ab 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards 9f9ae1abbd 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards 904c08e992 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards b1612b203b 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards 82d1259f59 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards ff794f2d9c 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards 62e303825e 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 65e1bbb318 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards 39d230cb7d 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards e614e29735 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards f107215244 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 01200fe535 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b45ad2460d 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fe5cad9c36 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a91e1058f2 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cce2451f88 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 820bbe8ddd 16: onsuccess: 1: Successful build after binutils: 4 commits discards 620c4d6a2b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ddf97679b3 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 394776522a 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e0bd16f984 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fdec3a6d01 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5143a2a689 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9abda65c52 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 14e517a884 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 020e53933f 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f19b7f0541 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9c64d821e7 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3d51c353ab 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 29abfcfeda 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e6919d13f2 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fb5eb77360 16: onsuccess: 1: Successful build after binutils: 4 commits new fd9acc9cc4 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a4b9e27e8c 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 10d90dd117 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 83440f0d21 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c51009788b 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b3075a9786 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 9a4800ef47 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 10707a7202 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 95fe11ada6 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new 45543e6c18 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new 0d45a682f4 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new 056a9685a4 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new 9d982a6dbd 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new 40a4b3db7b 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new 47e01716d6 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new a0eb9590f4 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new 3d04286749 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new fd157804c3 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new e9770ac82d 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new 4a50c96234 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 6e83c1f1c5 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 8afef27606 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new f41879fd36 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new a8b91012d7 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new d324c77b9f 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 3bd60ff70a 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 142b596b3a 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 9a2c2dc8a3 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new f93d922b27 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 2ba2bce64a 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 1a6c28c62a 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 9ed94acc53 48: onsuccess: #782: 1: Success after binutils: 8 commits new b306044904 49: onsuccess: #785: 1: Success after binutils: 12 commits new 6e735a2784 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 8ead1688b6 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new c46e7eaec4 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new a3f0d8a4f3 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 48d1391179 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 9616716c79 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 4741d7b9c3 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 2ae22612a0 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new d9aee993c2 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 8652610a6d 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 36b9cea829 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new faa18d91a4 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 0d830ac3c5 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 4c425eafc0 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 9113c130a3 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 9b7f5da59b 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new a5817f7135 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 29068dd850 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 84d282ab06 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 09821577c2 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 72ea62c71b 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 1cf9cdc33b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 30af9242ae 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 04e41c2f89 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 565cb1cf0d 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 7de7e3ccd5 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 011377f788 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 65a5dd0218 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new e64c567383 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new c536862e8c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new b924e5b6c2 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 507c4fdff7 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new b24a94b628 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new a60a61ca85 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 048fdf9a81 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 65f8facf93 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new cfe127e5f5 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 6b67e69cd3 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 5353b423c2 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 4764da1482 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 7d455ddd09 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 99dcfd3c16 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new ad975ba4a8 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new e605f9d36a 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new be13ed5634 94: onsuccess: #832: 1: Success after binutils: 5 commits new fc24ad80f4 95: onsuccess: #835: 1: Success after binutils: 3 commits new 4f272d27ed 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 64fd92fb1c 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 1476621d1e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new d35bef84cd 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 71212f8ef3 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 2bf04a9ce9 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 587a307337 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 24fc975ffc 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new da9bacd9d6 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 56d5c493f6 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new fbaa214b4e 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 811c6cf824 107: onsuccess: #849: 1: Success after binutils: 5 commits new 2125151a10 108: onsuccess: #850: 1: Success after gcc: 2 commits new dc3671e94b 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new c40ffad94e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] 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 (9abf1a930f) \ 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 1684 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 39900 -> 40332 bytes 04-build_abe-gcc/console.log.xz | Bin 213668 -> 213256 bytes 06-build_abe-linux/console.log.xz | Bin 9272 -> 8392 bytes 07-build_abe-glibc/console.log.xz | Bin 243764 -> 244092 bytes 08-build_abe-gdb/console.log.xz | Bin 39584 -> 40156 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3840 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2432 -> 2564 bytes 11-check_regression/console.log.xz | Bin 5836 -> 8416 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 8 + 11-check_regression/mail-body.txt | 28 + 11-check_regression/results.compare | 11 +- 11-check_regression/results.compare2 | 321 ++- 11-check_regression/results.regressions | 28 + 12-update_baseline/console.log | 56 +- 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 | 30 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 28 + sumfiles/g++.log.xz | Bin 3753052 -> 3758720 bytes sumfiles/g++.sum | 42 +- sumfiles/gcc.log.xz | Bin 3315624 -> 3296532 bytes sumfiles/gcc.sum | 4712 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1082516 -> 1076572 bytes sumfiles/gfortran.sum | 205 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 231788 -> 231692 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 452336 -> 457544 bytes sumfiles/libstdc++.sum | 6 +- 42 files changed, 3080 insertions(+), 2454 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allnoconfig updated (fccdfa02f9 -> 9832690ac1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from fccdfa02f9 24: onsuccess: #466: boot: Success after binutils/gcc/qemu: [...] new 9832690ac1 25: onsuccess: #467: boot: Success after binutils/gcc/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1892 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 31900 -> 32776 bytes 04-build_abe-stage1/console.log.xz | Bin 73128 -> 72988 bytes 05-build_abe-qemu/console.log.xz | Bin 31900 -> 31152 bytes 06-build_linux/console.log.xz | Bin 3308 -> 3304 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3884 -> 4248 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-defconfig updated (09934775ac -> e4e2af0c01)

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-lts-defconfig in repository toolchain/ci/base-artifacts. from 09934775ac 24: onsuccess: #474: boot: Success after binutils/llvm/qemu: [...] new e4e2af0c01 25: onsuccess: #475: boot: 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 1916 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31920 -> 32888 bytes 04-build_kernel_llvm/console.log.xz | Bin 66724 -> 66384 bytes 05-build_abe-qemu/console.log.xz | Bin 32048 -> 31040 bytes 06-build_linux/console.log.xz | Bin 3484 -> 3460 bytes 07-boot_linux/console.log.xz | Bin 6068 -> 6060 bytes 08-check_regression/console.log.xz | Bin 3900 -> 4280 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[gcc] branch master updated (2200b705463 -> 07b9bcc1d14)

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 gcc. from 2200b705463 tree-optimization/107896 - allow v2si to dimode unpacks new 07b9bcc1d14 Fortran: ICE with elemental and dummy argument with VALUE a [...] 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/fortran/trans-stmt.cc | 1 + .../gfortran.dg/elemental_dependency_7.f90 | 28 ++++++++++++++++++++++ 2 files changed, 29 insertions(+) create mode 100644 gcc/testsuite/gfortran.dg/elemental_dependency_7.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[gcc] branch master updated (26aff453bf9 -> 2200b705463)

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 gcc. from 26aff453bf9 libstdc++: [_GLIBCXX_INLINE_VERSION] Adapt dg-error message new 2200b705463 tree-optimization/107896 - allow v2si to dimode unpacks 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/tree-vect-stmts.cc | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allnoconfig updated (a7906d586b -> 3fb8c93ccb)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allnoconfig in repository toolchain/ci/base-artifacts. from a7906d586b 24: onsuccess: #249: all: Success after binutils/llvm/qemu: [...] new 3fb8c93ccb 25: onsuccess: #250: all: Success after binutils/linux/qemu: [...] 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 1692 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29960 -> 29892 bytes 04-build_kernel_llvm/console.log.xz | Bin 64868 -> 65160 bytes 05-build_abe-qemu/console.log.xz | Bin 31224 -> 30716 bytes 06-build_linux/console.log.xz | Bin 3424 -> 3432 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3500 -> 3648 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 12 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits November 2022