-
Notifications
You must be signed in to change notification settings - Fork 142
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
TestTaskRunnerRun/with_success_and_max_runtime fails #2541
Labels
bug
Something isn't working
needs investigation
This issue needs extra data and investigation
ooni/probe-engine
priority/high
releaseBlocker
This issue blocks releasing
Comments
bassosimone
added
bug
Something isn't working
priority/high
needs investigation
This issue needs extra data and investigation
ooni/probe-engine
releaseBlocker
This issue blocks releasing
labels
Sep 22, 2023
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
Sep 22, 2023
This diff makes the policy previously known as loadable and now know as the static policy easier to use, by having a constructor that reads from a key-value store and by passing it a fallback policy to use. With this design, it should be possible to have code that uses the static policy if applied, falling back to whatever policy we are otherwise constructing into the NewNetwork constructor. In a subsequent commit, I will hook this code into NewNetwork, so that we can override the policy by changing the filesystem. While there, notice several failures in the test suite and apply workarounds (see ooni/probe#2539, ooni/probe#2540, ooni/probe#2541). Part of ooni/probe#2531.
bassosimone
changed the title
TestTaskRunnerRun/with_succes_and_max_runtime fails
TestTaskRunnerRun/with_success_and_max_runtime fails
Oct 6, 2023
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
Oct 10, 2023
I have ran the test several times locally with `go test -race -count 1` and it was working as intended. Either the CI run issue was just temporary or it's something fundamental of the CI that I can'r reproduce. For this reason, I am going to re-enable the test and see what happens. Closes ooni/probe#2541
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
Oct 10, 2023
I have ran the test several times locally with `go test -race -count 1` and it was working as intended. Either the CI run issue was just temporary or it's something fundamental of the CI that I can't reproduce. For this reason, I am going to re-enable the test and see what happens. Closes ooni/probe#2541
Murphy-OrangeMud
pushed a commit
to Murphy-OrangeMud/probe-cli
that referenced
this issue
Feb 13, 2024
…#1297) This diff makes the policy previously known as loadable and now know as the static policy easier to use, by having a constructor that reads from a key-value store and by passing it a fallback policy to use. With this design, it should be possible to have code that uses the static policy if applied, falling back to whatever policy we are otherwise constructing into the NewNetwork constructor. In a subsequent commit, I will hook this code into NewNetwork, so that we can override the policy by changing the filesystem. While there, notice several failures in the test suite and apply workarounds (see ooni/probe#2539, ooni/probe#2540, ooni/probe#2541). Part of ooni/probe#2531.
Murphy-OrangeMud
pushed a commit
to Murphy-OrangeMud/probe-cli
that referenced
this issue
Feb 13, 2024
I have ran the test several times locally with `go test -race -count 1` and it was working as intended. Either the CI run issue was just temporary or it's something fundamental of the CI that I can't reproduce. For this reason, I am going to re-enable the test and see what happens. Closes ooni/probe#2541
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
needs investigation
This issue needs extra data and investigation
ooni/probe-engine
priority/high
releaseBlocker
This issue blocks releasing
Here's an excerpt from the logs:
This issue is a release blocker.
The text was updated successfully, but these errors were encountered: