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.

Sign up for GitHub

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

Jump to bottom

scripts/coverage sporadically fails: invalid instrumentation profile data (file header is corrupt) #4540

Open
LizardWizzard opened this issue Jun 21, 2023 · 1 comment
Open

scripts/coverage sporadically fails: invalid instrumentation profile data (file header is corrupt) #4540

LizardWizzard opened this issue Jun 21, 2023 · 1 comment
Assignees
@bayandin
Labels
a/tech_debt Area: related to tech debt c/storage Component: storage t/bug Issue Type: Bug triaged bugs that were already triaged

Comments

@LizardWizzard
Copy link
Contributor

Steps to reproduce

Usual run of our coverage script, see https://github.com/neondatabase/neon/actions/runs/5325108505/jobs/9645530141

Expected result

No errors

Actual result

+ scripts/coverage --profraw-prefix=regress-tests --dir=/tmp/coverage merge
warning: /tmp/coverage/profraw/regress-tests-132427-18172625578746094607_0.profraw: invalid instrumentation profile data (file header is corrupt)
error: no profile can be merged

Environment

Logs, links
@LizardWizzard LizardWizzard added t/bug Issue Type: Bug a/tech_debt Area: related to tech debt c/storage Component: storage labels Jun 21, 2023
@LizardWizzard LizardWizzard added the triaged bugs that were already triaged label Jul 3, 2023
@jcsp
Copy link
Collaborator

jcsp commented Jan 4, 2024

Saw this relatively issue again today (it's pretty rare):
https://github.com/neondatabase/neon/actions/runs/7400306977/job/20133914202?pr=6123

@bayandin bayandin mentioned this issue Jan 4, 2024
Draft
5 tasks
@bayandin bayandin mentioned this issue Feb 18, 2024
Merged
5 tasks
bayandin added a commit that referenced this issue Feb 19, 2024
@bayandin
CI: temporary disable coverage report for regression tests (#6798)
4d2bf55 
## Problem

The merging coverage data step recently started to be too flaky.
This failure blocks staging deployment and along with the flakiness of
regression tests might require 4-5-6 manual restarts of a CI job.

Refs:
- #4540
- #6485
- https://neondb.slack.com/archives/C059ZC138NR/p1704131143740669

## Summary of changes
- Disable code coverage report for functional tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bayandin bayandin

Labels
a/tech_debt Area: related to tech debt c/storage Component: storage t/bug Issue Type: Bug triaged bugs that were already triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bayandin @jcsp @LizardWizzard