CI doesn't fail if you add nonsense attrs to the front-matter of changelog entries #228
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
awaiting
author
awaiting
contributors
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
Feature/S3
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lix-project/lix#228
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
see https://gerrit.lix.systems/c/lix/+/771/6..7
we do have a flake check for this, but checks include pieces of hydraJobs instead of hydraJobs including all of checks as our ci would need. this has been surprising on multiple occasions already :(
I think we've talked about this before but is there a reason to not make one simply an alias of the other?
hydra jobs are really expensive with all the vm tests they contain, and the key order of hydra jobs is reversed compared to checks. we move everything that is currently a link in checks into checks directly and have a key-flipped version of checks in hydraJobs, but we didn't want to make that big a change just for the (broken
) bugfix