Vector: Tests involving disk buffers fail on NixOS

Created on 9 Jan 2020  路  8Comments  路  Source: timberio/vector

Here is an example: https://app.circleci.com/jobs/github/timberio/vector/70981.

It might be related to some recent changes in the buffers, as these tests worked in https://github.com/timberio/vector/pull/1432 on two weeks old master branch.

buffers tests bug

All 8 comments

@LucioFranco do you mind seeing what's going on here (assuming it's related to recent work?)

@a-rodin do you know how I can reproduce this locally? Seems like just a slow system, that assert I believe relates to total events passed through so unless there was an error I doubt its the disk buffer.

@LucioFranco can you try running the tests on the nix docker image? And even if the test is slow, is there a way to deterministically wait for the test to complete?

@binarylogic yeah I can, will do so tomorrow.

It is possible to run these tests locally in Docker using this command:

./scripts/docker-run.sh verifier-nixos ./scripts/verify-nix.sh

I am having issues with running that command:

[BUG] Bus Error at 0x00007f502bd0ca2c
ruby 2.6.4p104 (2019-08-28) [x86_64-linux]

-- Machine register context ------------------------------------------------
 RIP: 0x00007f502bd0ca2c RBP: 0x00007ffdf5653fd0 RSP: 0x00007ffdf5653ed8
 RAX: 0x00007f502bd0ca2c RBX: 0x00007f502bde4000 RCX: 0x0000000000000000
 RDX: 0x0000000000000000 RDI: 0x00007f502bde3010 RSI: 0x0000000000000001
  R8: 0x0000000000000000  R9: 0x00007f502bc4b7c8 R10: 0x00007f502bde3000
 R11: 0x0000000000000206 R12: 0x00007f502bde2c40 R13: 0x00007ffdf5653f28
 R14: 0x00007f502c1fa008 R15: 0x00000000ffffffff EFL: 0x0000000000010202

-- C level backtrace information -------------------------------------------
Bus error

this is on WSL2 with docker desktop edge with WSL2 support.

Update: Both @a-rodin and I finally got this running locally. We both had it passing which tells me the CI machines are just being too slow. The test is correct and everything passes on a larger machine.

Going to close this issue since technically the test passes and the larger time we applied has seemed to fix it.

Was this page helpful?
0 / 5 - 0 ratings