| 27 May 2024 |
 hexa | In reply to @vcunat:matrix.org
Maybe we could do an average over the pair of platforms? the average between two platforms might very well be misleading, e.g. 0 and 1000 -> 500, 0 and 3000 -> 1500 | 13:29:18 |
| hexa | and you'd always have to dig into the list to get the accurate picture, and the list does not necessarily load/render very fast 🙂 | 13:30:00 |
 vcunat | Intuitively I'd want just a single number that estimates the amount of work for Hydra (say, even hours needed if doing nothing else). | 13:30:42 |
| vcunat | But perhaps there are more use cases for this. | 13:31:10 |
| hexa | so what would be a good number you could derive from two linux platforms for example? | 13:32:36 |
| hexa | I think the sum would be much less misleading fwiw | 13:33:20 |
| hexa | and would require less interpretation | 13:33:29 |
| vcunat | Sum might be best. | 13:34:22 |
| vcunat | But just the label name won't provide much understanding of the meaning anyway.
| 13:34:46 |
| vcunat | Like, the fact that two platforms are involved in the "rebuild-linux" label.
| 13:35:15 |
| vcunat | * Like, the fact that two platforms would become involved in the "rebuild-linux" label.
| 13:35:22 |
| vcunat | And switching to sum is problematic in the aspect that typically it will double the value. | 13:36:12 |
| vcunat | So we'd be changing that now. | 13:36:26 |
| vcunat | * Sum might be best, though I'm not sure really. | 13:36:51 |
| hexa | ok, so rebuild-${system} then | 14:00:12 |
| hexa | would probably be the safest migration path, since people are familiar with the rebuild count labels | 14:00:47 |
| hexa | except for maybe that rebuild-linux currently causes up to twice the rebuilds | 14:01:15 |
| hexa | which is why the proposal would make things a bit clearer | 14:01:37 |
 Lily Foster | In reply to @hexa:lossy.network
ok, so rebuild-${system} then i'll make PR then today. do you wanna make labels? | 14:36:05 |
| hexa | gh label create --color "#eeffee" "10.rebuild-aarch64-darwin: 0"
gh label create --color "#eeffee" "10.rebuild-aarch64-darwin: 1"
gh label create --color "#eeffee" "10.rebuild-aarch64-darwin: 1-10"
gh label create --color "#fbca04" "10.rebuild-aarch64-darwin: 11-100"
gh label create --color "#fbca04" "10.rebuild-aarch64-darwin: 101-500"
gh label create --color "#d93f0b" "10.rebuild-aarch64-darwin: 501-1000"
gh label create --color "#b60205" "10.rebuild-aarch64-darwin: 1001-2500"
gh label create --color "#b60205" "10.rebuild-aarch64-darwin: 2501-5000"
gh label create --color "#b60205" "10.rebuild-aarch64-darwin-stdenv"
gh label create --color "#eeffee" "10.rebuild-aarch64-linux: 0"
gh label create --color "#eeffee" "10.rebuild-aarch64-linux: 1"
gh label create --color "#eeffee" "10.rebuild-aarch64-linux: 1-10"
gh label create --color "#fbca04" "10.rebuild-aarch64-linux: 11-100"
gh label create --color "#fbca04" "10.rebuild-aarch64-linux: 101-500"
gh label create --color "#d93f0b" "10.rebuild-aarch64-linux: 501-1000"
gh label create --color "#b60205" "10.rebuild-aarch64-linux: 1001-2500"
gh label create --color "#b60205" "10.rebuild-aarch64-linux: 2501-5000"
gh label create --color "#b60205" "10.rebuild-aarch64-linux-stdenv"
gh label edit --name "10.rebuild-x86_64-linux: 0" "10.rebuild-linux: 0"
gh label edit --name "10.rebuild-x86_64-linux: 1" "10.rebuild-linux: 1"
gh label edit --name "10.rebuild-x86_64-linux: 1-10" "10.rebuild-linux: 1-10"
gh label edit --name "10.rebuild-x86_64-linux: 11-100" "10.rebuild-linux: 11-100"
gh label edit --name "10.rebuild-x86_64-linux: 101-500" "10.rebuild-linux: 101-500"
gh label edit --name "10.rebuild-x86_64-linux: 501-1000" "10.rebuild-linux: 501-1000"
gh label edit --name "10.rebuild-x86_64-linux: 1001-2500" "10.rebuild-linux: 1001-2500"
gh label edit --name "10.rebuild-x86_64-linux: 2501-5000" "10.rebuild-linux: 2501-5000"
gh label edit --name "10.rebuild-x86_64-linux-stdenv" "10.rebuild-linux-stdenv"
gh label edit --name "10.rebuild-x86_64-darwin: 0" "10.rebuild-darwin: 0"
gh label edit --name "10.rebuild-x86_64-darwin: 1" "10.rebuild-darwin: 1"
gh label edit --name "10.rebuild-x86_64-darwin: 1-10" "10.rebuild-darwin: 1-10"
gh label edit --name "10.rebuild-x86_64-darwin: 11-100" "10.rebuild-darwin: 11-100"
gh label edit --name "10.rebuild-x86_64-darwin: 101-500" "10.rebuild-darwin: 101-500"
gh label edit --name "10.rebuild-x86_64-darwin: 501-1000" "10.rebuild-darwin: 501-1000"
gh label edit --name "10.rebuild-x86_64-darwin: 1001-2500" "10.rebuild-darwin: 1001-2500"
gh label edit --name "10.rebuild-x86_64-darwin: 2501-5000" "10.rebuild-darwin: 2501-5000"
gh label edit --name "10.rebuild-x86_64-darwin-stdenv" "10.rebuild-darwin-stdenv"
| 14:36:15 |
| Lily Foster | oh have you already done them? | 14:36:36 |
| hexa | not yet | 14:36:39 |
| Lily Foster | or do you want me to run that when it's deployed? | 14:36:42 |
| hexa | ideally someone proofchecks them | 14:36:47 |
| hexa | I don't care about running them myself 😄 | 14:36:52 |
| Lily Foster | okie | 14:36:59 |
| hexa | * I don't care about creating them myself 😄 | 14:37:00 |
| hexa | * ideally someone proofreads them | 14:37:07 |
| hexa | white = "#eeffee"
yellow = "#fbca04"
orange = "#d93f0b"
red = "#b60205"
ranges = {
": 0": white,
": 1": white,
": 1-10": white,
": 11-100": yellow,
": 101-500": yellow,
": 501-1000": orange,
": 1001-2500": red,
": 2501-5000": red,
"-stdenv": red,
}
systems = [
"aarch64-darwin",
"aarch64-linux",
]
legacy_systems = {
"linux": "x86_64-linux",
"darwin": "x86_64-darwin",
}
for system in systems:
for range, color in ranges.items():
print(f'gh label create --color "{color}" "10.rebuild-{system}{range}"')
for legacy_name, name in legacy_systems.items():
for range in ranges.keys():
print(f'gh label edit --name "10.rebuild-{name}{range}" "10.rebuild-{legacy_name}{range}"')
| 14:37:27 |
 cole-h | Rather than renaming, could we just create new labels? That would allow the labels to be created and the change to be deployed independently of each other, and not need to worry about a race between the two | 16:47:17 |
