-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
remove .github/workflows/ci_ssl.yml; instead run via trunner_thirdparty #16221
Conversation
76c4cd4
to
874aae0
Compare
Ping @FedericoCeratto since he wrote these tests. |
ping @FedericoCeratto |
1 similar comment
ping @FedericoCeratto |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are integration tests. How about creating a tests/integration
directory with a dedicated README, to collect such tests?
Also, the PR remove the github action without adding a new one it seems.
If the new file is picked up automatically by testament this becomes a problem: people should be able to run the "default" test suite without any network interaction.
That's not specific to that test, Here's a better idea for future work: testament spec tags, see timotheecour#445. As explained in this RFC, tags, unlike file hierarchies, can model fact that a given test can be associated with different tags, eg:
That's the whole point, as explained in PR, a separate github action for this test isnt' needed, the test runs via existing CI pipelines (via
that's a good point; timotheecour#445 would solve this nicely via:
In the meantime, I can also simply add a custom define flag in |
874aae0
to
ab7d984
Compare
@FedericoCeratto PTAL, see
|
An actual flag to testament would be appreciated. |
I thought about this but decided it'd be better to use
which avoids adding N flags and instead simplifies into 1 flag (--tags) and N tags (js, networking, benchmarking, flaky, etc) that can be used for filtering what to run (generalizes testament categories which are hardcoded to a single dir and can't express fact that some tests can be associated with multiple tags). |
And please document the flags you added. |
done |
f54fd02
to
96ceca0
Compare
PTAL |
96ceca0
to
f3e62bf
Compare
f3e62bf
to
ef17fcf
Compare
ping @alaviss (had to rebase again for conflicts) is this good to go? this is needed to avoid things like #16667 (comment) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
testament
looks good to me
var client = newHttpClient(sslContext = ctx) | ||
let a = $client.getContent(expired) | ||
test "httpclient in insecure mode": | ||
var ctx = newContext(verifyMode = CVerifyPeerUseEnvVars) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did you change the mode here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't, it's a github diff artifact. check the diff more carefully (look also with "ignore whitespace", or with a local git diff)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
ef17fcf
to
6229500
Compare
…oken tests and enable them locally
6229500
to
7ed5726
Compare
PTAL, I had to rebase again to avoid bitrot conflicts. note: the diff is smaller than it seems from github; eg: git diff -w origin/devel:tests/untestable/thttpclient_ssl.nim HEAD:tests/untestable/thttpclient_ssl_remotenetwork.nim
|
update
--pedantic
--putenv:NIM_TESTAMENT_REMOTE_NETWORKING:1
in runCI which gets propagated all the way through process calls down to individual tests (easiest way to propagate a flag) so that by default, CI will run with external networking enabled, and running locally testament will not; but can be easily overridden with --putenv:NIM_TESTAMENT_REMOTE_NETWORKING:1. This is abstracted viatestutils.enableRemoteNetworking
so individual tests can query for this in a typesafe way-d:nimTestsEnableFlaky
to ease identifying tests broken on a specific platform and make ie easy to enable those tests locally by changing a single flag (in tests/config.nims)note: use hide whitespace changes to view a smaller diff (because of re-indentation i needed)
future work