Skip to content

Add realistic process list test data#1836

Merged
KCarretto merged 1 commit intomainfrom
add-process-test-data-9095939779900339488
Feb 22, 2026
Merged

Add realistic process list test data#1836
KCarretto merged 1 commit intomainfrom
add-process-test-data-9095939779900339488

Conversation

@KCarretto
Copy link
Copy Markdown
Collaborator

Added realistic process list generation for test data.

  • Implemented createProcessList helper in tavern/test_data.go.
  • Generated processes for Windows, Linux, MacOS, and BSD.
  • Linked processes to Task and Host entities.
  • Verified creation in tavern/test_data_test.go.

PR created automatically by Jules for task 9095939779900339488 started by @KCarretto

This commit enhances the test data generation logic to create realistic mock process lists for Windows, Linux, MacOS, and BSD hosts.

- Updates `tavern/test_data.go` to include a `createProcessList` function that populates `HostProcess` entities with platform-specific data (PIDs, names, paths, commands, environment variables).
- Modifies `createTestData` to invoke `createProcessList` for a subset of hosts (indices 1-4 in groups 1-3), ensuring at least 3 hosts per platform have process data.
- Adds a `ProcessList` quest and tome to associate with the tasks creating these processes.
- Updates `tavern/test_data_test.go` to verify that the expected number of `HostProcess` entities are created.

Co-authored-by: KCarretto <16250309+KCarretto@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@github-actions
Copy link
Copy Markdown
Contributor

Summary

Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
2608    ±0 2608    ±0 0    ±0 0    ±0 0    ±0 0    ±0 1ms    ±0

Previous Results

Build 🏗️ Result 🧪 Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
#1029 2608 2608 0 0 0 0 37.0s

Insights

Average Tests per Run Total Flaky Tests Total Failed Slowest Test (p95)
2608 0 0 5.8s

Slowest Tests

Test 📝 Results 📊 Duration (avg) ⏱️ Duration (p95) ⏱️
TestDockerExecutor_Build_ContextCancellation 1 5.8s 5.8s
eldritch-libsys: std::dll_inject_impl::tests::test_dll_inject_simple 1 5.2s 5.2s
TestInteractiveShell 1 5.1s 5.1s
TestOtherStreamOutput 1 5.0s 5.0s
imix::bin/imix: install::tests::test_install_execution 3 1.2s 3.4s
imix::bin/imix: install::tests::test_install_execution 3 1.2s 3.4s
imix::bin/imix: install::tests::test_install_execution 3 1.2s 3.4s
imix::bin/imix: tests::task_tests::test_task_streaming_error 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_streaming_error 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_streaming_error 3 3.0s 3.0s

🎉 No failed tests in this run. | 🍂 No flaky tests in this run.

Github Test Reporter by CTRF 💚

@KCarretto KCarretto requested a review from hulto February 21, 2026 23:38
@KCarretto KCarretto marked this pull request as ready for review February 21, 2026 23:38
@KCarretto KCarretto added this pull request to the merge queue Feb 21, 2026
Merged via the queue into main with commit 787d231 Feb 22, 2026
8 checks passed
@KCarretto KCarretto deleted the add-process-test-data-9095939779900339488 branch February 22, 2026 00:08
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

Successfully merging this pull request may close these issues.

2 participants