Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: split node from CI #1566

Merged
merged 18 commits into from
Sep 21, 2023
Merged

chore: split node from CI #1566

merged 18 commits into from
Sep 21, 2023

Conversation

fbarbu15
Copy link
Collaborator

@fbarbu15 fbarbu15 commented Sep 12, 2023

Problem

See #1548

Solution

Created a new workflow test-node that has the workflow_call and can be called from nwaku as well
Removed workflow_call and all extra conditions from the main workflow
Calling the new workflow for all node test jobs

@github-actions
Copy link

github-actions bot commented Sep 12, 2023

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
Waku core 28.79 KB (0%) 576 ms (0%) 430 ms (+72.34% 🔺) 1.1 s
Waku Simple Light Node 310.09 KB (0%) 6.3 s (0%) 946 ms (-1.31% 🔽) 7.2 s
ECIES encryption 28.68 KB (0%) 574 ms (0%) 410 ms (-3.55% 🔽) 983 ms
Symmetric encryption 28.68 KB (0%) 574 ms (0%) 354 ms (+16.04% 🔺) 928 ms
DNS discovery 118.59 KB (0%) 2.4 s (0%) 669 ms (+5.62% 🔺) 3.1 s
Privacy preserving protocols 122.6 KB (0%) 2.5 s (0%) 646 ms (+28.02% 🔺) 3.1 s
Light protocols 29.25 KB (0%) 585 ms (0%) 397 ms (+1.5% 🔺) 982 ms
History retrieval protocols 28.34 KB (0%) 567 ms (0%) 391 ms (+37.77% 🔺) 958 ms
Deterministic Message Hashing 5.64 KB (0%) 113 ms (0%) 77 ms (-41.99% 🔽) 189 ms

@fbarbu15 fbarbu15 changed the title split node from CI split: node from CI Sep 12, 2023
@fbarbu15 fbarbu15 changed the title split: node from CI chore: split node from CI Sep 12, 2023
@fbarbu15 fbarbu15 marked this pull request as ready for review September 12, 2023 15:25
@fbarbu15 fbarbu15 requested a review from a team as a code owner September 12, 2023 15:25
@fbarbu15
Copy link
Collaborator Author

Not sure why it appears 1 expected checks here. @weboko do you know?
image

DEBUG: ${{ (inputs.test_type == 'go-waku-master' || inputs.test_type == 'nwaku-master') && 'waku*' || '' }}

jobs:
node:
Copy link
Collaborator

@weboko weboko Sep 12, 2023

Choose a reason for hiding this comment

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

Github CI works in a way that if is sees a file in the workflows folder then it unfolds into steps in the CI.

One way can be to re-use the action but then you need to place it into actions folder (similar to actions/npm I created there) and from ther you can use it (I am not sure if it is possible to rely on it from different repo)

Or to create a file in workflows and expect it to be run in js-waku and nwaku and have conditions in it to handle that

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Tried to move it to actions but unfortunately it doesn't work. Actions is for jobs (like npm) not workflows and I need a workflow for the workflow_call functionality and cross repo usage.
So I need the new workflow to be excluded from the Required status checks in the Branch protection rules and made optional (similar to all other tests).
@weboko do you have access to do this or do I need to ask @fryorcraken ?
Thanks

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@weboko @fryorcraken little help here please

Copy link
Collaborator

Choose a reason for hiding this comment

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

@fbarbu15 was looking into it yesterday, to me it seemed that some different configuration might help here but if some setting on the repo required - I do not have access.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Let me know if you have a better idea on how to handle this.
On the other hand to fix it on my implementation we need something like this(tried it on a forked repo):
image

Copy link
Collaborator

@weboko weboko Sep 19, 2023

Choose a reason for hiding this comment

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

In that case we need to ask @fryorcraken to do the setting change

and I think we need to skip node Expected — Waiting for status to be reported in js-waku all together (seems it's already done)

@fbarbu15 fbarbu15 added the E:End-to-end testing See https://github.com/waku-org/pm/issues/34 for details label Sep 13, 2023
@fbarbu15 fbarbu15 requested a review from weboko September 13, 2023 08:58
@fryorcraken fryorcraken merged commit a0c96bb into master Sep 21, 2023
9 of 10 checks passed
@fryorcraken fryorcraken deleted the chore/split-ci-into-chunks branch September 21, 2023 01:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E:End-to-end testing See https://github.com/waku-org/pm/issues/34 for details
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants