| 22 Sep 2024 |
 aleksana (force me to bed after 18:00 UTC) | per month | 10:10:17 |
| aleksana (force me to bed after 18:00 UTC) | https://docs.github.com/en/actions/administering-github-actions/usage-limits-billing-and-administration#usage-limits | 10:10:28 |
| aleksana (force me to bed after 18:00 UTC) | 5 concurrent macOS jobs (machine) | 10:10:44 |
| aleksana (force me to bed after 18:00 UTC) | Each job can run up to 6 hours | 10:11:05 |
 cafkafk | Pretty sure you're in breaking ToS territory | 10:11:21 |
| aleksana (force me to bed after 18:00 UTC) | But it seems like GitHub does not allow deploying tasks from remote connection, not from the repository (for free users). | 10:12:01 |
| aleksana (force me to bed after 18:00 UTC) | But if we trigger workflow directly from Nixpkgs repository with each PR, is the time calculated to NixOS organization or PR author? | 10:13:25 |
| cafkafk | Also it should be noted that it seems macOS 3-core usage is 10x as expensive as the Ubuntu 2-core | 10:16:02 |
| cafkafk | I've used only 152 hours of macOS 3-core this month, but that's counted as 1520 hours | 10:16:30 |
| aleksana (force me to bed after 18:00 UTC) | In reply to @cafkafk:gitter.im
I've used only 152 hours of macOS 3-core this month, but that's counted as 1520 hours So we can only use 3.3 hours per user per month | 10:18:28 |
| aleksana (force me to bed after 18:00 UTC) | Also do the builds for merged/closed PRs get cancelled or killed from the queue now? | 10:20:09 |
| cafkafk | It seems that I'm only paying for private repository actions when I look at my summary thou | 10:23:04 |
 7c6f434c | From the code, looks like merged PRs do not get the builds cancelled | 10:25:11 |
| 27 Sep 2024 |
|  loudgolem changed their display name from phanirithvij to loudgolem. | 14:38:04 |
| loudgolem changed their profile picture. | 14:38:30 |
| 28 Sep 2024 |
|  sstubbs joined the room. | 14:49:09 |
| sstubbs | I have a PR that has been waiting for ofborg for a week. Is this something common or is there something I need to do to get this to run? Also I notice it's waiting for x86_64-darwin when I have only included aarch64-darwin. | 14:59:29 |
 K900 | Darwin builders are very much over capacity | 14:59:47 |
| K900 | It's possible it's actually just in the queue | 14:59:53 |
| sstubbs | OK no rush from my end just checking. | 15:00:13 |
| sstubbs | Is there a way to exclude it from adding it to the x86 darwin queue in future if I'm only including aarch64? | 15:00:52 |
| K900 | Not really | 15:01:02 |
| sstubbs | Ah ok thanks. | 15:01:13 |
| 1 Oct 2024 |
|  -_o joined the room. | 21:00:28 |
| 10 Oct 2024 |
|  adamcstephens joined the room. | 16:07:43 |
| 18 Oct 2024 |
|  @domenkozar:matrix.org left the room. | 00:13:53 |
|  Emmanuel Genga joined the room. | 09:39:37 |
| 19 Oct 2024 |
 iv-nn | I've a PR that's been waiting for aarch64-darwin for one month and 16 days. I know it's over capacity and supposed to be long but is it normal to be this long? | 09:39:24 |
| Emmanuel Genga | I've got a pr that fails ofborg evaluation , here's the error message
https://gist.github.com/GrahamcOfBorg/e69f59a8ff42ef9bb7c4a49387f87d0a
| 09:55:15 |
| Emmanuel Genga | * I've got a pr that fails ofborg evaluation , here's the error message
https://gist.github.com/GrahamcOfBorg/e69f59a8ff42ef9bb7c4a49387f87d0a
The pr
https://github.com/NixOS/nixpkgs/pull/349304
| 09:55:50 |
