Skip to content

lsquic: don't link c++ explicitly#8154

Closed
arnetheduck wants to merge 2 commits intounstablefrom
cpplib
Closed

lsquic: don't link c++ explicitly#8154
arnetheduck wants to merge 2 commits intounstablefrom
cpplib

Conversation

@arnetheduck
Copy link
Copy Markdown
Member

No description provided.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 23, 2026

Unit Test Results

       12 files  ±0    2 488 suites  ±0   47m 54s ⏱️ - 8m 31s
12 978 tests ±0  12 431 ✔️ ±0  547 💤 ±0  0 ±0 
65 612 runs  ±0  64 902 ✔️ ±0  710 💤 ±0  0 ±0 

Results for commit 4ce8436. ± Comparison against base commit adc18e9.

♻️ This comment has been updated with latest results.

@arnetheduck
Copy link
Copy Markdown
Member Author

@tersec
Copy link
Copy Markdown
Contributor

tersec commented Mar 25, 2026

Holding this until after the next release, which we might try to do soon, if the current setup works. So sequence is test status quo, if works, then wait on this. If not, merge this. Want to avoid disruptions for the moment.

@tersec
Copy link
Copy Markdown
Contributor

tersec commented Mar 28, 2026

Still relevant?

@tersec
Copy link
Copy Markdown
Contributor

tersec commented Mar 30, 2026

nim-lsquic bumped separately.

@tersec tersec closed this Mar 30, 2026
@tersec tersec deleted the cpplib branch March 30, 2026 06:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants