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.

Sign up for GitHub

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

Jump to bottom

kyua test failures on Ubuntu 24.04 (docker container) #237

Open
ngie-eign opened this issue Dec 1, 2024 · 2 comments
Open

kyua test failures on Ubuntu 24.04 (docker container) #237

ngie-eign opened this issue Dec 1, 2024 · 2 comments

Comments

@ngie-eign
Copy link
Contributor 

2e6dff52d073# kyua report -r ~/.kyua/store/results.usr_local_tests_kyua.20241201-024941-696911.db
...
===> Broken tests
utils/fs/operations_test:free_disk_space__ok__real  ->  broken: Empty test result or no new line  [0.004s]
utils/fs/operations_test:mount_tmpfs__ok__default_size  ->  broken: Empty test result or no new line  [0.005s]
utils/fs/operations_test:mount_tmpfs__ok__explicit_size  ->  broken: Empty test result or no new line  [0.005s]
utils/fs/operations_test:unmount__ok  ->  broken: Empty test result or no new line  [0.004s]
===> Failed tests
engine/atf_test:test__body_only__crashes  ->  failed: Line 155: exp_result != test_result_handle->test_result() (model::test_result{type='broken', reason='Premature exit; test case received signal 6 (core dumped)'} != model::test_result{type='broken', reason='Empty test result or no new line'})  [0.009s]
integration/cmd_test_test:premature_exit  ->  failed: atf-check failed; see the output of the test for details  [0.057s]
utils/stacktrace_test:dump_stacktrace__integration  ->  failed: Line 382: atf::utils::grep_file("#0", exit_handle.stderr_file().str()) not met  [0.006s]
utils/stacktrace_test:dump_stacktrace__ok  ->  failed: Line 411: atf::utils::grep_file("^frame 1$", exit_handle.stderr_file().str()) not met  [0.005s]
utils/stacktrace_test:dump_stacktrace_if_available__append  ->  failed: Line 551: atf::utils::grep_file("frame 1", exit_handle.stderr_file().str()) not met  [0.006s]
utils/stacktrace_test:find_core__found__long  ->  failed: Core dumped, but no candidates found  [0.006s]
utils/stacktrace_test:find_core__found__short  ->  failed: Core dumped, but no candidates found  [0.005s]

I need to doublecheck and see whether or not the "Empty test result or no new line" issues are fixed by a commit I have in the queue.
@ngie-eign ngie-eign changed the title kyua test failures on Ubuntu 24.04 kyua test failures on Ubuntu 24.04 (docker container) Dec 1, 2024
@ngie-eign
Copy link
Contributor Author

ngie-eign commented Dec 1, 2024 •
edited
Loading

It looks like some of the issues are occurring because I'm running the Ubuntu Linux container from within docker on MacOS.
I might need to spin up a full VM in VMware Fusion to confirm that the issues aren't present in non-containerized setups, e.g., on physical hardware.
This might also be why the tmpfs failures are occurring as well since Docker does some interesting things to try and isolate the host from the running containers.

ngie-eign added a commit to ngie-eign/kyua that referenced this issue Dec 1, 2024
@ngie-eign
Add more information to failed results
27b03e9 
This change adds more information to "premature failures" or failures
where no output was provided on the command-line. This is being done to
help make the reasons for why a failure occurred clearer to the
end-user.

This also fixes the fact that several ATF-related tests were failing with
"empty output" (lacking exit code data), or not failing with the
appropriate (expected) "timeout" messages.

This addresses part of freebsd#237 and makes the kyua tests pass cleanly
again on FreeBSD.

Signed-off-by: Enji Cooper <[email protected]>
@ngie-eign ngie-eign mentioned this issue Dec 1, 2024
Merged
ngie-eign added a commit to ngie-eign/kyua that referenced this issue Dec 1, 2024
@ngie-eign
Add more information to failed results
e56c44b 
This change adds more information to "premature failures" or failures
where no output was provided on the command-line. This is being done to
help make the reasons for why a failure occurred clearer to the
end-user.

This also fixes the fact that several ATF-related tests were failing with
"empty output" (lacking exit code data), or not failing with the
appropriate (expected) "timeout" messages.

While here, address the fact that newer versions of sqlite3 fail when
executing statements with `sqlite::api_error` instead of `store::error`.

This addresses part of freebsd#237 and makes the kyua tests pass cleanly
again on FreeBSD.

Signed-off-by: Enji Cooper <[email protected]>
ngie-eign added a commit to ngie-eign/kyua that referenced this issue Dec 1, 2024
@ngie-eign
Add more information to failed results
49dcbd8 
This change adds more information to "premature failures" or failures
where no output was provided on the command-line. This is being done to
help make the reasons for why a failure occurred clearer to the
end-user.

This also fixes the fact that several ATF-related tests were failing with
"empty output" (lacking exit code data), or not failing with the
appropriate (expected) "timeout" messages.

While here, address the fact that newer versions of sqlite3 fail when
executing statements with `sqlite::api_error` instead of `store::error`.

This addresses part of freebsd#237 and makes the kyua tests pass cleanly
again on FreeBSD.

Signed-off-by: Enji Cooper <[email protected]>
ngie-eign added a commit to ngie-eign/kyua that referenced this issue Dec 1, 2024
@ngie-eign
Add more information to failed results
f7ac5e0 
This change adds more information to "premature failures" or failures
where no output was provided on the command-line. This is being done to
help make the reasons for why a failure occurred clearer to the
end-user.

This also fixes the fact that several ATF-related tests were failing with
"empty output" (lacking exit code data), or not failing with the
appropriate (expected) "timeout" messages.

While here, address the fact that newer versions of sqlite3 fail when
executing statements with `sqlite::api_error` instead of `store::error`.

This addresses part of freebsd#237 and makes the kyua tests pass cleanly
again on FreeBSD.

Signed-off-by: Enji Cooper <[email protected]>
@ngie-eign ngie-eign mentioned this issue Dec 1, 2024
Open
@ngie-eign
Copy link
Contributor Author

The utils/fs/operations_test issues don't occur in a full Ubuntu 24.04 VM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ngie-eign