-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Different build behavior between murdock and riot/riotbuild:latest image #9645
Copy link
Copy link
Closed
Labels
Area: CIArea: Continuous Integration of RIOT componentsArea: Continuous Integration of RIOT componentsArea: build systemArea: Build systemArea: Build systemArea: toolchainArea: toolchains; everything related to compilation, libc, linking, …Area: toolchains; everything related to compilation, libc, linking, …Area: toolsArea: Supplementary toolsArea: Supplementary toolsType: bugThe issue reports a bug / The PR fixes a bug (including spelling errors)The issue reports a bug / The PR fixes a bug (including spelling errors)Type: trackingThe issue tracks and organizes the sub-tasks of a larger effortThe issue tracks and organizes the sub-tasks of a larger effort
Metadata
Metadata
Labels
Area: CIArea: Continuous Integration of RIOT componentsArea: Continuous Integration of RIOT componentsArea: build systemArea: Build systemArea: Build systemArea: toolchainArea: toolchains; everything related to compilation, libc, linking, …Area: toolchains; everything related to compilation, libc, linking, …Area: toolsArea: Supplementary toolsArea: Supplementary toolsType: bugThe issue reports a bug / The PR fixes a bug (including spelling errors)The issue reports a bug / The PR fixes a bug (including spelling errors)Type: trackingThe issue tracks and organizes the sub-tasks of a larger effortThe issue tracks and organizes the sub-tasks of a larger effort
Description
Compilation behavior is different between
murdockthedockerimage withBUILD_IN_DOCKER=1even withRIOT_CI_BUILD=1.It makes things hard to debug and understand the root cause of problems.
Like for the following PRs:
#9362 Warnings only on murdock
#9605 Warnings only on murdock with llvm
#9507 Enough memory on murdock but not in the container
Sub pull requests
Steps to reproduce the issue
To take one as an example:
Building
tests/pkg_fatfs_vfsforBOARD=wsn430-v1_4works in murdock as it is not complaining but this does notExpected results
It has the same behavior in docker as in murdock, so either both fail or both succeed.
Actual results
Murdock is ok, but in docker it fails with:
Versions
Building with docker in master.