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

add more information to collect_build_data output #3996

Merged
merged 1 commit into from
Jan 9, 2020

Conversation

garyverhaegen-da
Copy link
Contributor

The collect_build_data step has been failing on master. Based on its current output, it looks like:

  1. It doesn't have GCP credentials, and
  2. The status checks for other jobs erroneously fails.

Regarding 1, I currently have no clue what may be happening. Regarding 2, Azure did change the enum strings used for job statuses a few weeks ago, so maybe that happened again. I don't think we'll be able to know until this runs on master.

Copy link
Contributor

@hurryabit hurryabit left a comment

Choose a reason for hiding this comment

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

Looks good to me. Thanks.

This commit:
- fixes an issue introduced by e2015e2 whereby the data was never
saved to GCS, because if the variable _is_ set, then Azure will
substitute the right side of the comparison as well as set the
environment variable, so the two sides will still be equal. The new
approach skips the first character of the env var and removes the dollar
from the (intended) literal expression, ensuring Azure does not
substitute.
- adds output to the failure case because we have recently seen all
commits on master fail that step, regardless of success of other jobs.

CHANGELOG_BEGIN
CHANGELOG_END
@garyverhaegen-da garyverhaegen-da force-pushed the debug-collect-build-data branch from 03bc94f to c89ddf4 Compare January 9, 2020 11:01
@garyverhaegen-da
Copy link
Contributor Author

After further digging, it looks like 1 just never worked after e2015e2. The problem is that Azure will replace the variable in both the env var and the Bash script, so the two sides are also equal when the substitution does happen. To fix, I have removed the dollar sign on the right side (so Azure does no substitution) and used Bash syntax to say, on the left side, "take the value of the variable starting at character 1 (i.e. skipping 0) and taking length-1 characters (i.e. until the end)".

@garyverhaegen-da garyverhaegen-da merged commit 7260de6 into master Jan 9, 2020
@garyverhaegen-da garyverhaegen-da deleted the debug-collect-build-data branch January 9, 2020 12:03
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.

2 participants