Skip to content

Classify unknown errors by current step #1452

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

Merged
merged 6 commits into from
Aug 12, 2025

Conversation

colincasey
Copy link
Contributor

Instead of treating all errors without a specific handler as unknown, classify them as unknown according to the current build step where the failure occurred. E.g.;

  • unknown-build-script-error
  • unknown-prebuild-script-error
  • unknown-cleanup-error
  • and so on...

W-19282339

@colincasey colincasey self-assigned this Aug 8, 2025
@colincasey colincasey requested a review from a team as a code owner August 8, 2025 17:46
@colincasey colincasey added the skip changelog Changelog entry is not required - Skips changelog check label Aug 8, 2025
@dzuelke
Copy link
Contributor

dzuelke commented Aug 8, 2025

Philosophical discussion, but... should it maybe be steps.<build-step>.failures.unknown? Or, either way, would it make sense to have .unknown always at the end, or at least make the identifiers something.unknown.reason, so that it becomes easier to build reports that capture e.g. counts of all unknown failures (by counting all occurences of *.unknown and *.unknown.*? Having a dash as the separator after unknown I think introduces ambiguity - e.g. imagine failures.dependency-resolution.unknown-package, which would semantically "collide".

@edmorley
Copy link
Member

Philosophical discussion, but... should it maybe be

The mcount helpers can all be removed, at which point I think this resolves itself?

Base automatically changed from fix_yaml_string_escape to main August 12, 2025 14:45
@colincasey colincasey requested a review from edmorley August 12, 2025 14:47
@colincasey colincasey enabled auto-merge (squash) August 12, 2025 14:49
@colincasey colincasey merged commit 0bf4580 into main Aug 12, 2025
10 checks passed
@colincasey colincasey deleted the classify_generic_build_script_error branch August 12, 2025 15:01
@heroku-linguist heroku-linguist bot mentioned this pull request Aug 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip changelog Changelog entry is not required - Skips changelog check
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants