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

fix: ci and e2e test #383

Merged
merged 30 commits into from
Nov 4, 2022

Conversation

ShootingKing-AM
Copy link
Contributor

@ShootingKing-AM ShootingKing-AM commented Oct 26, 2022

- use chrome as being done in CI
- Narrow down Selector to div with alert class else larger vue app dialog will be matched
@codecov
Copy link

codecov bot commented Oct 26, 2022

Codecov Report

Base: 25.35% // Head: 25.05% // Decreases project coverage by -0.30% ⚠️

Coverage data is based on head (512f690) compared to base (27e5c59).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #383      +/-   ##
==========================================
- Coverage   25.35%   25.05%   -0.31%     
==========================================
  Files          26       27       +1     
  Lines        1471     1489      +18     
  Branches      235      240       +5     
==========================================
  Hits          373      373              
- Misses       1068     1086      +18     
  Partials       30       30              
Impacted Files Coverage Δ
src/util/classes.ts 81.18% <0.00%> (-1.65%) ⬇️
src/stores/categories.ts 55.55% <0.00%> (-1.59%) ⬇️
src/util/validate.ts 0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

* fix: Display proper error content in e2e test

- use chrome as being done in CI
- Narrow down Selector to div with alert class else larger vue app dialog will be matched

* Update nodejs.yml

* fix: check errors after taking screenshot
- add contents of loading elements if found to log since >95% of CI errors are on timeouts as of now
- github runners genuinely takes more time to load timeline view (as can be confirmed from previous ci-runs (logs and screenshots) of this pr
- since 40s is also not enough sometimes for loading timeline
@ShootingKing-AM ShootingKing-AM marked this pull request as draft October 27, 2022 00:56
@ShootingKing-AM ShootingKing-AM marked this pull request as ready for review October 27, 2022 01:03
@ShootingKing-AM ShootingKing-AM marked this pull request as draft October 27, 2022 01:09
- it seems like the indefinite wait is not working, pointing to some other issues
- went bank to 20s wait time + Extra logging of browser console and dumping HTTP requests of non js css font image requests
@ShootingKing-AM ShootingKing-AM marked this pull request as ready for review October 27, 2022 05:18
@ShootingKing-AM
Copy link
Contributor Author

ShootingKing-AM commented Oct 27, 2022

Update: sometimes aw-server-rust(Rocket) is not even getting the requests - https://github.com/ActivityWatch/aw-webui/actions/runs/3341509927/jobs/5532792619#step:15:355 even when webui sent the request - https://github.com/ActivityWatch/aw-webui/actions/runs/3341509927/jobs/5532792619#step:12:275 - weird

@ShootingKing-AM
Copy link
Contributor Author

ShootingKing-AM commented Oct 28, 2022

The issue can be in testcafe, node, github-actions, or rocket internals none of which are in the scope of this organization. Guess we have to stick to the refresh-if-loading not dissapers workarround for now. If even this workarround fails, all we can do is just increase the refresh values in https://github.com/ActivityWatch/aw-webui/pull/383/files#diff-409ad53159fcbc018c9fbe758b15f440bcef12d37127ead30403a3d528e30a55R8-R10.

We can also start building for rust-server-nightly, any reason its commented out @ErikBjare ?

Copy link
Member

@ErikBjare ErikBjare left a comment

Choose a reason for hiding this comment

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

Very nice!

Merging ActivityWatch/aw-server-rust#310 now.

Anything left to do here?


We can also start building for rust-server-nightly, any reason its commented out?

Feels like CI abuse to have it on all the time, feel free to enable if it helps you :)

Makefile Show resolved Hide resolved
.github/workflows/nodejs.yml Show resolved Hide resolved
.github/workflows/nodejs.yml Show resolved Hide resolved
.github/workflows/nodejs.yml Show resolved Hide resolved
test/e2e/screenshot.test.js Show resolved Hide resolved
@ShootingKing-AM
Copy link
Contributor Author

Thanks for the review and great comments :3
At this level it’s not CI abuse at all :3

We need to even have windows and mac os builds-and-test for atleast each for the latest release version of server and master of server.
I feel it’s better to bring to the notice of contributors that their contribution fails on certain cases, so the fixes can be done here and now(with much ease and isolation). Else the work maintainer needs to do when releasing an actual release would be unimaginable.

For now, this is it.

@ErikBjare ErikBjare merged commit cbb555d into ActivityWatch:master Nov 4, 2022
@ErikBjare
Copy link
Member

Very nice! Thank you so much for this ❤️

@ShootingKing-AM ShootingKing-AM deleted the fix-ci-error-log branch November 20, 2022 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants