Skip to content

Broken CI job: apidiff #284

Closed
Closed
@MadhavJivrajani

Description

@MadhavJivrajani

The apidiff job is broken since the merge of #243

I don't think its anything to do with the PR itself, but more to do with how apidiff handles things.
I've filed an issue for this with a potential root cause: golang/go#60911

One of 2 can be done here:

IMO we should revert for now to ensure the CI is in good shape for when we need to fix something here to mitigate a test flake/failure in something like k/k.

Reverting isn't an option since we've already merged the API and apidiff will fail on a package level (ref).

/cc @logicalhan
/cc @cpanato (in case you have an estimate yet on the go1.20 bumps of release branches)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions