[Bug rust/119508] Hundreds of rust tests XPASS

[powerboat9.gamer at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508

--- Comment #12 from Owen A.  ---
I can't replicate this on my end anymore -- is it still present on x86_64?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug rust/119508] Hundreds of rust tests XPASS

[powerboat9.gamer at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508

--- Comment #16 from Owen A.  ---
*linked builders

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug rust/119508] Hundreds of rust tests XPASS

[powerboat9.gamer at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508

--- Comment #15 from Owen A.  ---
https://code.wildebeest.org/git/mirror/gcc/commit/?id=89ca1e3cb697a87f02682a1fb1f62f02d0671c57

Wildebeest seems to have the patch. It seems like all of the linked tests are
failing for other reasons, though. Does anyone have a link to a builder failing
because of this bug?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug rust/119641] narrowing Warning during bootstrap in Rust::BIR::PlaceDB::lookup_or_add_variable

[powerboat9.gamer at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119641

--- Comment #4 from Owen A.  ---
(In reply to Thomas Schwinge from comment #3)
> (I haven't checked, but) supposedly fixed in trunk via commit
> r16-237-gbeced835afa3908aa94550d2ca5ee3879a620adb "gccrs: Fix narrowing
> conversion warnings".
> 
> Owen, for next time, to auto-annotate GCC Bugzilla, the correct syntax to
> use in Git log would've been to put "PR rust/119641" into the ChangeLog
> snippet, see .

Ah, alright, sorry about that.

> Given this has been filed with "Version: 15.0", should this be cherry-picked
> into releases/gcc-15 branch as well?

I don't think it would hurt to do so.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug rust/119508] Hundreds of rust tests XPASS

[powerboat9.gamer at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508

--- Comment #23 from Owen A.  ---
(In reply to Thomas Schwinge from comment #22)
> (In reply to Owen A. from comment #12)
> > I can't replicate this on my end anymore -- is it still present on x86_64?
> 
> That's a surprising statement, given that I clearly described how to
> reproduce the issue:
> 
> (In reply to myself from comment #11)
> > Running 'check-gcc-rust' with '-j1' looks reasonable.  But, for example,
> > comparing a '-j1' run to a '-j2' run, I see: [...]
> 
> Anyway, now fixed on trunk branch, and will cherry-pick into releases/gcc-15
> branch, once the first GCC 15 release has been done, and
>  "Disable parallel testing for
> 'rust/compile/nr2/compile.exp' [PR119508]".

I've tried -j2, -j3, -j64, etc, on both trunk and
https://github.com/Rust-GCC/gccrs -- I can't reproduce it.

I'm starting to think that, for some reason, my machine is running tests with
parallel testing effectively disabled. That would explain my not being able to
reproduce this bug since "gccrs: nr2.0: Improve test script" was merged.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug rust/119508] Hundreds of rust tests XPASS

[powerboat9.gamer at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508

--- Comment #25 from Owen A.  ---
(In reply to Thomas Schwinge from comment #24)
> (In reply to Owen A. from comment #23)
> > (In reply to Thomas Schwinge from comment #22)
> > > (In reply to Owen A. from comment #12)
> > > > I can't replicate this on my end anymore -- is it still present on 
> > > > x86_64?
> > > 
> > > That's a surprising statement, given that I clearly described how to
> > > reproduce the issue:
> > > 
> > > (In reply to myself from comment #11)
> > > > Running 'check-gcc-rust' with '-j1' looks reasonable.  But, for example,
> > > > comparing a '-j1' run to a '-j2' run, I see: [...]
> 
> > I've tried -j2, -j3, -j64, etc, on both trunk and
> > https://github.com/Rust-GCC/gccrs -- I can't reproduce it.
> 
> I'd like to understand what's happening, what's different.
> 
> Are these '-jN' for 'make -jN check-gcc-rust', or for 'make -jN check'?  The
> former is what I was talking about; the latter includes 'make -jM
> check-gcc-rust', with 'M <= N'; typically 'M << N' ('M' much less than 'N').
> If the latter, you could examine '[build]/gcc/testsuite/rust*'
> directories/content, to see what the actual "'-jM'" parallelism is that's
> used for 'check-gcc-rust'.
> 
> > I'm starting to think that, for some reason, my machine is running tests
> > with parallel testing effectively disabled.
> 
> That seems unlikely to me?  If parallel testing isn't working, you should
> see system load ~1, otherwise ~N.  (..., and again, see
> '[build]/gcc/testsuite/*' directories/content for the details.

`make check-gcc-rust -jN`

-- 
You are receiving this mail because:
You are on the CC list for the bug.