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

Upload vcpkg install failure logs as artifact #120

Open
quyykk opened this issue Aug 29, 2023 · 1 comment
Open

Upload vcpkg install failure logs as artifact #120

quyykk opened this issue Aug 29, 2023 · 1 comment

Comments

@quyykk
Copy link

quyykk commented Aug 29, 2023

It would be nice for this action to upload the failure logs if a vcpkg port fails to build. The output always looks like this for example:

      See logs for more information:
        /home/runner/work/user/project/vcpkg/buildtrees/gtk3/config-x64-linux-dynamic-dbg-meson-log.txt.log
        /home/runner/work/user/project/vcpkg/buildtrees/gtk3/config-x64-linux-dynamic-dbg-out.log

It should be possible to parse those paths and upload the files as an artifact to facilitate debugging.

Thoughts? Thanks!

@lukka
Copy link
Owner

lukka commented Aug 29, 2023

@quyykk yes, there is already such functionality which dumps on the action's log the whole content of the files which match the regex provided by logCollectionRegExps input, see in action.yml:

 logCollectionRegExps:
    default: "\\s*\"(.+CMakeOutput\\.log)\"\\.\\s*;\\s*\"(.+CMakeError\\.log)\"\\.\\s*;\\s*(.+out\\.log)\\s*;\\s+(.+err\\.log)\\s*;\\s*(.+vcpkg.+\\.log)\\s*"
    required: false
    description: "Specifies a semicolon separated list of regular expressions that are used to identify log file paths in the workflow output. A regular expression must have a single capturing group, that is a single pair of parenthesis such as 'See also (.+.log)'. When a match occurs, the content of the file is written into the workflow output for disclosing its content to the user. The default regular expressions are for CMake's and vcpkg's log files."

That regex looks like not matching those files, do you have a link to the run?
Also, if you find how to augment the regexp to make it working in your case, I think I'd be super happy to merge the changes in and set them as default

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

No branches or pull requests

2 participants