[warning] failed package validation and/or copy for commit c1ed1ea6a8c9fcf46e1dd29b728077f7401d6440

[conda-forge-webservices[bot]]

Hi @conda-forge/sccache! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token. Below we have put some information about the failure to help you debug it.

Rerendering the feedstock will usually fix these problems.

If you have any issues or questions, you can find us on Element in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/sccache! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token. Below we have put some information about the failure to help you debug it.

Rerendering the feedstock will usually fix these problems.

If you have any issues or questions, you can find us on Element in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/sccache! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token. Below we have put some information about the failure to help you debug it.

Rerendering the feedstock will usually fix these problems.

If you have any issues or questions, you can find us on Element in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/sccache! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token. Below we have put some information about the failure to help you debug it.

Rerendering the feedstock will usually fix these problems.

If you have any issues or questions, you can find us on Element in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/sccache! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token. Below we have put some information about the failure to help you debug it.

Rerendering the feedstock will usually fix these problems.

If you have any issues or questions, you can find us on Element in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/sccache! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token. Below we have put some information about the failure to help you debug it.

Rerendering the feedstock will usually fix these problems.

If you have any issues or questions, you can find us on Element in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/sccache! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token. Below we have put some information about the failure to help you debug it.

Rerendering the feedstock will usually fix these problems.

If you have any issues or questions, you can find us on Element in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/sccache! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token. Below we have put some information about the failure to help you debug it.

Rerendering the feedstock will usually fix these problems.

If you have any issues or questions, you can find us on Element in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[jakirkham]

This was recently fixed. Please see discussion in this issue ( https://github.com/conda-forge/admin-requests/issues/855 ) for details. Closing this out

[jakirkham]

@jonashaag could you please do us a favor and relogin to Travis CI? It is possible to do that with GH login if you prefer

Asking as there are Travis requests that failed to start a job (please see the screenshot below)

The recommendation by Travis to resolve this issue was to logout of Travis CI and relogin ( https://github.com/conda-forge/admin-requests/issues/855#issuecomment-1799348780 )

[jonashaag]

Ok I just did as you suggested. I wonder what my personal Travis token has to do with this build pipeline though? I haven't logged in to Travis for months

[jakirkham]

Thanks Jonas! 🙏

Could you please try creating a new PR? Maybe just making some small tweak to the recipe. Would like to confirm that fixed the issue (or follow up with Travis if not)

We were fixing a different issue recently ( https://github.com/conda-forge/staged-recipes/issues/24406 ). This new issue with requests only started happening after. It's possible the fix deployed is now causing us to reauthenticate with Travis CI. This is only a personal theory though

[jakirkham]

Updating the thread, please see testing in PR: https://github.com/conda-forge/sccache-feedstock/pull/34

[jakirkham]

Looks like things are working. Thanks Jonas! 🙏

Closing as resolved