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

GHA: Move from always() to !cancelled() #86

Merged
merged 1 commit into from
Jan 11, 2024

Conversation

stronk7
Copy link
Member

@stronk7 stronk7 commented Dec 19, 2023

And add extra step to mark cancelled jobs as failed.

And add extra step to mark cancelled jobs as failed.
Copy link

codecov bot commented Dec 19, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (9e3dcb0) 96.46% compared to head (66cf4ff) 96.46%.

Additional details and impacted files
@@            Coverage Diff            @@
##               main      #86   +/-   ##
=========================================
  Coverage     96.46%   96.46%           
  Complexity      517      517           
=========================================
  Files            22       22           
  Lines          1471     1471           
=========================================
  Hits           1419     1419           
  Misses           52       52           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@stronk7
Copy link
Member Author

stronk7 commented Jan 11, 2024

Self-merging this, so further changes can happen...

@stronk7 stronk7 merged commit 0cfc3d8 into moodlehq:main Jan 11, 2024
8 checks passed
@stronk7 stronk7 deleted the move_always_to_cancelled branch January 11, 2024 11:08
@stronk7
Copy link
Member Author

stronk7 commented Jan 11, 2024

Drat, it seems that the tests that were passing ok some weeks ago have started to fail now with PHP 7.4, some updated component I bet.

Example: https://github.com/moodlehq/moodle-cs/actions/runs/7487886902/job/20381269027

Will look to this in separate issue and try to hot-fix it... ciao :-)

@stronk7
Copy link
Member Author

stronk7 commented Jan 11, 2024

Just to confirm, it seems that the new https://github.com/nikic/PHP-Parser/releases/tag/v5.0.0 (released 4 days ago) is the change leading to the problems... so, apart from investigating and reporting it upstream... I'm going to try to force v4 here to be back to green ASAP.

@stronk7
Copy link
Member Author

stronk7 commented Jan 11, 2024

And #89 will fix the troubles, by making nikic/php-parser to stay sticky to v4 (curious that both phpunit and php-code-coverage have started to allow v5 when they are exactly the ones breaking with v5).

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.

1 participant