test: copyedit `test-tls-psk-alpn-callback-exception-handling` by aduh95 · Pull Request #63485 · nodejs/node

aduh95 · 2026-05-22T09:33:38Z

Make the assertions more intention revealing

codecov · 2026-05-22T11:00:27Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.22%. Comparing base (e7864e6) to head (8a1f4ec).
⚠️ Report is 16 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #63485 +/- ##
==========================================
- Coverage 90.24% 90.22% -0.03% 
==========================================
Files 741 741 Lines 241665 241665 Branches 45543 45538 -5 ==========================================
- Hits 218092 218043 -49 - Misses 15105 15158 +53 + Partials 8468 8464 -4

see 31 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Renegade334 · 2026-07-02T23:18:13Z

- server.on('secureConnection', () => {
- reject(new Error('secureConnection should not fire'));
- });
+ server.on('secureConnection', common.mustNotCall('secureConnection listener'));


What happens if this fires while promise is being awaited at the end of the test function, and tlsClientError doesn't fire? Seems like the event will be handled outside of the test's promise task, promise won't be resolved or rejected, and the test will hang until timeout?

node/test/common/index.js
Lines 563 to 572 in 5922197
functionmustNotCall(msg){
constcallSite=getCallSites()[1];
returnfunctionmustNotCall(...args){
constargsInfo=args.length>0 ?
`\ncalled with arguments: ${args.map((arg)=>inspect(arg)).join(', ')}` : '';
assert.fail(
`${msg||'function should not have been called'} at ${callSite.scriptName}:${callSite.lineNumber}`+
argsInfo);
};
}
It would throw an unhandled rejection which would terminate the process immediately
In any case, a pending promise is not enough to keep the process alive, so no the test won't hang

mcollina

lgtm

nodejs-github-bot · 2026-07-13T13:21:15Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74781/

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>

nodejs-github-bot · 2026-07-13T20:11:55Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74795/

nodejs-github-bot · 2026-07-14T09:00:23Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74805/

nodejs-github-bot · 2026-07-14T12:58:03Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74810/

nodejs-github-bot · 2026-07-15T10:59:59Z

Landed in 824bc66

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com> PR-URL: #63485 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>

aduh95 · 2026-05-22T09:33:38Z

Make the assertions more intention revealing

codecov · 2026-05-22T11:00:27Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.22%. Comparing base (e7864e6) to head (8a1f4ec).
⚠️ Report is 16 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #63485 +/- ##
==========================================
- Coverage 90.24% 90.22% -0.03% 
==========================================
Files 741 741 Lines 241665 241665 Branches 45543 45538 -5 ==========================================
- Hits 218092 218043 -49 - Misses 15105 15158 +53 + Partials 8468 8464 -4

see 31 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Renegade334 · 2026-07-02T23:18:13Z

- server.on('secureConnection', () => {
- reject(new Error('secureConnection should not fire'));
- });
+ server.on('secureConnection', common.mustNotCall('secureConnection listener'));


What happens if this fires while promise is being awaited at the end of the test function, and tlsClientError doesn't fire? Seems like the event will be handled outside of the test's promise task, promise won't be resolved or rejected, and the test will hang until timeout?

node/test/common/index.js
Lines 563 to 572 in 5922197
functionmustNotCall(msg){
constcallSite=getCallSites()[1];
returnfunctionmustNotCall(...args){
constargsInfo=args.length>0 ?
`\ncalled with arguments: ${args.map((arg)=>inspect(arg)).join(', ')}` : '';
assert.fail(
`${msg||'function should not have been called'} at ${callSite.scriptName}:${callSite.lineNumber}`+
argsInfo);
};
}
It would throw an unhandled rejection which would terminate the process immediately
In any case, a pending promise is not enough to keep the process alive, so no the test won't hang

mcollina

lgtm

nodejs-github-bot · 2026-07-13T13:21:15Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74781/

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>

nodejs-github-bot · 2026-07-13T20:11:55Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74795/

nodejs-github-bot · 2026-07-14T09:00:23Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74805/

nodejs-github-bot · 2026-07-14T12:58:03Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74810/

nodejs-github-bot · 2026-07-15T10:59:59Z

Landed in 824bc66

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com> PR-URL: #63485 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>

aduh95 · 2026-05-22T09:33:38Z

Make the assertions more intention revealing

codecov · 2026-05-22T11:00:27Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.22%. Comparing base (e7864e6) to head (8a1f4ec).
⚠️ Report is 16 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #63485 +/- ##
==========================================
- Coverage 90.24% 90.22% -0.03% 
==========================================
Files 741 741 Lines 241665 241665 Branches 45543 45538 -5 ==========================================
- Hits 218092 218043 -49 - Misses 15105 15158 +53 + Partials 8468 8464 -4

see 31 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Renegade334 · 2026-07-02T23:18:13Z

- server.on('secureConnection', () => {
- reject(new Error('secureConnection should not fire'));
- });
+ server.on('secureConnection', common.mustNotCall('secureConnection listener'));


What happens if this fires while promise is being awaited at the end of the test function, and tlsClientError doesn't fire? Seems like the event will be handled outside of the test's promise task, promise won't be resolved or rejected, and the test will hang until timeout?

node/test/common/index.js
Lines 563 to 572 in 5922197
functionmustNotCall(msg){
constcallSite=getCallSites()[1];
returnfunctionmustNotCall(...args){
constargsInfo=args.length>0 ?
`\ncalled with arguments: ${args.map((arg)=>inspect(arg)).join(', ')}` : '';
assert.fail(
`${msg||'function should not have been called'} at ${callSite.scriptName}:${callSite.lineNumber}`+
argsInfo);
};
}
It would throw an unhandled rejection which would terminate the process immediately
In any case, a pending promise is not enough to keep the process alive, so no the test won't hang

mcollina

lgtm

nodejs-github-bot · 2026-07-13T13:21:15Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74781/

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>

nodejs-github-bot · 2026-07-13T20:11:55Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74795/

nodejs-github-bot · 2026-07-14T09:00:23Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74805/

nodejs-github-bot · 2026-07-14T12:58:03Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74810/

nodejs-github-bot · 2026-07-15T10:59:59Z

Landed in 824bc66

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com> PR-URL: #63485 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>

aduh95 · 2026-05-22T09:33:38Z

Make the assertions more intention revealing

codecov · 2026-05-22T11:00:27Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.22%. Comparing base (e7864e6) to head (8a1f4ec).
⚠️ Report is 16 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #63485 +/- ##
==========================================
- Coverage 90.24% 90.22% -0.03% 
==========================================
Files 741 741 Lines 241665 241665 Branches 45543 45538 -5 ==========================================
- Hits 218092 218043 -49 - Misses 15105 15158 +53 + Partials 8468 8464 -4

see 31 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Renegade334 · 2026-07-02T23:18:13Z

- server.on('secureConnection', () => {
- reject(new Error('secureConnection should not fire'));
- });
+ server.on('secureConnection', common.mustNotCall('secureConnection listener'));


What happens if this fires while promise is being awaited at the end of the test function, and tlsClientError doesn't fire? Seems like the event will be handled outside of the test's promise task, promise won't be resolved or rejected, and the test will hang until timeout?

node/test/common/index.js
Lines 563 to 572 in 5922197
functionmustNotCall(msg){
constcallSite=getCallSites()[1];
returnfunctionmustNotCall(...args){
constargsInfo=args.length>0 ?
`\ncalled with arguments: ${args.map((arg)=>inspect(arg)).join(', ')}` : '';
assert.fail(
`${msg||'function should not have been called'} at ${callSite.scriptName}:${callSite.lineNumber}`+
argsInfo);
};
}
It would throw an unhandled rejection which would terminate the process immediately
In any case, a pending promise is not enough to keep the process alive, so no the test won't hang

mcollina

lgtm

nodejs-github-bot · 2026-07-13T13:21:15Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74781/

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>

nodejs-github-bot · 2026-07-13T20:11:55Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74795/

nodejs-github-bot · 2026-07-14T09:00:23Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74805/

nodejs-github-bot · 2026-07-14T12:58:03Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74810/

nodejs-github-bot · 2026-07-15T10:59:59Z

Landed in 824bc66

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com> PR-URL: #63485 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>

aduh95 · 2026-05-22T09:33:38Z

Make the assertions more intention revealing

codecov · 2026-05-22T11:00:27Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.22%. Comparing base (e7864e6) to head (8a1f4ec).
⚠️ Report is 16 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #63485 +/- ##
==========================================
- Coverage 90.24% 90.22% -0.03% 
==========================================
Files 741 741 Lines 241665 241665 Branches 45543 45538 -5 ==========================================
- Hits 218092 218043 -49 - Misses 15105 15158 +53 + Partials 8468 8464 -4

see 31 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Renegade334 · 2026-07-02T23:18:13Z

- server.on('secureConnection', () => {
- reject(new Error('secureConnection should not fire'));
- });
+ server.on('secureConnection', common.mustNotCall('secureConnection listener'));


What happens if this fires while promise is being awaited at the end of the test function, and tlsClientError doesn't fire? Seems like the event will be handled outside of the test's promise task, promise won't be resolved or rejected, and the test will hang until timeout?

node/test/common/index.js
Lines 563 to 572 in 5922197
functionmustNotCall(msg){
constcallSite=getCallSites()[1];
returnfunctionmustNotCall(...args){
constargsInfo=args.length>0 ?
`\ncalled with arguments: ${args.map((arg)=>inspect(arg)).join(', ')}` : '';
assert.fail(
`${msg||'function should not have been called'} at ${callSite.scriptName}:${callSite.lineNumber}`+
argsInfo);
};
}
It would throw an unhandled rejection which would terminate the process immediately
In any case, a pending promise is not enough to keep the process alive, so no the test won't hang

mcollina

lgtm

nodejs-github-bot · 2026-07-13T13:21:15Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74781/

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>

nodejs-github-bot · 2026-07-13T20:11:55Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74795/

nodejs-github-bot · 2026-07-14T09:00:23Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74805/

nodejs-github-bot · 2026-07-14T12:58:03Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74810/

nodejs-github-bot · 2026-07-15T10:59:59Z

Landed in 824bc66

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com> PR-URL: #63485 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>

aduh95 · 2026-05-22T09:33:38Z

Make the assertions more intention revealing

codecov · 2026-05-22T11:00:27Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.22%. Comparing base (e7864e6) to head (8a1f4ec).
⚠️ Report is 16 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #63485 +/- ##
==========================================
- Coverage 90.24% 90.22% -0.03% 
==========================================
Files 741 741 Lines 241665 241665 Branches 45543 45538 -5 ==========================================
- Hits 218092 218043 -49 - Misses 15105 15158 +53 + Partials 8468 8464 -4

see 31 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Renegade334 · 2026-07-02T23:18:13Z

- server.on('secureConnection', () => {
- reject(new Error('secureConnection should not fire'));
- });
+ server.on('secureConnection', common.mustNotCall('secureConnection listener'));


What happens if this fires while promise is being awaited at the end of the test function, and tlsClientError doesn't fire? Seems like the event will be handled outside of the test's promise task, promise won't be resolved or rejected, and the test will hang until timeout?

node/test/common/index.js
Lines 563 to 572 in 5922197
functionmustNotCall(msg){
constcallSite=getCallSites()[1];
returnfunctionmustNotCall(...args){
constargsInfo=args.length>0 ?
`\ncalled with arguments: ${args.map((arg)=>inspect(arg)).join(', ')}` : '';
assert.fail(
`${msg||'function should not have been called'} at ${callSite.scriptName}:${callSite.lineNumber}`+
argsInfo);
};
}
It would throw an unhandled rejection which would terminate the process immediately
In any case, a pending promise is not enough to keep the process alive, so no the test won't hang

mcollina

lgtm

nodejs-github-bot · 2026-07-13T13:21:15Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74781/

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>

nodejs-github-bot · 2026-07-13T20:11:55Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74795/

nodejs-github-bot · 2026-07-14T09:00:23Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74805/

nodejs-github-bot · 2026-07-14T12:58:03Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74810/

nodejs-github-bot · 2026-07-15T10:59:59Z

Landed in 824bc66

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com> PR-URL: #63485 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>

aduh95 · 2026-05-22T09:33:38Z

Make the assertions more intention revealing

codecov · 2026-05-22T11:00:27Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.22%. Comparing base (e7864e6) to head (8a1f4ec).
⚠️ Report is 16 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #63485 +/- ##
==========================================
- Coverage 90.24% 90.22% -0.03% 
==========================================
Files 741 741 Lines 241665 241665 Branches 45543 45538 -5 ==========================================
- Hits 218092 218043 -49 - Misses 15105 15158 +53 + Partials 8468 8464 -4

see 31 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Renegade334 · 2026-07-02T23:18:13Z

- server.on('secureConnection', () => {
- reject(new Error('secureConnection should not fire'));
- });
+ server.on('secureConnection', common.mustNotCall('secureConnection listener'));


What happens if this fires while promise is being awaited at the end of the test function, and tlsClientError doesn't fire? Seems like the event will be handled outside of the test's promise task, promise won't be resolved or rejected, and the test will hang until timeout?

node/test/common/index.js
Lines 563 to 572 in 5922197
functionmustNotCall(msg){
constcallSite=getCallSites()[1];
returnfunctionmustNotCall(...args){
constargsInfo=args.length>0 ?
`\ncalled with arguments: ${args.map((arg)=>inspect(arg)).join(', ')}` : '';
assert.fail(
`${msg||'function should not have been called'} at ${callSite.scriptName}:${callSite.lineNumber}`+
argsInfo);
};
}
It would throw an unhandled rejection which would terminate the process immediately
In any case, a pending promise is not enough to keep the process alive, so no the test won't hang

mcollina

lgtm

nodejs-github-bot · 2026-07-13T13:21:15Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74781/

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>

nodejs-github-bot · 2026-07-13T20:11:55Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74795/

nodejs-github-bot · 2026-07-14T09:00:23Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74805/

nodejs-github-bot · 2026-07-14T12:58:03Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74810/

nodejs-github-bot · 2026-07-15T10:59:59Z

Landed in 824bc66

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com> PR-URL: #63485 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>

aduh95 · 2026-05-22T09:33:38Z

Make the assertions more intention revealing

codecov · 2026-05-22T11:00:27Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.22%. Comparing base (e7864e6) to head (8a1f4ec).
⚠️ Report is 16 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #63485 +/- ##
==========================================
- Coverage 90.24% 90.22% -0.03% 
==========================================
Files 741 741 Lines 241665 241665 Branches 45543 45538 -5 ==========================================
- Hits 218092 218043 -49 - Misses 15105 15158 +53 + Partials 8468 8464 -4

see 31 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Renegade334 · 2026-07-02T23:18:13Z

- server.on('secureConnection', () => {
- reject(new Error('secureConnection should not fire'));
- });
+ server.on('secureConnection', common.mustNotCall('secureConnection listener'));


What happens if this fires while promise is being awaited at the end of the test function, and tlsClientError doesn't fire? Seems like the event will be handled outside of the test's promise task, promise won't be resolved or rejected, and the test will hang until timeout?

node/test/common/index.js
Lines 563 to 572 in 5922197
functionmustNotCall(msg){
constcallSite=getCallSites()[1];
returnfunctionmustNotCall(...args){
constargsInfo=args.length>0 ?
`\ncalled with arguments: ${args.map((arg)=>inspect(arg)).join(', ')}` : '';
assert.fail(
`${msg||'function should not have been called'} at ${callSite.scriptName}:${callSite.lineNumber}`+
argsInfo);
};
}
It would throw an unhandled rejection which would terminate the process immediately
In any case, a pending promise is not enough to keep the process alive, so no the test won't hang

mcollina

lgtm

nodejs-github-bot · 2026-07-13T13:21:15Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74781/

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>

nodejs-github-bot · 2026-07-13T20:11:55Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74795/

nodejs-github-bot · 2026-07-14T09:00:23Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74805/

nodejs-github-bot · 2026-07-14T12:58:03Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74810/

nodejs-github-bot · 2026-07-15T10:59:59Z

Landed in 824bc66

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com> PR-URL: #63485 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>

nodejs-github-bot added needs-ci PRs that need a full CI run. test Issues and PRs related to Node.js core tests and test infrastructure. labels May 22, 2026

aduh95 requested a review from mcollina May 26, 2026 15:25

aduh95 added the request-ci Add this label to start a Jenkins CI on a PR. label May 26, 2026

aduh95 requested a review from Renegade334 July 2, 2026 08:40

Renegade334 reviewed Jul 2, 2026
View reviewed changes

mcollina approved these changes Jul 13, 2026
View reviewed changes

github-actionsBot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jul 13, 2026

test: copyedit test-tls-psk-alpn-callback-exception-handling
8a1f4ec
Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>

aduh95 force-pushed the test-tls-psk-alpn-callback-exception-handling branch from da7d903 to 8a1f4ecCompare July 13, 2026 19:57

aduh95 added author ready PRs with CI started, the required approvals, and no outstanding review comments. request-ci Add this label to start a Jenkins CI on a PR. labels Jul 13, 2026

github-actionsBot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jul 13, 2026

aduh95 added the commit-queue PRs queued for automated landing through the Commit Queue. label Jul 15, 2026

nodejs-github-bot removed the commit-queue PRs queued for automated landing through the Commit Queue. label Jul 15, 2026

nodejs-github-bot merged commit 824bc66 into nodejs:mainJul 15, 2026
74 checks passed

aduh95 added a commit that referenced this pull request Jul 21, 2026
test: copyedit test-tls-psk-alpn-callback-exception-handling
4e5c61c
Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com> PR-URL: #63485 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>

github-actionsBot mentioned this pull request Jul 21, 2026
2026-07-22, Version 26.6.0 (Current) #64655
Merged

aduh95 added a commit that referenced this pull request Jul 21, 2026
test: copyedit test-tls-psk-alpn-callback-exception-handling
28cb3f6
Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com> PR-URL: #63485 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>

RafaelGSS pushed a commit that referenced this pull request Jul 29, 2026
test: copyedit test-tls-psk-alpn-callback-exception-handling
0db4e10
Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com> PR-URL: #63485 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>

aduh95 added a commit that referenced this pull request Aug 6, 2026
test: copyedit test-tls-psk-alpn-callback-exception-handling
14b710c
Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com> PR-URL: #63485 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>

aduh95 mentioned this pull request Aug 22, 2026
2026-08-26, Version 24.20.0 'Krypton' (LTS) #65461
Merged