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

Merge develop into breaking #12202

Merged
merged 58 commits into from
Oct 27, 2021
Merged

Merge develop into breaking #12202

merged 58 commits into from
Oct 27, 2021

Conversation

cameel
Copy link
Member

@cameel cameel commented Oct 27, 2021

The main reason for updating the branch is that I want to see if the t_ems_ext_hardhat job added in #12165 will pass on breaking too.

cameel and others added 30 commits October 14, 2021 18:55
- SemanticTests accepts fully qualified library name and also unqualifed library name when
the library is defined in the same file for convenience.
- commandline tests are added!

Signed-off-by: soroosh-sdi <soroosh.sardari@gmail.com>
Remove linking to unqualified library name
Template code for disallowing options in input modes that do not support them (handles `--error-recovery`)
[Docs] Fix formatting of the "security fixes" link on the main page
Fix typo in ir-breaking-changes.rst
Fix typo compiler->constructor.
Co-authored-by: shikharvashistha <shikharvashistha@yandex.com>
Co-authored-by: cameel <kamil.sliwak@codepoets.it>
[CI] Run hardhat tests as a PR check
…command

[CI] Reusable command for gitter notifications
Added different colors for warning & error
Do not use named function labels if function names are not unique.
…dition

Add missing condition to `gitter_notify` command
…arding-fqln

Clarify that `linkersymbol()` accepts but does not require a fully qualified library name
@cameel cameel self-assigned this Oct 27, 2021
@chriseth
Copy link
Contributor

Oh! The use-after-free is in develop?? I'll fix it right away.

@cameel
Copy link
Member Author

cameel commented Oct 27, 2021

CI seems to be failing for the same reason as the last time (#11840 (comment)).

Last time I reported it to CircleCI and this is how I described the situation (after some back and forth to provide more details):

The scheduled t_ubu_ossfuzz (816229) finished at 1:45 UTC but then there was another run ~5h later and you can see in the header that it was not a scheduled one: t_ubu_ossfuzz (816230). The workflow page only links to the earlier one.

So it looks like there was some glitch that associated the nightly run with the PR. The PR was different from usual PRs in that it was not associated with a short-lived feature branch. It was instead merging the main branch (develop) into another long-lived branch (breaking). Scheduled nightly workflows also run on develop so there might be some connection here.

The main part of the response I got was this:

I'm passing on this information to the team actively working on the issue, as mentioned by my colleague Aaron.
For now I'm putting this ticket on hold until we get an update from our software engineers regarding the implementation of a fix.
There's no need to reply right now. You will be notified automatically when the status of your issue is updated by CircleCI.

I haven't heard anything on the issue since then. Apparently the bug is still present. If my assessment is correct then a workaround is to simply merge something into develop. It will rerun the CI with correct jobs.

@chriseth
Copy link
Contributor

Fix is here: #12203

@cameel
Copy link
Member Author

cameel commented Oct 27, 2021

Oh! The use-after-free is in develop?? I'll fix it right away.

Yeah. It's not the first time this happens - some jobs that run outside of PRs have no notifications so we usually don't notice. I have a PR that adds notifications to them: #12174.

Moved storage size assert to TypeChecker from DeclarationTypeChecker
Fix wrong path to isoltest in docs
@cameel
Copy link
Member Author

cameel commented Oct 27, 2021

Looks like t_ems_ext_hardhat passed.

EDIT: Ah, wait. That's on develop. The job will run on breaking only after this PR is merged.

@chriseth chriseth merged commit 8c6e5e5 into breaking Oct 27, 2021
@cameel
Copy link
Member Author

cameel commented Oct 27, 2021

The Hardhat test finally ran on breaking and passed.

The workflow as a whole did not pass though. There's some unrelated breakage.

@cameel
Copy link
Member Author

cameel commented Jan 17, 2022

I just got a notification from CircleCI that the issue from #12202 (comment) has been fixed. So, hopefully, no more nightly workflow running on develop :)

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.

10 participants