On Mon, Mar 2, 2020 at 1:15 PM Gianfranco Costamagna <locutusofb...@debian.org> wrote:
> The following patch is not enough, because of something printed on stderr. > > I'm attaching a "fix" (better would be do not throw stuff on stderr) > crossbuild FAIL stderr: dpkg-architecture: warning: specified GNU > system type arm-linux-gnueabihf does not match CC system type > x86_64-linux-gnu, try setting a correct CC environment variable I hate, hate, hate, hate this feature. It is the stupidest policy choice and for some reason many test frameworks do that, sometimes even silently. The only thing this accomplishes is that people will run their tests with a wrapper script that does ./realcommand 2>&1, because if you call any external program then you have lost control of what gets printed to stderr. Some of those programs are chatty. The proper way of detecting failures is the exit code. That being said, does this happen on all platforms or only a subset of them? > I also cherry-picked an upstream test failure when python is removed and > changed to python2 (a change that is retro-compatible, and will break also > Debian on the next few days) Please file this as a pull request upstream. All big changes like these should go in master first. > Also, please depend on rustc and valac on autopkgtests, so on > each new rustc and valac upstream releases, meson autopkgtests will be > triggered for regressions! That should already be happening. AFAIUI the exhaustive test has a dependency on all build deps of Meson, which includes valac and rustc.
