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

Build broken because of dead link (p4tc) #5171

Closed
antoninbas opened this issue Mar 9, 2025 · 5 comments · Fixed by #5172
Closed

Build broken because of dead link (p4tc) #5171

antoninbas opened this issue Mar 9, 2025 · 5 comments · Fixed by #5172
Assignees
Labels
infrastructure Topics related to code style and build and test infrastructure. p4tc Topics related to the P4-TC back end. On PRs, also triggers p4tc CI tests to run.

Comments

@antoninbas
Copy link
Member

The build keeps failing because this link is dead:

URL https://github.com/p4tc-dev/iproute2-p4tc-pub/archive/refs/tags/release-v17-rc6.tar.gz

In particular, this workflow runs on a 4 hour schedule: https://github.com/p4lang/p4c/blob/main/.github/workflows/ci-container-image.yml. So I keep getting a failure notification every 4 hours :/

@antoninbas antoninbas added the infrastructure Topics related to code style and build and test infrastructure. label Mar 9, 2025
@ChrisDodd ChrisDodd added the p4tc Topics related to the P4-TC back end. On PRs, also triggers p4tc CI tests to run. label Mar 9, 2025
@ChrisDodd
Copy link
Contributor

Looks like this is from #5011

@fruffy
Copy link
Collaborator

fruffy commented Mar 10, 2025

@vbnogueira

The problem is that the p4tc testing setup is installed on every build. It should only be used by the p4tc workflow.

@antoninbas
Copy link
Member Author

@fruffy Github workflows have the following behavior for scheduled worklfows:

Notifications for scheduled workflows are sent to the user who last modified the cron syntax in the workflow file.

That user is me, so I get failure notifications every 4h when the build is broken. Any chance you would volunteer to update the cron syntax? BTW, in retrospect, running the workflow every 4h seems a bit excessive, maybe twice a day would be more than enough.

@fruffy
Copy link
Collaborator

fruffy commented Mar 10, 2025 via email

@trvon
Copy link

trvon commented Mar 10, 2025

I was able to get the build to working by updating the ./backends/tc/CMakeLists.txt file with the correct sha256 hash and updated version release-v17-rc8. It looks like the old release was deleted.

Here is what the update looks like. I am sure that this can be a simple pull request to master.

  fetchcontent_declare(
    iproute2repo
    URL https://github.com/p4tc-dev/iproute2-p4tc-pub/archive/refs/tags/release-v17-rc8.tar.gz
    URL_HASH SHA256=c96a057cae4054f06a906bb38e7f430cb27c7025cc23bae0943fdc0967c7be29
    SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}/runtime/iproute2-p4tc-pub
    USES_TERMINAL_DOWNLOAD TRUE
    GIT_PROGRESS TRUE
    DOWNLOAD_EXTRACT_TIMESTAMP TRUE
  )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Topics related to code style and build and test infrastructure. p4tc Topics related to the P4-TC back end. On PRs, also triggers p4tc CI tests to run.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants