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

Github workflows available locally #3

Open
mttschltz opened this issue Dec 19, 2021 · 0 comments
Open

Github workflows available locally #3

mttschltz opened this issue Dec 19, 2021 · 0 comments
Labels
devops Test automation, deployment, observability

Comments

@mttschltz
Copy link
Owner

Goals

  • Debug CD issues easily by being able to run Github workflows locally
  • Bonus: If they're fast, add to pre-commit hooks

Initial investigation

On 2021-12-20 I tried to get act running locally.

Came across the following problems

It only took act 1m27s from start to the point of failure with visual regression tests, and that job was not running in parallel but after the first (unit test) job. So it seems quite fast.

loki output within act

| WARN asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
| WARN This can impact web performance.
| WARN Assets: 
| WARN   vendors~main.8c347319.iframe.bundle.js (2.3 MiB)
| WARN entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
| WARN Entrypoints:
| WARN   main (2.35 MiB)
| WARN       runtime~main.97d9166e.iframe.bundle.js
| WARN       vendors~main.8c347319.iframe.bundle.js
| WARN       main.bf0f3db5.iframe.bundle.js
| WARN 
| info => Output directory: /home/matt/projects/life/storybook-static
| loki test v0.28.1
| PASS chrome.docker/PREPARE
| PASS chrome.docker/START
| PASS chrome.docker/FETCH_STORIES
| PASS chrome.docker/chrome.laptop/Controls/Button/Kind
| PASS chrome.docker/chrome.laptop/Layout/Box/Align
| PASS chrome.docker/chrome.laptop/Layout/Box/Background
| FAIL chrome.docker/chrome.laptop/Layout/Box/Simple: Screenshot differs from reference, see .loki/difference/chrome_laptop_Layout_Box_Simple.png
| PASS chrome.docker/chrome.laptop/Layout/Box/Height
| FAIL chrome.docker/chrome.laptop/Layout/Box/Padding: Screenshot differs from reference, see .loki/difference/chrome_laptop_Layout_Box_Padding.png
| FAIL chrome.docker/chrome.laptop/Layout/Box/Margin: Screenshot differs from reference, see .loki/difference/chrome_laptop_Layout_Box_Margin.png
| PASS chrome.docker/chrome.laptop/Layout/Box/Width
| PASS chrome.docker/chrome.iphone7/Controls/Button/Kind
| PASS chrome.docker/chrome.iphone7/Layout/Box/Align
| FAIL chrome.docker/chrome.iphone7/Layout/Box/Simple: Screenshot differs from reference, see .loki/difference/chrome_iphone7_Layout_Box_Simple.png
| PASS chrome.docker/chrome.iphone7/Layout/Box/Background
| PASS chrome.docker/chrome.iphone7/Layout/Box/Height
| PASS chrome.docker/chrome.iphone7/Layout/Box/Width
| FAIL chrome.docker/chrome.iphone7/Layout/Box/Margin: Screenshot differs from reference, see .loki/difference/chrome_iphone7_Layout_Box_Margin.png
| FAIL chrome.docker/chrome.iphone7/Layout/Box/Padding: Screenshot differs from reference, see .loki/difference/chrome_iphone7_Layout_Box_Padding.png
| FAIL chrome.docker/TESTS: Some tasks failed to run
| FAIL chrome.docker: Some tasks failed to run
| Visual tests failed
| You can update the reference files with:
| loki update --storiesFilter="^Layout\\/Box Simple|Layout\\/Box Margin|Layout\\/Box Padding\$" --reactUri="file:./storybook-static"
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[matt.fyi CD/Visual regression tests       ]   ❌  Failure - Visual regression tests
Error: exit with `FAILURE`: 1
@mttschltz mttschltz added the devops Test automation, deployment, observability label Dec 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops Test automation, deployment, observability
Projects
None yet
Development

No branches or pull requests

1 participant