Skip to content

Conversation

@Eomm
Copy link
Member

@Eomm Eomm commented Jan 8, 2022

Testing the new reusable workflow

@Eomm Eomm requested a review from Fdawgs January 8, 2022 08:54
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

Seem to work great! Just a note!

Eomm and others added 2 commits January 8, 2022 10:17
Co-authored-by: Matteo Collina <hello@matteocollina.com>
@Eomm
Copy link
Member Author

Eomm commented Jan 8, 2022

There was an error on the coverage step that requires the --cov --coverage-report=html args.

Run coverallsapp/github-action@master
  with:
    github-token: ***
    parallel: true
    flag-name: run-12-ubuntu-latest
    path-to-lcov: ./coverage/lcov.info
    coveralls-endpoint: https://coveralls.io
Using lcov file: ./coverage/lcov.info
Error: Lcov file not found.

Now the error is the following:

Run coverallsapp/github-action@master
Using lcov file: ./coverage/lcov.info
Error: Bad response: 422 {"message":"Couldn't find a repository matching this job.","error":true}

Not sure the config required to get the coverrals working.

@mcollina
Copy link
Member

mcollina commented Jan 8, 2022

I would just remove coveralls from everywhere.

@Fdawgs
Copy link
Member

Fdawgs commented Jan 8, 2022

Now the error is the following:


Run coverallsapp/github-action@master

Using lcov file: ./coverage/lcov.info

Error: Bad response: 422 {"message":"Couldn't find a repository matching this job.","error":true}

Not sure the config required to get the coverrals working.

I think I talked about this with @mcollina early last year when I was trying to standardise the plugin repos. Some of the repos in the Fastify org do not send coverage to Coveralls or fail to do so if they try (like this one). Fastify-cors is an example of one that does manage to send coverage. If the repo is missing a coveralls badge in the readme then it's one that will most likely fail.

@mcollina
Copy link
Member

mcollina commented Jan 8, 2022

I would just disable it everywhere, it's not worth it (effort vs the information it provides).

@zekth
Copy link
Member

zekth commented Jan 8, 2022

+1 on disabling coveralls if it's a blocker for this feature

@Eomm Eomm mentioned this pull request Jan 9, 2022
2 tasks
@Eomm Eomm marked this pull request as draft January 9, 2022 10:24
@Fdawgs
Copy link
Member

Fdawgs commented Jan 12, 2022

@Eomm, v2 of workflows has been released, which has removed all coveralls integration.

@@ -1,45 +1,15 @@
name: ci
'on':
name: CI
Copy link
Member

Choose a reason for hiding this comment

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

The CI badge in the readme may need to be updated if changing from lower to uppercase, but i prefer the uppercase to be honest!

Copy link
Member Author

Choose a reason for hiding this comment

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

Good spot: for consistency in the action menu, I would keep the old ci name.

I must say that I like the upper case too 😖

@Eomm Eomm marked this pull request as ready for review January 12, 2022 22:29
@Fdawgs
Copy link
Member

Fdawgs commented Jan 13, 2022

LGTM 👍

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.

5 participants