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 CI use of txm and its need for a new Node #3293

Merged
merged 14 commits into from
May 18, 2021
Merged

Fix CI use of txm and its need for a new Node #3293

merged 14 commits into from
May 18, 2021

Conversation

adamnovak
Copy link
Member

Changelog Entry

To be copied to the draft changelog by merger:

  • vg autoindex now produces valid FAI indexes when the sequence name lines contain tabs.
  • vg autoindex has best-practices options set correctly for GBWT construction.
  • PKG_CONFIG_PATH is now forwarded to vcflib build
  • Gitlab build now runs with Node 14

Description

This pulls in #3287 and #3292 and should fix Gitlab CI by upgrading node beyond what Ubuntu LTS ships.

@adamnovak adamnovak changed the title Fix build Fix CI use of txm and its need for a new Node May 17, 2021
@adamnovak
Copy link
Member Author

It looks like we have another CI-breaking bug, which is that, successful docker login notwithstanding, Quay is refusing our image pushes:


#25 [run 4/5] COPY --from=build /vg/scripts/* /vg/scripts/
#25 sha256:5c4cafc6e5f8afcdeb7eb405481078f29dc92c25023044149551c4ee149f72b4
#25 CACHED

#26 [run 5/5] COPY --from=build /vg/deps/FlameGraph /vg/deps/FlameGraph
#26 sha256:cbaac0c9b60e7d1260dc0029981d7e32ec3939656157c42a26852ded5589a582
#26 CACHED

#27 exporting to image
#27 sha256:e8c613e07b0b7ff33893b694f7759a10d42e180f2b4dc349fb57dc6b71dcab00
#27 exporting layers done
#27 exporting manifest sha256:fda2303780903eb065b38b64236c9351be993724739b1dcc2c1c9283ce14ae45 done
#27 exporting config sha256:29f0b4e36410a2682c6aca9355b01eb6fd0f47feb5a9f6daf82e5fc73dff4f4e done
#27 pushing layers
#27 pushing layers 0.5s done
#27 pushing manifest for quay.io/vgteam/vg:ci-2989-3654fec4b54befeb506e7d379cb5f8ff0c61e7f1
#27 pushing manifest for quay.io/vgteam/vg:ci-2989-3654fec4b54befeb506e7d379cb5f8ff0c61e7f1 0.6s done
#27 ERROR: failed commit on ref "manifest-sha256:fda2303780903eb065b38b64236c9351be993724739b1dcc2c1c9283ce14ae45": unexpected status: 401 UNAUTHORIZED

I have no idea why they are doing this; it doesn't seem to happen every time, and it doesn't seem to be at all related to a long build time like all the other issues I can find complaining that their logins expired.

@jeizenga
Copy link
Contributor

Lovely.

@jeizenga jeizenga merged commit 9b0c959 into master May 18, 2021
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