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 reporting when skipping extensions #3254

Merged
merged 5 commits into from
Mar 25, 2020

Conversation

Flamefire
Copy link
Contributor

The lists ext and ext_instances become out of sync when extensions are skipped.
Hence use ext_instances as the true source for reporting

Also fix the documentation of skip_extensions and add verbose reporting to stdout

Fixes #3253

boegel
boegel previously approved these changes Mar 24, 2020
Copy link
Member

@boegel boegel left a comment

Choose a reason for hiding this comment

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

lgtm

@boegel boegel added the bug fix label Mar 24, 2020
@boegel boegel added this to the next release (4.2.0) milestone Mar 24, 2020
The lists ext and ext_instances become out of sync when extensions are skipped.
Hence use ext_instances as the true source for reporting
Also fix the documentation of skip_extensions and add verbose reporting to stdout
@boegel
Copy link
Member

boegel commented Mar 24, 2020

Changes look good, but I'm wondering if we can make sure the tests trip over the misreporting?

@Flamefire
Copy link
Contributor Author

Not without actually running a real build and intercepting the output. Sounds like a bit of overkill for me.

@boegel
Copy link
Member

boegel commented Mar 25, 2020

@Flamefire We try to get all bug fixes covered by the tests, to avoid re-introducing the issue later.

Done in Flamefire#1

@Flamefire
Copy link
Contributor Author

Ah that easy, thanks!

@easybuilders easybuilders deleted a comment from boegelbot Mar 25, 2020
@Flamefire
Copy link
Contributor Author

@boegel API rate limit hit. We can only to 60/hour which are hit easily: There are 8 travis jobs per build. Hence less than 8 builds can be done per hour. Better solution: #3257

@boegel
Copy link
Member

boegel commented Mar 25, 2020

@Flamefire I think the issue was that the Travis GitHub App was not registered yet, which I've fixed just now. We shouldn't be hitting rate limits at all I think...

@boegel boegel merged commit 2f380fb into easybuilders:develop Mar 25, 2020
@Flamefire
Copy link
Contributor Author

60/hour isn't much. In the mentioned PR I use an endpoint that isn't even rate limitted hence should work better.

@Flamefire Flamefire deleted the fix_ext_skipping branch March 25, 2020 13:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Progress reporting for --skip shows wrong extensions
2 participants