Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

investigate & resolve failing colony job #2701

Closed
CruzMolina opened this issue Dec 18, 2019 · 4 comments
Closed

investigate & resolve failing colony job #2701

CruzMolina opened this issue Dec 18, 2019 · 4 comments
Labels
needs investigated priority2 ⚠️

Comments

@CruzMolina
Copy link
Contributor

On the merge for PR #2646, the colony job failed. We only run the colony job on pushes to develop, so there will need to be some investigation to figure out what exactly is causing the new behavior. So far it appears transactions cost more than they used to 🤷‍♂.

Unclear whether this is a regression or actually a fix made to ensure proper behavior.
@haltman-at
Copy link
Contributor

Hm, wondering if #2710 could be related? (Although, now that #2723 has come up as well... oy.)

@gnidan
Copy link
Contributor

gnidan commented Jan 6, 2020

Welcome back from break @haltman-at 😄

@area area mentioned this issue Jan 9, 2020
Closed
@haltman-at
Copy link
Contributor

Huh, looks like this is no longer a problem?

@CruzMolina
Copy link
Contributor Author

CruzMolina commented Jan 9, 2020 •
edited
Loading

Looks like #2727 resolved it. 👏

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
needs investigated priority2 ⚠️
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@gnidan @CruzMolina @eggplantzzz @haltman-at