Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fs-storage-test.c++ failure #12

Open
dwrensha opened this issue Oct 13, 2015 · 3 comments
Open

fs-storage-test.c++ failure #12

dwrensha opened this issue Oct 13, 2015 · 3 comments

Comments

@dwrensha
Copy link
Collaborator

I'm having trouble reproducing this right now, but earlier today I was repeatedly hitting this test failure:

blackrock/fs-storage.c++:2123: failed: expected journal.openObject(id, xattr) != nullptr; object not found
stack: 0x4a105d 0x4400ab 0x440109 0x4e9d8d 0x495022 0x4e95a0 0x4e6410 0x4eb1f0 0x4ea590 0x4ec380 0x488d70 0x48ec8c 0x47e425 0x4d2570
[ FAIL ] fs-storage-test.c++:99: basic assignables
[ TEST ] fs-storage-test.c++:158: use after reload
blackrock/fs-storage-test.c++:164: failed: expected value.getText() == "bar"
stack: 0x4904f5 0x47c70a 0x4d2570 0x49b78a 0x4d1cf4 0x4d1aad 0x4c810f 0x49b78a 0x4c632c 0x4d0e12 0x7f8b12cb3a40 0x4079a9
:0: failed: Called null capability.
stack: 0x488d70 0x48ec8c 0x47c805 0x4d2570
[ FAIL ] fs-storage-test.c++:158: use after reload
[ TEST ] fs-storage-test.c++:185: delete some children
blackrock/fs-storage-test.c++:194: failed: expected sandstorm::listDirectoryFd(main).size() == 4
stack: 0x48bcf5 0x47a423 0x4d2570 0x49b78a 0x4d1cf4 0x4d1aad 0x4c810f 0x49b78a 0x4c632c 0x4d0e12 0x7f8b12cb3a40 0x4079a9
blackrock/fs-storage-test.c++:207: failed: expected size == 4096 * 2; size = 4096
stack: 0x48f7bf 0x47ab74 0x4d2570 0x49b78a 0x4d1cf4 0x4d1aad 0x4c810f 0x49b78a 0x4c632c 0x4d0e12 0x7f8b12cb3a40 0x4079a9
blackrock/fs-storage-test.c++:216: failed: expected sandstorm::listDirectoryFd(main).size() == 2
stack: 0x48bcf5 0x47adb2 0x4d2570 0x49b78a 0x4d1cf4 0x4d1aad 0x4c810f 0x49b78a 0x4c632c 0x4d0e12 0x7f8b12cb3a40 0x4079a9
:0: failed: Called null capability.
stack: 0x487db0 0x48f0fc 0x47b0e5 0x4d2570
[ FAIL ] fs-storage-test.c++:185: delete some children
[ TEST ] fs-storage-test.c++:242: delete volume child while still writing
blackrock/fs-storage-test.c++:251: failed: expected sandstorm::listDirectoryFd(main).size() == 2
stack: 0x48bcf5 0x4772b3 0x4d2570 0x49b78a 0x4d1cf4 0x4d1aad 0x4c810f 0x49b78a 0x4c632c 0x4d0e12 0x7f8b12cb3a40 0x4079a9
blackrock/fs-storage-test.c++:280: failed: expected size == 4096 * 2; size = 4096
stack: 0x48f7bf 0x478454 0x4d2570 0x49b78a 0x4d1cf4 0x4d1aad 0x4c810f 0x49b78a 0x4c632c 0x4d0e12 0x7f8b12cb3a40 0x4079a9
blackrock/fs-storage-test.c++:287: failed: expected sandstorm::listDirectoryFd(main).size() == 2
stack: 0x48bcf5 0x4785aa 0x4d2570 0x49b78a 0x4d1cf4 0x4d1aad 0x4c810f 0x49b78a 0x4c632c 0x4d0e12 0x7f8b12cb3a40 0x4079a9
blackrock/fs-storage-test.c++:301: failed: expected root.getStorageUsageRequest().send().wait(env.io.waitScope).getTotalBytes() == 4096*2
stack: 0x48fd65 0x4789ab 0x4d2570 0x49b78a 0x4d1cf4 0x4d1aad 0x4c810f 0x49b78a 0x4c632c 0x4d0e12 0x7f8b12cb3a40 0x4079a9
@dwrensha
Copy link
Collaborator Author

It seems like this happens roughly 50 percent of the time when I do make continuous. It only ever happens on the first run; if I run the test binary by itself, or if I trivially edit the source file to get it to re-compile and re-run, the test always succeeds.

@paulproteus
Copy link
Collaborator

I do actually run into this! I thought I didn't but I wasn't read the logs. I also am OK ignoring it for now on my system.

@kentonv
Copy link
Member

kentonv commented Nov 13, 2015

My guess is that this will be "fixed" when we switch over to the new storage stack I'm working on. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants