Skip to content

add github action to wait for ofborg#93581

Merged
Mic92 merged 1 commit intoNixOS:masterfrom
Mic92:ofborg-wait
Jul 28, 2020
Merged

add github action to wait for ofborg#93581
Mic92 merged 1 commit intoNixOS:masterfrom
Mic92:ofborg-wait

Conversation

@Mic92
Copy link
Member

@Mic92 Mic92 commented Jul 21, 2020

In case ofborg is down this will not mark the CI as green.
Also if other github actions are used and pass
checks will be still marked as pending even if other other github
actions have passed.

@Mic92 Mic92 force-pushed the ofborg-wait branch 3 times, most recently from 9b5330c to dc8225b Compare July 21, 2020 08:04
@Mic92
Copy link
Member Author

Mic92 commented Jul 21, 2020

@GrahamcOfBorg build hello

@Mic92 Mic92 force-pushed the ofborg-wait branch 2 times, most recently from 3396bd0 to b7ab073 Compare July 21, 2020 08:08
@Mic92
Copy link
Member Author

Mic92 commented Jul 21, 2020

@GrahamcOfBorg build hello

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That commit still seems wrong...

@Mic92 Mic92 force-pushed the ofborg-wait branch 4 times, most recently from 179a21b to c10fc81 Compare July 21, 2020 08:25
@Mic92
Copy link
Member Author

Mic92 commented Jul 21, 2020

@GrahamcOfBorg build hello

@Mic92
Copy link
Member Author

Mic92 commented Jul 21, 2020

@GrahamcOfBorg eval

@zowoq
Copy link
Contributor

zowoq commented Jul 21, 2020

Something that might be an issue with this approach is the limits on github actions, if ofborg goes down we'll start burning through our allocation.

@Mic92
Copy link
Member Author

Mic92 commented Jul 21, 2020

It is limited to 10min. How much time on github actions do we have?

@zowoq
Copy link
Contributor

zowoq commented Jul 21, 2020

It is limited to 10min.

Which could end up adding up quickly if ofborg does down for any length of time.

@Mic92
Copy link
Member Author

Mic92 commented Jul 21, 2020

It is limited to 10min.

Which could end up adding up quickly if ofborg does down for any length of time.

Where do you have the information from that we have limits? This looks like there are only for private repos: https://docs.github.com/en/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions#about-spending-limits-for-github-actions

@zowoq
Copy link
Contributor

zowoq commented Jul 21, 2020

Where do you have the information from that we have limits? This looks like there are only for private repos:

Ah, must have misremembered. Concurrent jobs and API requests may be an issue?

https://docs.github.com/en/actions/getting-started-with-github-actions/about-github-actions#usage-limits

@Mic92
Copy link
Member Author

Mic92 commented Jul 21, 2020

Not really. It would just means that the job is started later...

In case ofborg is down this will not mark the CI as green.
Also if other github actions are used and pass
checks will be still marked as pending even if other other github
actions have passed.
@Mic92 Mic92 requested a review from grahamc July 21, 2020 08:40
@Mic92
Copy link
Member Author

Mic92 commented Jul 21, 2020

Any idea why ofborg is not picking up this PR? Do I need to modify nix files?

@Mic92
Copy link
Member Author

Mic92 commented Jul 21, 2020

@GrahamcOfBorg eval

1 similar comment
@Mic92
Copy link
Member Author

Mic92 commented Jul 21, 2020

@GrahamcOfBorg eval

@zowoq
Copy link
Contributor

zowoq commented Jul 21, 2020

Any idea why ofborg is not picking up this PR? Do I need to modify nix files?

No. AFAIK, you shouldn't need to modify a nix file for it to start.

I have noticed that ofborg has been a bit flakey the last day or two, not picking up pushes or stopping after eval/meta checks and not triggering builds.

@ofborg ofborg bot added 6.topic: policy discussion Discuss policies to work in and around Nixpkgs 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. labels Jul 21, 2020
@ofborg ofborg bot added the 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux. label Jul 21, 2020
@flokli
Copy link
Member

flokli commented Jul 21, 2020

Let's keep the wip label as long as we flip the gnuhello tests, so we don't accidentially merge it ;-)

@ofborg ofborg bot requested a review from edolstra July 21, 2020 10:18
@ofborg ofborg bot added 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-darwin: 1 This PR causes 1 package to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. and removed 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux. labels Jul 21, 2020
@Mic92
Copy link
Member Author

Mic92 commented Jul 21, 2020

This is working now. In case it timeouts its still clear that ofborg should have been run so users are not tricked into thinking that the CI run successfully.

@ofborg ofborg bot added 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux. and removed 10.rebuild-darwin: 1 This PR causes 1 package to rebuild on Darwin. 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. labels Jul 21, 2020
@Mic92
Copy link
Member Author

Mic92 commented Jul 28, 2020

Let's see how this works out in practice.

@Mic92 Mic92 merged commit ece92ca into NixOS:master Jul 28, 2020
@Mic92 Mic92 deleted the ofborg-wait branch July 28, 2020 09:04
@zowoq
Copy link
Contributor

zowoq commented Aug 5, 2020

Builds started by an manual ofborg build *** satisfy this check, can we limit it to successful evals?

1

@Mic92
Copy link
Member Author

Mic92 commented Aug 5, 2020

Builds started by an manual ofborg build *** satisfy this check, can we limit it to successful evals?

1

It could check for a specific eval, but to be honest before we do this we rather should consider making the eval job a required check...

@zowoq
Copy link
Contributor

zowoq commented Aug 5, 2020

It could check for a specific eval, but to be honest before we do this we rather should consider making the eval job a required check...

Should we disable the actions for now until we get the required checks working?

The timeout job is a nice workaround but I think the drawbacks may be outweighing the benefits of having it just for the editorconfig check.

@Mic92
Copy link
Member Author

Mic92 commented Aug 5, 2020

It could check for a specific eval, but to be honest before we do this we rather should consider making the eval job a required check...

Should we disable the actions for now until we get the required checks working?

The timeout job is a nice workaround but I think the drawbacks may be outweighing the benefits of having it just for the editorconfig check.

This is a problem with or without github actions. If someone triggers ofborg build it will mark the build as green. I don't see how this is worth than the status quo. In fact having github actions increases seeing the absence of ofborg runs. If ofborg is down for example github actions would still mark the build as failed. So just having the Waiting for ofborg action provides value on its own.

@zowoq
Copy link
Contributor

zowoq commented Aug 5, 2020

In fact having github actions increases seeing the absence of ofborg runs. If ofborg is down for example github actions would still mark the build as failed. So just having the Waiting for ofborg action provides value on its own.

There was a 3hr wait for ofborg evals earlier, needed to clear a page of errored PRs after ofborg caught up.

@Mic92
Copy link
Member Author

Mic92 commented Aug 5, 2020

Let's continue discussion in #94658

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

6.topic: policy discussion Discuss policies to work in and around Nixpkgs 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants