You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Doing testing at stage3 under openbsd, I have several failures in rpass-full that I don't have at stage2 (all tests pass at stage2).
In order to debug, I have test it under Linux, and I reproduce theses issues. All errors below come from Linux using make check-stage3-rpass-full (configure options are just --disable-docs and --disable-valgrind-rpass) .
@steveklabnik I am not agreed about A-bsd flag: it is reproductible under Linux. Please note there are also several ICE generated. Thanks to review the labels.
I have run a bisect in order to have some informations.
the check-stage3-rpass-full target start failing with 50f4a0e (more than one year ago), with the introduction of macro-crate test in run-pass-fulldeps.
so basically it say (if I understand well) that macro export don't work with rustc stage3.
Doing testing at stage3 under openbsd, I have several failures in rpass-full that I don't have at stage2 (all tests pass at stage2).
In order to debug, I have test it under Linux, and I reproduce theses issues. All errors below come from Linux using
make check-stage3-rpass-full
(configure options are just--disable-docs
and--disable-valgrind-rpass
) .The failures seems mainly related to plugins.
Errors messages are kind of:
error: macro undefined
error:
derivemay only be applied to structs and enums
And there are some ICE too:
thread 'rustc' panicked at 'fold converted a module to not a module'
thread '<unnamed>' panicked at 'index out of bounds: the len is 60 but the index is 68'
The main difference between stage2 and stage3 is
-C prefer-dynamic
option.The text was updated successfully, but these errors were encountered: