| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Argh! |
Sorry, something went wrong.
|
cc @encukou @vstinner I'm confused by this error as the struct has existed with the members that we need since v0.7 (2016) of libzstd. Do you have any suggestions? A |
Sorry, something went wrong.
|
Is it worth setting the ZDICT_STATIC_LINKING_ONLY define? The other option is to remove the fallback symbol detection and have autoconf just check for >=1.4.5. |
Sorry, something went wrong.
|
IMO, the >=1.4.5 check is safer. |
Sorry, something went wrong.
|
For reference, v1.4.4 and earlier guarded the symbol behind a define. It was stabilised (facebook/zstd#2111) in v1.4.5. |
Sorry, something went wrong.
|
free-threaded tsan failure is spurious: 1 test failed: test_asyncio.test_free_threading |
Sorry, something went wrong.
|
test_datetime's [24, 24, 24] leaks are also spurious: this PR doesn't include #133498. I checked:
|
Sorry, something went wrong.
|
The buildbots don't seem to have scheduled |
Sorry, something went wrong.
Same thing happened at #133497 (comment). Trying again worked. |
Sorry, something went wrong.
|
I'm still not seeing e.g. 'AMD64 RHEL8 LTO PR' in the pending checks list? |
Sorry, something went wrong.
|
buildbot/PPC64LE RHEL8 Refleaks PR failures are the leaks: test_datetime leaked [24, 24, 24] memory blocks, sum=72 FAIL: test_interrupt (test.test_multiprocessing_spawn.test_processes.WithProcessesTestProcess.test_interrupt) Re-running test.test_multiprocessing_spawn.test_processes in verbose mode (matching: test_interrupt) Re-running test_datetime in verbose mode test_datetime leaked [24, 24, 24] memory blocks, sum=72 |
Sorry, something went wrong.
|
AMD64 RHEL8 FIPS No Builtin Hashes is unstable; failed in the usual way here. |
Sorry, something went wrong.
|
Looking good so far, let's merge. Thanks both! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
We now have better version detection in autoconf, including detecting the most recent symbol we used. A hard version check in the header file can lead to spurious failures when using zstd versions between 1.1.3 (symbol added) and 1.4.5 (symbol stabilised).
xref:
A