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

fix(minipipeline): set control expectation for all observations #1419

Merged
merged 1 commit into from
Nov 30, 2023

Conversation

bassosimone
Copy link
Member

Up until now, we were setting the control expectation (i.e., the final result of accessing the website from the control) only for TCP endpoints observations. However, there are cases where we're considering DNS lookup failures where we also need this information.

So, let's just make sure every observation we produce knows about what's the final expectation according to the test helper.

Part of ooni/probe#2634

Up until now, we were setting the control expectation (i.e., the final
result of accessing the website from the control) only for TCP endpoints
observations. However, there are cases where we're considering DNS
lookup failures where we also need this information.

So, let's just make sure every observation we produce knows about what's
the final expectation according to the test helper.

Part of ooni/probe#2634
@bassosimone bassosimone merged commit 4dc6e7d into master Nov 30, 2023
10 checks passed
@bassosimone bassosimone deleted the xcompare branch November 30, 2023 19:43
Murphy-OrangeMud pushed a commit to Murphy-OrangeMud/probe-cli that referenced this pull request Feb 13, 2024
…#1419)

Up until now, we were setting the control expectation (i.e., the final
result of accessing the website from the control) only for TCP endpoints
observations. However, there are cases where we're considering DNS
lookup failures where we also need this information.

So, let's just make sure every observation we produce knows about what's
the final expectation according to the test helper.

Part of ooni/probe#2634
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant