Reapply "[lldb] Increase timeout on lldbutil.wait_for_file_on_target" (#190833)
Reapplication notes:
After reviewing the test failures that caused the original reverts, I'm
not convinced that this change is related. None of the test failures
failed while timing out waiting for a file.
Original Summary:
I've been tracking sporadic timeouts waiting for a file to appear on
macOS buildbots (and occasionally local development environments). I
believe I've tracked it down to a regression in process launch
performance in macOS.
What I noticed is that running multiple test suites simultaneously
almost always triggered these failures and that the tests were always
waiting on files created by the inferior. Increasing this timeout no
longer triggers the failures on my loaded machine locally.
This timeout moves from about 16 seconds of total wait time to about 127
[4 lines not shown]
[lldb][NFC] Add helper to compute breakpoint's constituent load address (#190762)
This allows the callsite to be simplified.
This also exposes a bug where the variable `ShouldShowError` is guarding
more than the error printing.
NAS-140593 / 27.0.0-BETA.1 / Use /run/middleware instead of /var/run/middleware to avoid symlink in path (#18670)
## Problem
Active node is not able to retrieve debug from standby node because
`filesystem.get` now uses `safe_open` with
`openat2(RESOLVE_NO_SYMLINKS)` (change introduced in
https://github.com/truenas/middleware/pull/18379).
On HA systems where the system dataset lives on a data pool, the standby
node does not have that pool imported. `debug_generate` on the standby
falls back to storing the debug archive under `MIDDLEWARE_RUN_DIR`
(`/var/run/middleware/ixdiagnose/ixdiagnose.tgz`). When the active node
calls `core.download` → `filesystem.get` on the standby to retrieve it,
`openat2` rejects the path with `ELOOP` because `/var/run` is a symlink
to `/run`.
## Solution
[3 lines not shown]
[SPIR-V] Change DL for logical SPIR-V (#190807)
This PR originates from bogner@ draft PR. It modifies the triple for
logical SPIR-V to use the new vector sizing feature.
This means updating the tests, and fix one codegen issue:
on the old datalayout, we knew a float3 allocation size was the
same as a float4 allocation. This is now invalid, thus
a store `<4 x float>` into a `<3 x float>` allocation is UB.
net/nbd-server: Update version 3.25=>3.27.0
Please note that I have tried to build the manpages with docbook2man
but it fails. If someone has any clue I would be happy to have a patch.
Until then the manpages are disabled.
Changelog: https://github.com/NetworkBlockDevice/nbd/releases/tag/nbd-3.27.0
[AMDGPU] Fix duplicate s_wait_asynccnt on gfx12-plus (#190906)
S_WAIT_ASYNCCNT was missing from counterTypeForInstr(), so isWaitInstr() did not recognize it as a wait instruction. On the fixpoint algorithm's second pass over a loop body, the already-inserted S_WAIT_ASYNCCNT was treated as a normal instruction, causing WAIT_ASYNCMARK to be re-processed and a duplicate S_WAIT_ASYNCCNT to be emitted.
Assisted-By: Claude Opus 4.6
[NFC][AMDGPU] don't test asyncmark for non-async variants on pre-gfx12 (#190774)
The test for asyncmark on pref-gfx12 targets, checks the effect of async
marks on both async and non-async instructions. This is achieved by a
sed invocation in the RUN line to remove the .async from intrinsic name.
Such a test serves no purpose other than a minor flex. The two sets of
CHECK lines using the WITH and WITHOUT prefix are not easy to compare by
a simple eyeballing. Eliminating this hack makes it easier to add GISEL
variants later. With and without GISEL, the combinations will increase
to four instead of the current two.
Assisted-By: Claude Opus 4.6
