Repository navigation
research: publish canonical pilot v1 dataset and analysis - #151
Merged
Merged
Conversation
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (8)
📒 Files selected for processing (23)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
ErenAri
marked this pull request as ready for review
September 18, 2026 21:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Publish the first successful prospective BPFCompat pilot collection as an
immutable repository dataset snapshot, then generate descriptive RQ1–RQ4 tables
from that snapshot under CI.
Canonical collection
353938334645de550e5cc8c659872a90fc262eb0250c229bf2310566859006sha256:7aae7b5c099739ef0bcad74fbb3731aaafb1177f1ba128020729b08803610910collection_complete: truefully_evaluable: falseThe seven inconclusive executions are the frozen
oracle-linux-9-uek7-5.15logical profile. The vendor image actually booted6.12 UEK, so those executions retain the exact observed environment but are not
claimed as evidence about requested 5.15 compatibility.
Dataset publication
Adds
research/data/v1/with:artifact and canonical
executions.jsonldigest.Raw reports are not duplicated into Git history. Their exact hashes and paths
are committed; the content-addressed full Actions artifact remains staging
evidence to copy into the later DOI archive.
Deterministic analysis
Adds
scripts/research/analyze-study-v1.pyand generated RQ1–RQ4 outputs underresearch/analysis/v1/.test-analysis-v1.shregenerates the outputs,compares them byte-for-byte, checks dataset SHA-256s, and asserts key collection
invariants.
The main research preflight now runs that reproduction gate whenever the
dataset, analysis, or analysis scripts change.
Descriptive pilot findings
RQ1: For the controlled
BPF_MAP_TYPE_RINGBUFprobe, the simple upstreamLinux 5.8 version threshold agrees with 8/9 conclusive pilot observations
(88.889%). AlmaLinux 8's observed 4.18 kernel is the below-threshold compatible
exception, consistent with a vendor backport. The 5.8 threshold is bound to
Linux commit
457f44363a8894135c85b7a9afd2bd8196db24ab.RQ2: Outside the calibration case there are 4 incompatible observations
among 54 evaluable executions: 2
UNSUPPORTED_MAP_TYPEand 2COMMAND_VALIDATION_FAILURE. Calibration remains separately reported and isnever mixed into field-failure prevalence.
RQ3: The paired Cilium-derived paths have 0 verdict disagreements across 9
conclusive exact environments. This is intentionally not interpreted as a
pure loader-effect estimate because libbpf exercises load+attach while the
cilium/ebpf path is load-only.
RQ4: The pilot records 10 exact environments and two cross-vendor
version inversions where an older-numbered kernel passes while a newer-numbered
kernel fails. Patch-level longitudinal change is not estimable in v1 because
there is only one exact environment per logical profile.
These are selected, stratified x86_64 pilot results, not population estimates
for Linux deployments.
Still pending
Summary by CodeRabbit
New Features
Documentation
Tests