feature/resync2 #5

ahuston-0 · 2025-05-14T20:30:59-04:00

ahuston-0 commented

2025-05-14 20:30:59 -04:00

No description provided.

ahuston-0 added 10 commits 2025-05-14 20:31:05 -04:00

Fix compilation with a nix which was compiled withou aws sdk d12d4753ee

Fix displaying eval errors in jobset eval view c7972c3687

Quickfix for something that annoyed me once too often.

Specifically, I'm talking about `/eval/1#tabs-errors`.

To not fetch long errors on each request, this is only done on-demand.
I.e., when the tab is opened, an iframe is requested with the errors.
This iframe uses a template for both the jobset view and the jobset-eval
view. It is differentiated by checking if `jobset` or `eval` is defined.

However, the jobset-eval view also has a `jobset` variable in its stash
which means that in both cases the `if` path was used. Since
`jobset.fetcherrormsg` isn't defined in the eval case though, you always
got an empty error.

The band-aid fix is relatively simple: swap if and else: the `eval`
variable is not defined in the stash of the jobset view, so now this is
a useful condition to decide which view we're in.

(cherry picked from commit 70c3d75f73)

web: increase colspan for machine row in machine status 47158cf360

re-enable restrict-eval for non-flakes fa1e989b7d

jobset-eval: fix actions not showing up sometimes for new jobs 17f9920cf9

New jobs have their "new" status take precedence over them being
"failed" or "queued", which means actions that can act on "failed" or
"queued" jobs weren't shown to the user when they could only act on
"new" jobs.

(cherry picked from commit 9a4a5dd624)

flake.lock: Update d5d4d19a4c

Flake lock file updates:

• Updated input 'nix':
    'github:NixOS/nix/a4962f73b5fc874d4b16baef47921daf349addfc' (2025-04-07)
  → 'github:NixOS/nix/70921714cb3b5e6041b7413459541838651079f3' (2025-04-23)
• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/db8f4fe18ce772a9c8f3adf321416981c8fe9371' (2025-04-07)
  → 'github:NixOS/nixpkgs/eea3403f7ca9f9942098f4f2756adab4ec924b2b' (2025-04-23)

Use Nix without the flake 1001b67704

This is what we do for `nix-eval-jobs` already. It allows for more
fine-grained control over dependencies.

hydra: expose nix-cli package 21f793e21b

This makes it easier in other packages to get the nix version used to
build Hydra.

queue runner: attempt at slightly smarter scheduling criteria 0dd4c0cc8e

Instead of just going for "whatever is the oldest build we know of",
use the following first:

- Is the step more constrained? If so, schedule it first to avoid
  filling up "more desirable" build slots with less constrained builds.

- Does the step have more dependents? If so, schedule it first to try
  and maximize open parallelism and breadth of scheduling options.

(cherry picked from commit b8d03adaf4)

Add missing slash 84ce142a9d

error: access to absolute path '/nix/store/sai35xfsrba2a2vasmzxakmn54wdfa13-sourcepackaging' is forbidden in pure evaluation mode (use '--impure' to override)

ahuston-0 merged commit 84ce142a9d into add-gitea-pulls

2025-05-14 20:31:12 -04:00

ahuston-0 deleted branch feature/resync2

2025-05-14 20:33:37 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: ahuston-0/hydra#5