Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangobench --help` got 0 exit code
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangobench --version` and found version 3.3.4
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangodump --help` got 0 exit code
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangodump --version` and found version 3.3.4
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangoexport --help` got 0 exit code
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangoexport --version` and found version 3.3.4
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangoimp --help` got 0 exit code
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangoimp --version` and found version 3.3.4
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangorestore --help` got 0 exit code
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangorestore --version` and found version 3.3.4
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangosh --help` got 0 exit code
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangosh --version` and found version 3.3.4
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangovpack --help` got 0 exit code
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangovpack --version` and found version 3.3.4
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangod --help` got 0 exit code
- ran `/nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4/bin/arangod --version` and found version 3.3.4
- found 3.3.4 with grep in /nix/store/vrgq52j00vwlq56wzq21rzq281lvrzrw-arangodb-3.3.4
I've started digging into the actual cause of the problem a week ago but
didn't continue fixing this.
The reason why the tests are failing is because
torvalds/linux/commit/72f5e08dbba2d01aa90b592cf76c378ea233b00b has
remapped the location of the TSS into the CPU entry area and we did
update our default kernel to version 4.14 in NixOS/nixpkgs@88530e02b6.
Back to VirtualBox: The guru meditation happens in
selmRCGuestTssPostWriteCheck, which I think is only a followup error. I
believe the right location couldn't be determined by VirtualBox and thus
the write check function triggers that panic because it's reading from
the wrong location.
So the actual problem *only* surfaces whenever we use software
virtualization, which we do for our tests because we don't have nested
virtualization available.
Our tests are also for testing the functionality of VirtualBox itself
and not certain kernel versions or kernel features, so for the time
being and until this is fixed, let's actually use kernel version 4.9 for
the guests within the VM tests. Kernel 4.9 didn't have the mentioned
change of the TSS location and thus the tests succeed.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @dtzWill
`boost::system::posix_error` is deprecated since v1.37, however the
default Boost version in NixOS is 1.66.
The following upstream patch fixed the issue:
c9b5b13fb8
See ticket #36453
conan has very strict requirements on the versions of its dependencies.
This patch adds downgraded versinos of node-semver and distro to
statisfy these requirements.
